The skill you invoke when you don't know which skill to invoke.
autoskill is a meta-skill for Claude Code that acts as an intelligent router. Instead of memorizing which specialized skill handles which kind of task, you describe your problem and autoskill figures out the right skills to apply — scoring every available skill, auto-applying the best matches, and letting you approve borderline ones.
Claude Code ships with a large and growing library of specialized skills: security reviewers, TDD guides, frontend pattern libraries, database reviewers, deployment helpers, and more. Knowing which one to reach for — and in what combination — adds cognitive overhead to every task.
autoskill removes that overhead. It reads your problem, scans the live skill list, scores each skill on four criteria, and invokes the top matches automatically. You get the right expert for the job without having to know who that is.
When you run /autoskill, it executes a six-phase pipeline:
Reads your description (or infers it from the current conversation) and builds a structured context profile: problem statement, action intent, language/stack, domain tags, and keywords.
Scans the live skill list already in Claude's context — no slow file reads. Groups all skills into domain buckets (testing, security, frontend, backend, database, deployment, etc.) and builds a candidate list relevant to your domains.
Scores every candidate skill 0–100 using a weighted rubric:
| Criterion | Weight | What it checks |
|---|---|---|
| Intent match | 35% | Does the skill's purpose match what you want to do? (fix / create / review / deploy / etc.) |
| Domain match | 30% | Does the skill apply to the relevant domain? (security, testing, frontend, database, etc.) |
| Keyword overlap | 20% | How many of your problem's keywords appear in the skill name or description? |
| Stack match | 15% | Does the skill target your detected language or framework? |
Score thresholds:
- ≥ 70 — recommended, shown in the execution plan
- 40–69 — suggested, you decide whether to include
- < 40 — skipped silently
Every run shows the full proposed execution plan and asks for your explicit approval before invoking anything. There are no exceptions — even a single recommended skill requires confirmation. You can remove any skill from the queue before proceeding.
Runs approved skills one at a time in score order. Each skill may change project state that the next one depends on, so execution is always sequential. Blocked or context-starved skills are noted but don't abort the rest.
Prints a full table showing every skill that was considered, its score, whether it was applied or skipped, and why. Nothing is hidden.
Claude Code
/install autoskill
Cursor
@autoskill
Or open Cursor Settings → MCP / Skills → Add Skill → search autoskill.
OpenClaw
npx clawhub@latest install autoskillbash autoskill/install.shRestart Claude Code (or start a new session) to pick up /autoskill.
After install:
- Skill definition →
~/.claude/skills/autoskill/SKILL.md - Slash command →
~/.claude/commands/autoskill.md
rm -rf ~/.claude/skills/autoskill
rm -f ~/.claude/commands/autoskill.md/autoskill fix the login crash on empty password
/autoskill add unit tests for the payment module
/autoskill review my PR before I merge
/autoskill refactor the auth module to use the repository pattern
/autoskill # infers from the current conversation
Pass a problem description as the argument, or omit it and autoskill synthesizes from recent messages, open files, and tool call context.
CONTEXT PROFILE
───────────────
Problem: Fix login crash when password field is empty
Intent: fix
Stack: typescript
Domains: security, backend, api
Keywords: login, crash, password, empty, authentication
Found 12 candidate skills in relevant buckets.
SKILL SCORING
──────────────────────────────────────────────────────────────
Skill Score Tier Reason
─────────────────── ───── ─────────── ──────────────────────
security-review 88 RECOMMENDED fix intent + security domain + keyword=auth
investigate 82 RECOMMENDED fix intent + keyword=crash
typescript-reviewer 75 RECOMMENDED stack=typescript, code-quality domain
code-review 72 RECOMMENDED review intent match
tdd-workflow 48 SUGGEST testing domain, weak intent match
──────────────────────────────────────────────────────────────
RECOMMENDED: 4 skills | SUGGEST: 1 skill | SKIP: 7 skills
** autoskill recommends 4 skills for: "Fix login crash when password field is empty" **
These skills will run only after you confirm below:
Recommended (score ≥70):
- `security-review` — fix intent + security domain
- `investigate` — fix intent + keyword=crash
- `typescript-reviewer` — stack=typescript
- `code-review` — review intent match
Also applicable — want any of these?
- `tdd-workflow` [SUGGEST] — testing domain, weak intent match
Actions:
- Type the names of any suggested skills you want to add
- Type "none" to run only the recommended skills
- Type "cancel" to stop and do nothing
→ Applying `security-review` (score: 88) — fix intent + security domain
[security-review output...]
→ Applying `investigate` (score: 82) — fix intent + crash keyword
[investigate output...]
## autoskill Run Complete
| Skill | Score | Tier | Applied | Outcome | Reason |
|--------------------|-------|-------------|---------|-----------|----------------------------------|
| security-review | 88 | RECOMMENDED | ✅ | completed | fix intent + security domain |
| investigate | 82 | RECOMMENDED | ✅ | completed | fix intent + keyword=crash |
| typescript-reviewer| 75 | RECOMMENDED | ✅ | completed | stack=typescript |
| code-review | 72 | RECOMMENDED | ✅ | completed | review intent match |
| tdd-workflow | 48 | SUGGEST | ⏸ | skipped | user declined |
Summary: 4 skills applied, 1 skipped, 0 blocked.
autoskill is designed to route to other skills automatically. Before installing, be aware of how it handles high-impact actions:
Mandatory execution preview. Every single run shows the full proposed execution plan and asks for your explicit confirmation before invoking anything. There are no exceptions — even one recommended skill requires approval. You can remove any skill from the queue at that point, or type cancel to abort entirely.
High-risk skill gate. Skills that deploy, send messages, modify data, charge accounts, or access broad shell/file scope (e.g. ship, database-migrations, customer-billing-ops, github-ops, email-ops) are never automatically included — they always appear as optional suggestions marked [HIGH-RISK], regardless of their score. A keyword heuristic also catches newly added skills with dangerous descriptions even if they are not in the fixed registry.
Preamble transparency. The Bash preamble that runs at startup only inspects local git state and project config files (package.json, go.mod, etc.). It does not modify files, run project code, or send data externally.
Persistent install. The installer adds a skill and slash command to ~/.claude/. They remain available in future sessions until you uninstall them (see Uninstall above).
- No hardcoded skill assumptions. The candidate list is always derived from the live system-reminder, so new skills are automatically included without any changes to autoskill itself.
- No bulk file reads. The in-context skill list is sufficient for scoring. autoskill only reads a specific SKILL.md when it needs invocation details for an edge case.
- Max 5 auto-applied skills. Prevents runaway chaining on broad problem statements.
- Sequential execution. Skills run one at a time. Each may change project state that the next depends on.
- Graceful degradation. If the Skill tool is unavailable, autoskill prints the scored table and tells you which skills to invoke manually.
autoskill/
├── SKILL.md # Full skill definition (the six-phase pipeline)
└── install.sh # Copies skill + slash command into ~/.claude/
scripts/
└── publish_to_clawhub.sh # Maintainer script for ClawHub releases