Stop guessing which agent skill to use.

skill-manager knows what you have installed, which skill fits the task, and what is broken or duplicated.

find-skills, by Vercel Labs

The shop.

Searches skills.sh for skills you do not have yet, ranked by popularity.

skill-manager

The inventory.

Works on what you already have, and hands off to find-skills when something is missing. Use them together.

Answers the questions you actually ask.

Short answers by default, one line per skill. Ask about a specific skill and you get the full explanation.

See what you have

Every skill across Claude Code, Codex, Cursor, OpenCode and Windsurf folders, grouped by area, with what each one is for.

"What skills do I have?"

Pick the right one

Which of your skills fit the task, in the order you would use them, and what is missing. Then it steps aside and the chosen skill runs exactly as written.

"Which skills for a REST API with JWT?"

Spot overlap

Duplicates, partial overlaps and complementary skills. You decide what to remove.

"Do I need all these?"

Find broken installs

Broken links, invalid SKILL.md files, name collisions, skills installed for another agent.

"Are my skills OK?"

Know when to search

Nothing fits? It says so, and points you to find-skills with a search term.

"Do I have anything for OAuth?"

Works without an agent too

The inventory script is read-only and dependency-free. Run it in any terminal with Node 18+.

node inventory.mjs --issues --text

Same model, same question.

Answers from our test runs with Claude Opus 5, with and without the skill. Shortened and translated from Portuguese; nothing added.

> which skills do I have installed? I forgot what half of them do
Without the skill
You have 10 skills in ~/.claude/skills:
backend-development | General backend reference: APIs,
  databases, auth, security, caching, microservices...
...
Notes:
- grill-me and grilling do the same thing. You can delete
  that folder and lose nothing.
- This project has no skills of its own in .claude/skills/.
  • Missed find-skills, installed in another agent's folder
  • Missed 9 broken skill links, said the project had none
  • Suggested deleting a shortcut that is working as intended
With skill-manager
Engineering
✓ diagnosing-bugs  diagnosis loop for hard bugs
✓ grilling  stress-tests a plan with hard questions
  ↳ grill-me  manual shortcut that runs grilling
Database (this project only)
• prisma-cli  Prisma CLI commands reference
...
✓ = this agent can load it   • = installed for another agent

⚠ 18 issues, mostly Prisma links saved as text files.
  Ask me for a health check to see how to fix them.
  • Scanned every agent folder, found all 20 skills
  • Flagged the broken installs without being asked
  • Explained the shortcut instead of calling it a duplicate

What changed in testing.

Seven test prompts, each answered with and without the skill, checked against 5 to 11 written criteria.

100% vs 76%

Criteria met with the skill, compared with the same model on its own.

+2.4k tokens

Average extra tokens per answer, after trimming the skill and its script output.

33s vs 37s

Average time per answer. The read-only script replaces folder-by-folder reads.

List installed skills38% → 100%
No skills installed yet57% → 100%
Too many frontend skills80% → 100%
Missing skill for a task83% → 100%
Explain one skill in depth86% → 100%
Health check, broken fixtures91% → 100%
Health check, real setup100% → 100%
Read these numbers as indicative. One run per prompt per configuration, on Claude Opus 5 in Claude Code, graded by the skill's author. The model alone already does well when asked directly, as the health checks show. The skill's value is consistency: it scans every agent folder every time, does not invent skills, and does not push you to delete things. Prompts and fixtures are in the repo, so you can rerun them.

Install once. Call it by name.

Add the skill

Uses the skills CLI, which installs into any supported agent.

npx skills add SWAGGATH4K1NG/skill-compass --skill skill-manager

Make it trigger on its own

Agents often answer "what skills do I have?" from memory. One line in your AGENTS.md or CLAUDE.md fixes that.

## Skills
When I ask about my agent skills (what I have, what one does,
which to use, whether one is missing or redundant, or whether
they are installed correctly), use the skill-manager skill.

Or start it explicitly

The most reliable way, in whichever agent you use.

Claude Code/skill-manager
Codex$skill-manager or pick it from /skills
Cursor/skill-manager
Windsurf@skill-manager
OpenCodeMention it: "use the skill-manager skill"

A guide, not another layer in the way.

Recommends, then steps aside

The skill you pick runs exactly as its author wrote it. Nothing is summarised, skipped or shortened.

Read-only

It never installs, removes or edits anything. You get the command and run it yourself.

Treats skill files as data

Instructions hidden in a third-party SKILL.md are flagged, never followed.

No agent lock-in

Follows the open Agent Skills format. No agent-specific paths or commands assumed.