finding-skills
Finding Skills
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.
Usage
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.
When to reach for this
- You have a task where a skill might help but no obvious name comes to mind →
search <keywords> - The boot emitted names-only and you want the description of a candidate →
show <name> - You want catalog breadth before picking an approach →
list
Pattern
search "<what you want to do>"— get 3–10 ranked candidatesshow <top-pick>— read its SKILL.md- Follow the SKILL.md's instructions (which may point at
scripts/,references/, etc.)
Stop at step 1 if none of the candidates fit — don't shoehorn an unrelated skill onto the task.
Ranking
- Exact match on skill name: 100
- Substring match on skill name: 10
- Substring match in description: 1 per match (multiple hits compound)
Case-insensitive throughout. Results sorted high-to-low, ties broken by name.
Output format
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 found
All three are line-oriented so they compose with grep, head, etc.
More from oaustegard/claude-skills
developing-preact
Specialized Preact development skill for standards-based web applications with native-first architecture and minimal dependency footprint. Use when building Preact projects, particularly those involving data visualization, interactive applications, single-page apps with HTM syntax, Web Components integration, CSV/JSON data parsing, WebGL shader visualizations, or zero-build solutions with vendored ESM imports.
104reviewing-ai-papers
Analyze AI/ML technical content (papers, articles, blog posts) and extract actionable insights filtered through enterprise AI engineering lens. Use when user provides URL/document for AI/ML content analysis, asks to "review this paper", or mentions technical content in domains like RAG, embeddings, fine-tuning, prompt engineering, LLM deployment.
79exploring-codebases
>-
63mapping-codebases
Generate navigable code maps for unfamiliar codebases. Extracts exports/imports via AST (tree-sitter) to create _MAP.md files per directory showing classes, functions, methods with signatures and line numbers. Use when exploring repositories, understanding project structure, analyzing unfamiliar code, or before modifications. Triggers on "map this codebase", "explore repo", "understand structure", "what does this project contain", or when starting work on an unfamiliar repository.
49accessing-github-repos
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
43asking-questions
Guidance for asking clarifying questions when user requests are ambiguous, have multiple valid approaches, or require critical decisions. Use when implementation choices exist that could significantly affect outcomes.
41