capability-discovery
Detect which MCP servers, Claude Code plugins, and CLI tools are available in the current environment, so kits and build sites can bind to real capabilities instead of imagined ones. Runs via /ck:init --tools-only or `cavekit-tools.cjs discover`. Writes .cavekit/capabilities.json. Trigger phrases: "what do we have available", "what's installed", "detect tools", "can we use X", "setup tools".
- License 许可
- MIT
- 最近更新
- 2026-08-26
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- capability-discovery
- description
- Detect which MCP servers, Claude Code plugins, and CLI tools are available in the current environment, so kits and build sites can bind to real capabilities instead of imagined ones. Runs via /ck:init --tools-only or `cavekit-tools.cjs discover`. Writes .cavekit/capabilities.json. Trigger phrases: "what do we have available", "what's installed", "detect tools", "can we use X", "setup tools".
02 资源文件 4
- 资产文件assets/01-template.md36 B
- 参考文档README.md431 B
- 参考文档references/01-overview.md32 B
- 参考文档references/02-usage.md24 B
03 SKILL.md 正文
Capability Discovery
The pipeline should never invent tools. Before drafting a kit that references GitHub Actions, Supabase, Codex, or any other external dependency, check what actually exists.
What we detect
- CLI tools on $PATH:
gh,git,node,go,rustc,cargo,python3,pip,docker,vercel,supabase,firebase,wrangler,ffmpeg,playwright,codex,graphify. - MCP servers: parsed from
.mcp.jsonin the project root and~/.claude.json(user level). - Claude Code plugins: parsed from
~/.claude/plugins/installed_plugins.json. - Codex: presence of the
codexCLI (enables peer-review commands). - Knowledge graph: presence of
graphify-out/graph.json(enables thegraphify-integrationskill).
Running discovery
node "${CLAUDE_PLUGIN_ROOT}/scripts/cavekit-tools.cjs" discover
Writes .cavekit/capabilities.json:
{
"discovered_at": "2026-04-17T14:22Z",
"cli_tools": {
"gh": true, "git": true, "node": true, "codex": false
},
"mcp_servers": ["codex-reviewer", "graphify"],
"plugins": [],
"codex": { "available": false }
}
How other commands use it
/ck:sketch— reads capabilities before proposing integrations. If a kit would need a missing tool, it either adds a "Setup" task to the build site or asks the user whether to proceed without it./ck:map— flags tasks that depend on missing capabilities asblocked: setup-required./ck:make— refuses to dispatch subagents that require a missing MCP server./ck:check— includes a "Capability Coverage" section in the inspect report.
When to re-run
- After installing a new CLI tool.
- After adding or removing an MCP server.
- At the start of every new project (via
/ck:init). - Whenever a task fails with "command not found".
The file is cheap to regenerate — always discover, never guess.
What we deliberately do not detect
- Network-accessible APIs behind credentials. Availability is not reachability; kits should record credentials as a separate concern (never committed).
- IDE extensions. They are not scriptable from the loop and would create false assurances.
- Language versions. Version-pinning is the project's responsibility (package.json / go.mod / pyproject.toml); discovery only confirms executables exist.
04 同仓库更多 Skills
zustand-5
Zustand 5 state management patterns. Trigger: When managing React state with Zustand.
zod-4
Zod 4 schema validation patterns. Trigger: When using Zod for validation - breaking changes from v3.
x-bookmark-quote-posts
Workflow para revisar bookmarks de X/Twitter y convertirlos en drafts de quote posts. Accede a la sección de bookmarks vía browser headless, extrae posts recientes, y genera drafts con voz personal del usuario. No publica ni muta X — solo genera contenido para revisión. Trigger: X bookmarks, Twitter bookmarks, quote posts, bookmark automation, crear quote posts, revisar bookmarks, growth content X.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.