skill-finder

Skill Finder

The skills-atlas CLI searches and installs AI agent skills from the Skills Atlas catalog — hundreds of skills across 100+ source repositories, organized by function.

Grounding rules (must follow)

Treat the skills-atlas CLI as the only source of truth. The catalog — not your training data — defines which skills exist, who publishes them, and how to install them.

• Before naming or recommending any skill, run skills-atlas search "<query>" --json (or skills-atlas info "<skill>" --json) and recommend only skills that appear in that output.
• Never invent skill names, repos, star counts, or install commands. Quote them verbatim from the JSON: the skill name, sources[].id / url, the install command, the use_case / when_to_use.
• If search returns no matches, say so and propose different queries — do not fall back to skills you "know" from elsewhere.
• To install, always go through skills-atlas install <skill> --yes. The CLI installs only catalog skills; a name that isn't in the catalog returns not found with suggestions — relay those instead of guessing.
• If results look stale or a skill seems missing, run skills-atlas update first, then search again.

Commands (add --json whenever you parse the output)

• Search: skills-atlas search "<query>" --json — filters: -c <category>, -p <persona>, -t <type>, --chain
• Details: skills-atlas info "<skill>" --json
• Install: skills-atlas install "<skill>" --yes — --global (default → ~/.claude/skills/) or --project (→ ./.claude/skills/); add --force to overwrite
• Refresh: skills-atlas update (refresh the local catalog from the public feed)

How to help

1. Turn the user's need into a short search query (plus filters), run search, and present the top matches from the JSON — what each does and its exact install command.
2. On request, install with skills-atlas install <skill> --yes. If a skill has several sources, the CLI auto-picks the best installable one; pass --source <id> to choose.
3. Some sources have no per-skill folder (marketplace / CLI-framework types). For those, the CLI prints the exact whole-repo install command — relay it instead of assuming the install failed.
4. After a successful install, tell the user to start a new Claude Code session to load the skill, then invoke it by name.

Skills install into <target>/.claude/skills/<skill>/. This requires the skills-atlas-cli package on PATH (npm i -g skills-atlas-cli, or npm link in the package directory for local development before it is published).