skill-finder
Skill1 starsChanged 32 days agoMITView on GitHub
Instructions for selecting skill files by lexical or fuzzy matching, with an optional configured model reranker. Use for ambiguous skill/tool choices and consult the arbitration table. This catalog supplies the files, not the search runtime. Not for per-project profiles or budget allocation.
26 other projects use a version of this.
Adopted by
Most recently taken up by
- milad-ahmd/agent-skillstheir own version, first seen Nov 8, 2026
- aktsmm/Agent-Skillstheir own version, first seen Nov 8, 2026
- omnigami-ai/skill-findertheir own version, first seen Nov 8, 2026
- c95tj48sd8-a11y/skill-findertheir own version, first seen Nov 8, 2026
- chinaretaildesign/agent-skillstheir own version, first seen Nov 8, 2026
- geekfujiwara/copilot-cowork-skillstheir own version, first seen Nov 1, 2026
Other versions26 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 26
- Affitor/affiliate-skills★ 757same name
- mizchi/skills★ 369same name
- aktsmm/Agent-Skills★ 26same name
- peter-tu-zynkr/zynkr-skill-builder★ 21same name
- ckorhonen/claude-skills★ 17same name
- geekfujiwara/copilot-cowork-skills★ 13same name
- kargnas/skills★ 9same name
- milad-ahmd/agent-skills★ 5same name
- robinbril/claude-code-harness★ 3same name
- sanyamk23/aphanis★ 3same name
16 more not listed
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.
In this repository114 other files it gives its agents.
- agent-cacheSkill
- agent-compressionSkill
- agent-intelSkill
- agent-overlapSkill
- agent-stateSkill
- ambient-hudSkill
- app-testSkill
- audit-dagSkill
- auto-distillSkill
- auto-memorySkill
- auto-routerSkill
- benchSkill
- bootstrapSkill
- botte-learnSkill
- botte-nnSkill
- botte-proxySkill
- botte-wrapSkill
- cacheSkill
- call-chainsSkill
- capabilitiesSkill
- cardinalSkill
- checkupSkill
- clarificationSkill
- clusterSkill
- code-complexitySkill
- code-duplicationSkill
- code-fingerprintSkill
- code-rulesSkill
- code-stateSkill
- code-wrappersSkill
- comfyuiSkill
- completion-proofSkill
- conductorSkill
- context-budgetSkill
- context-compressorSkill
- context-profilerSkill
- context-slicerSkill
- context-windowsSkill
- control-loopSkill
- cost-estimatorSkill
- dag-optimizerSkill
- dashboardSkill
- decision-ladderSkill
- demoSkill
- diff-languageSkill
- directives-auditSkill
- docgenSkill
- docs-stewardSkill
- dynamic-workflowsSkill
- efficiencySkill
- eventsSkill
- fallow-likeSkill
- fallowSkill
- fast-contextSkill
- fixSkill
- fleetSkill
- hailo-visionSkill
- harness-deltaSkill
- harvestSkill
- hermes-bridgeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Before adding a skill to a cluster, check that no listed member already covers the same trigger.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
skill-finder — local, zero-token skill & tool search
Package scope and prerequisites
This catalog ships instructions, not the executable runtime. Python modules, scripts, local services and optional tools named below must be installed separately from the upstream project. Check their availability before running commands; if they are missing, explain the prerequisite instead of claiming execution or results. The host agent may use model tokens while following these instructions.
Cluster arbitration — when two local skills look interchangeable
This table is authoritative for the clusters below. Load the named skill, not its neighbour, and treat the listed skill as out of scope for the other cases.
| Cluster | Use | Not for |
| compression | token_compressor for repeated token structure; universal_compressor for content types (text, JSON, logs, tool output, code); agent_compression for inter-agent wire format; ultra_compact for report JSON; token_shaper to choose the per-turn policy | any of these for deciding which skill to load |
| context | context_budget to allocate under a token budget; context_profiler to measure the prefix; context_slicer to split into typed slices; context_windows to carry loop deltas | prefix_pruner or prefix_tree for the same jobs |
| code audits | code_complexity (A1); code_duplication (A6); code_state (A2); code_wrappers (A3); code_fingerprint as the skip gate in front of them | code_fingerprint for findings — it only decides what to re-run |
| prompt | prompt_improver to rewrite a prompt; prompt_repetition (A8) to find wasted repeated prefixes | prompt_repetition for rewriting |
| prefix | prefix_pruner to delete never-used sections; prefix_tree to keep per-agent prefixes and diff | context_windows when the reuse unit is a loop step |
| skills | skill_finder for one query; skill_project_optimizer for a standing per-project profile | either for deleting dead context sections |
| cache | cache for a project scan reused by later agents; response_cache for a model answer keyed by question; agent-cache for a predictable agent run | code_fingerprint for the same job — it only skips unchanged files inside one audit |
| model routing | tiered_router for the 5-level cost ladder with auto-downgrade; nn_router for the complexity-driven tier; local_router for placing a task on local hardware by type | any of the three for choosing a tool — use tool_router |
| inter-agent transport | vector_protocol for embedding exchange inside a fixed pipeline; agent_compression for a binary message format with deltas | either for durable memory — use memory_hub |
| audit | code_complexity, code_duplication, code_state, code_wrappers for the five-field policy findings; fallow_like for the broad 9-analyzer pass; fallow for JS/TS | mousquetaires for producing the work, cardinal for attacking it |
| output style | caveman for telegraphic output levels; diff_language for change and finding notation; ultra_compact for report JSON | token_shaper for the per-turn policy decision |
Before adding a skill to a cluster, check that no listed member already covers the same trigger; if one does, extend that skill or its bounds instead.
Picking the right skill/tool for a task is retrieval, not reasoning — so it should not cost paid cloud tokens. This module does the search locally and leaves the cloud model free for the actual work.
Two tiers
- Tier 0 — lexical matching: lexical + fuzzy match over each skill's name, description, tags, triggers and full SKILL.md body. Deterministic.
- Tier 1 — optional configured model: for ambiguous queries, a local model (via [[llm-backends]]) re-ranks the shortlist. Still no cloud spend.
Use it
python -m skills.skill_finder.cli "optimize slow postgres queries"
python -m skills.skill_finder.cli "set up an A/B test" --local # local-LLM rerank
python -m skills.skill_finder.cli "audit dead code" --roots ~/.claude/skills --jsonfrom skills.skill_finder import find
r = find("decide local vs cloud routing", top_k=5)
r.get("cloud_tokens") # runtime-reported field; not total host usage
r["matches"] # [{name, score, why, description, path, tokens_est}, …]--roots points at any directory tree containing SKILL.md files (your global
skill library, a project's skills, etc.); defaults to this repo's skills/.
Works whether or not a SKILL.md has YAML frontmatter — the body is always indexed.
Evaluate a shortlist
Use the installed runtime to rank candidate instructions, then check that the selected workflows actually fit the task. Compare loaded context and outcome quality against a declared baseline. The host agent may still consume model tokens to choose and follow instructions; this catalog supplies no measured saving.
Exposed via [[llm-mcp]] as the find_skills tool. Related:
skill_project_optimizer (rule-based per-project filtering), auto_router.
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.

