agentleFS
KarimJebaraKarimJebara/Curator/.claude/skills/curator/SKILL.md

curator

Skill8 starsChanged 7 months agoMITView on GitHub

Audit and curate the user's Claude Code skills and MCP servers. Detects overlapping clusters, proposes specialization/deletion, and generates router skills. Use when the user asks to clean up their setup, reduce token bloat, or has too many skills covering similar ground.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Quarktex/qcobrain★ 4same name
    2. yuntao1122/ai-media-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When invoked, run the curator audit on the user's ~/.claude/ setup and walk them through the findings.

    line 8
  2. Very specific:

    Run the scan via Bash: npx -y @curator/cli scan.

    line 12
  3. Very specific:

    Run the interactive review: npx -y @curator/cli review.

    line 13
  4. Very specific:

    If the user prefers to discuss before running the interactive prompt, read ~/.claude/curator/reports/latest.md, summarize …

    line 14
  5. Distinctive:

    Never apply actions without explicit user confirmation per action.

    line 24
  6. Very specific:

    Never delete a skill that has unique vocabulary or examples not covered elsewhere — even if curator suggested it.

    line 25
  7. Very specific:

    Never modify the report's structure when checking boxes.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

curator

When invoked, run the curator audit on the user's ~/.claude/ setup and walk them through the findings.

How to use

  1. Run the scan via Bash: npx -y @curator/cli scan.
  2. Run the interactive review: npx -y @curator/cli review. The CLI walks the user cluster-by-cluster with PASS actions pre-selected and WARN/FAIL pre-skipped — let the user drive that flow themselves.
  3. If the user prefers to discuss before running the interactive prompt, read ~/.claude/curator/reports/latest.md, summarize cluster-by-cluster, and surface verifier WARN/FAIL notes prominently. Then either edit the markdown file to check boxes (and run curator review --report --apply) or hand off to the interactive prompt.

What to flag

  • Clusters with mean similarity above 70% — those are usually true duplicates.
  • Skills with version-drift suffixes (-v2, -enhanced, etc.) — almost always safe to delete.
  • MCP servers consuming more than 1500 tokens individually — high-value targets for removal or scoping.

What NOT to do

  • Never apply actions without explicit user confirmation per action.
  • Never delete a skill that has unique vocabulary or examples not covered elsewhere — even if curator suggested it.
  • Never modify the report's structure when checking boxes; only flip [ ] to [x].

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.