| name | skill-search |
| description | Find the right skills for a task before acting. Use at the start of any multi-step or unfamiliar request to retrieve relevant skills by meaning, not name. Triggers when the user asks to build, set up, design, deploy, fix, or automate something and the right skill isn't obvious. |
| license | MIT |
| compatibility | Requires the skill-search MCP server (provides the search_skills tool) registered in Claude Code. See https://github.com/sowhan/skill-search |
| metadata | {"author":"Sowhan Mohammed","version":"0.1.0","mcp-server":"skill-search"} |
skill-search
Before tackling this task, call the search_skills MCP tool with a short query
describing the user's goal. It returns ranked skills by semantic relevance.
Then:
- Read the returned names + descriptions.
- Invoke the genuinely relevant ones by name (e.g. /frontend-design).
- Ignore low-score results — do not load skills that aren't relevant.
- If a result looks promising but the description is thin, call
get_skill
on it before deciding.
Prefer 2-4 high-relevance skills over loading many. Precision keeps context lean.
