01
What this skill does
Use this skill when an agent needs to inspect available local skills before planning, routing, or implementing a request. It decomposes the ask into deliverables, workflow phases, tools, domains, and implicit prerequisites, then combines session skill metadata with a bundled local scanner for plain project skills folders, Cursor, Claude Code, OpenCode, Codex, shared Agent Skills roots, and plugin skill caches before loading only the skill bodies that materially affect the task.
02
When to use it
- 01Finding relevant local skills before requirement analysis, planning, or implementation.
- 02Routing ambiguous or multi-phase requests through explicit skill selection instead of relying on memory.
- 03Surfacing prerequisite skills that are implied by a deliverable, tool, or workflow phase.
- 04Auditing available skill coverage across plain project skills folders, Cursor, Claude Code, OpenCode, Codex, and shared Agent Skills roots.
- 05Distinguishing plugin skills with names such as product-design:index.
03
How it works
- 01
Decompose the request into explicit asks, deliverables, artifacts, tools, workflow phases, and implicit prerequisites.
- 02
Inventory skills already present in session context before reading any additional skill bodies.
- 03
Run the bundled local scanner when filesystem access is available, including supported user, project, and plugin roots.
- 04
Run focused supplemental searches for individual facets or tight synonym groups after the broad inventory.
- 05
Compare the request against skill names, namespaced plugin names, descriptions, explicit mentions, tools, file types, products, domains, workflow cues, and decomposed prerequisites.
- 06
Select only skills that materially change how the work should be done.
- 07
Apply the selected skill workflows in dependency order, then continue with the requested analysis or implementation.
04
What you get back
- 01A brief skill-selection summary with one reason for each selected skill.
- 02The requested analysis, plan, implementation guidance, or work product using the selected workflows.
- 03A clear note when no suitable local skill was found.
05
Important boundaries
- 01Do not start solution analysis before the decomposition, inventory, and selection pass is complete.
- 02Do not load unrelated skill bodies.
- 03Do not narrow with a query until after the first broad inventory pass.
- 04Do not put unrelated decomposition facets into one long scanner query because the scanner matches all query terms.
- 05Prefer namespaced plugin entries over generic names when both could match the request.
06