find-a-plugin
Skill0 starsChanged 4 months agoMITView on GitHub
Find a Claude Code plugin for a task. Use whenever the user asks whether a plugin, skill or extension exists for something, asks what is available for a topic, or wants a recommendation from the community marketplace.
In this repositoryOne other file it gives its agents.
- browseSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Run shortlist find with the two or three most specific words from the request.
- Very specific: line 23
If nothing matches, try shortlist categories and browse the closest one rather than reporting nothing.
- Very specific: line 27
Use shortlist show <name> for the install command.
- Very specific: line 29
If a candidate is marked as failing, say so before recommending it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Answer from the local catalogue rather than guessing or searching the web. The
shortlist command is on PATH while this plugin is enabled.
shortlist find <words...> search names, descriptions and categories
shortlist categories every category and its size
shortlist browse <category> one category, most-starred first
shortlist show <name> one plugin in full, with the install command
shortlist top [n] the most-starred entries
shortlist broken entries that would not load, and whyUseful flags: --limit <n>, --min-stars <n>, --working, --json.
How to answer:
- Run
shortlist findwith the two or three most specific words from the request. Terms are ANDed, so fewer words match more. - If nothing matches, try
shortlist categoriesand browse the closest one rather than reporting nothing. - Show a few candidates with their star counts, not a single pick, and say plainly when the best match is weak.
- Use
shortlist show <name>for the install command. Do not invent one. showalso reports what the plugin provides and whether it passes the load checks. If a candidate is marked as failing, say so before recommending it.skill-no-descriptionin particular means the plugin installs without complaint and then never activates.
The catalogue is a filtered view of anthropics/claude-plugins-community. Entries
without a licence, archived repositories and repositories untouched for 180 days are
excluded, so an absence may mean "filtered out" rather than "does not exist". If the
user asks why something is missing, data/catalogue-rejected.json in this plugin's
directory records the reason for every exclusion.
Star counts describe popularity, not quality. Most of the catalogue has very few stars. Say so when a recommendation rests on a low number.
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
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.

