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".
SkillScore77Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/15/2026
What it changes
Passed 13 of 17 test cases with the skill, and 6 of 17 without it.
Without skill36%
With skill77%
Checks it passed that the model alone missed
Enables peer-review commands
Checks for graphify-out/graph.json
Labels tasks with blocked: setup-required
and 6 more in the full report
9 fixed8 passed either way5 still failing0 broke
Pass-rate lift
+41 pp
Tokens
-23%
Agent turns
0%
Response time
-68%
Model gemini-3.6-flashMeasured 8/15/2026v117 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
What JSON data structure type is used to store discovered MCP server entries in `.cavekit/capabilities.json`?
What was checked, without and with the skill
Checked
Without skill
With skill
Formats mcp_servers as a JSON array of strings
Missed
Passed
case-22 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md68 linessingle file
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.