From skill-development
Discovers and loads skills on demand from a local catalog. Use when you need a capability but don't know which skill provides it, or to list/search/show skill metadata.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skill-development:finding-skillsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Skills on disk at `/mnt/skills/user/` are a catalog — too expensive to preload as descriptions in every session's context. This skill is the on-demand accessor, analogous to Anthropic's ToolSearch for MCP tools.
Skills on disk at /mnt/skills/user/ are a catalog — too expensive to preload as descriptions in every session's context. This skill is the on-demand accessor, analogous to Anthropic's ToolSearch for MCP tools.
PY=/home/user/.spokes/claude-skills/finding-skills/scripts/skills.py
# List every skill by name (cheap, ~1.4KB)
python3 "$PY" list
# Search by keyword — ranks name matches above description matches
python3 "$PY" search "adversarial review"
# Load the full SKILL.md of a specific skill
python3 "$PY" show challenging
In a live CCotw session the script lives at /mnt/skills/user/finding-skills/scripts/skills.py.
search <keywords>show <name>listsearch "<what you want to do>" — get 3–10 ranked candidatesshow <top-pick> — read its SKILL.mdscripts/, references/, etc.)Stop at step 1 if none of the candidates fit — don't shoehorn an unrelated skill onto the task.
Case-insensitive throughout. Results sorted high-to-low, ties broken by name.
list: one skill name per linesearch: tab-separated <name>\t<description (truncated to 200 chars)>, one per lineshow: raw SKILL.md contents to stdout; exit 1 with a stderr message if not foundAll three are line-oriented so they compose with grep, head, etc.
npx claudepluginhub oaustegard/claude-skills --plugin skill-developmentCreates, edits, and verifies skills using a test-driven development approach with pressure scenarios and subagents.