agentleFS
Sign inStart free
ww-w-aiww-w-ai/bkit-claude-code/skills/bkit-explore/SKILL.md

bkit-explore

Skill605 starsChanged 3 months agoApache-2.0View on GitHub

Browse installed bkit skills, agents, and evals via lib/discovery/explorer.js (filesystem scan, no subprocess). Triggers: bkit explore, list skills, skill discovery, browse skills

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call explorer.listAll() to read skills/*/SKILL.md + agents/*.md.

    line 41
  2. Very specific:

    Call explorer.listEvals() and group by classification (workflow, capability, hybrid).

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

bkit Explore — Skill / Agent / Eval Discovery

v2.1.11 Sprint β FR-β1. Wraps lib/discovery/explorer.js to give Yuki + first-run users a single-command surface that answers "what's actually installed and how do I find it?"

Arguments

ArgumentDescriptionExample
(none)Show all categories with counts + first-line description/bkit-explore
<category>One of starter, dynamic, enterprise, pdca-core, utility/bkit-explore dynamic
evalsList skills with an evals/{cls}/{skill}/eval.yaml definition/bkit-explore evals
--level <L>Filter by Starter / Dynamic / Enterprise (cumulative)/bkit-explore --level Starter

Behavior

Default (no args) — full tree

  1. Call explorer.listAll() to read skills/*/SKILL.md + agents/*.md.
  2. Render category-grouped table: skill name + first-sentence description.
  3. Footer: Total: N skills · M agents · K evals.

<category> — single bucket

  1. Validate category against explorer.CATEGORIES.
  2. Render skill table + agent table for that bucket only.
  3. Suggest /bkit-explore --level Starter if user looks lost.

evals — eval coverage

  1. Call explorer.listEvals() and group by classification (workflow, capability, hybrid).
  2. Render counts + skill names per group.
  3. Tip: /bkit-evals run <skill> to execute one.

--level <L> — Starter / Dynamic / Enterprise filter

  1. Starter returns starter + pdca-core + utility.
  2. Dynamic adds dynamic (cumulative).
  3. Enterprise adds enterprise.

Output Layout (Design §5.1)

bkit Explore — 39 Skills · 36 Agents · K Evals
─────────────────────────────────────────────────
📂 starter (1 skill / 2 agents)
   /starter         — Static web kit
   🤖 starter-guide — Beginner agent
   🤖 pipeline-guide — Phase walk-through

📂 dynamic (8 skills / 2 agents)
   /dynamic           — bkend.ai fullstack
   /bkend-auth        — Authentication patterns
   ...
─────────────────────────────────────────────────
Footer: Try /bkit-explore --level Starter

Security

  • Pure filesystem scan — no child_process, no network.
  • category argument is validated against explorer.CATEGORIES (5-tuple whitelist); anything else returns null and renders a usage hint.
  • --level <L> validated against explorer.LEVELS (Starter / Dynamic / Enterprise).
  • Agent/skill descriptions read from local *.md files only — no remote fetch.

Module Dependencies

ModuleFunctionUsage
lib/discovery/explorer.jslistAll()Default tree
lib/discovery/explorer.jslistByCategory(cat)Single bucket
lib/discovery/explorer.jslistByLevel(level)Cumulative filter
lib/discovery/explorer.jslistEvals()evals/ scan

Categories (Design §3.2)

CategoryScope
starterStatic web + beginner-onboarding skills/agents
dynamicbkend.ai fullstack + Phase 1~6 build pipeline
enterpriseArchitecture + Phase 7~9 deployment + audit
pdca-corePDCA cycle + QA + PM agents
utilityCross-cutting (bkit, control, audit, evals)

Examples

# Full tree
/bkit-explore

# One category
/bkit-explore dynamic

# Cumulative level filter
/bkit-explore --level Starter

# Evals coverage
/bkit-explore evals

Related

  • /bkit-evals run <skill> — execute eval suite for one skill
  • /control trust — trust score informs which categories you can self-serve
  • /pdca status — find your active feature

ARGUMENTS:

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free