Agent Development / AGENT SKILL

skill-search

0 installs 2 GitHub stars

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.

One new superpower.

Run this command in your project to choose an agent and install the skill.

npx skillycli add https://github.com/thinhkhuat/skill-concierge --skill skill-searchView original source

BEFORE YOU INSTALL

Understand the trade-offs.

SECURITY REVIEW

Not yet assessed

Review the original instructions and requested permissions before installing.

No security review is available for this catalog entry yet.

SKILL QUALITY

Not yet assessed

How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.

No quality assessment is available for this catalog entry yet.

The full skill.

Original instructions from the publisher’s SKILL.md

# 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:
1. Read the returned names + descriptions. Each row also carries `origin` (which harness's
   roots hold the copy) and, when present, `disabled_in`. A row whose `disabled_in` names your
   harness is not a hit. Otherwise: a skill your harness lists is invoked by name; one it does not
   list is loaded with `get_skill(name)` and followed inline.
2. Invoke the genuinely relevant ones by name (e.g. /frontend-design).
3. Ignore low-score results — do not load skills that aren't relevant.
4. 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.