| name | skillfind |
| description | Use before writing a new skill, before saying no skill exists for something, or whenever Wes asks "do I have a skill for X" / "is there a skill that…". Also use when a task sounds like it needs a capability that might already be installed (spreadsheets, PDFs, docx, scraping, copywriting, a framework, a provider) — most of this machine's skills are NOT in the session listing, so "I don't see one" is not evidence that none exists. |
skillfind — most of your skills are invisible
389 unique skills live on this machine. Only 211 load into a session.
178 are on disk and invisible to every session: stale plugin version
directories, the skills of 19 disabled plugins, project-scoped installs,
skills-archive, and 16 cloned marketplaces whose plugins were never installed.
So the skill listing in your context is roughly half the truth. Not finding
something there means nothing. Search before you conclude.
Not the same as find-skills
They trigger on similar words and do opposite things. Always run this one
first, because installing something Wes already owns is pure waste.
| searches | installs? | network |
|---|
| skillfind (this) | what is already on the machine | never | never |
find-skills | the public ecosystem via npx skills / skills.sh | yes | yes |
Local first. Only reach for find-skills once skillfind has come back empty.
The command
node ~/.claude/tools/skillfind/skillfind.cjs "<query>"
Query it the way you would describe the task, not with a guessed skill name.
The scoring runs over each skill's , and descriptions are written
to match task language. works; does not.
