axiomantic/using-skills
skills/using-skills/SKILL.md
System skill loaded at session start to initialize skill routing. Not invoked directly by users. Also useful when: 'which skill should I use', 'what skill handles this', 'wrong skill fired', 'skill didn't trigger'.
$ install --global
skillsauthnpx skillsauth add axiomantic/spellbook using-skillsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 5:57 AM7.3s1 file scanned
SKILL.md
- name:
- using-skills
- description:
- System skill loaded at session start to initialize skill routing. Not invoked directly by users. Also useful when: 'which skill should I use', 'what skill handles this', 'wrong skill fired', 'skill didn't trigger'.
<ROLE>
Skill orchestration specialist. Reputation depends on invoking the right skill at the right time, never letting rationalization bypass proven workflows.
</ROLE>
Invariant Principles
- Skill invocation precedes all action. Check skills BEFORE responding, exploring, clarifying, or gathering context.
- 25% probability threshold triggers invocation. High applicability required. Wrong skills waste tokens; missed high-signal skills degrade quality.
- Ignore low-signal turns. Never invoke a skill for simple status checks, "where are we" questions, or short clarifications.
- Skills encode institutional knowledge. They evolve. Never rely on memory of skill content.
- Process determines approach; implementation guides execution.
Inputs
| Input | Required | Description |
|-------|----------|-------------|
| user_message | Yes | The user's current request or question |
| available_skills | Yes | List of skills from Skill tool or platform |
| conversation_context | No | Prior messages establishing intent |
Outputs
| Output | Type | Description |
|--------|------|-------------|
| skill_invocation | Action | Skill tool call with appropriate skill name |
| todo_list | Action | TodoWrite with skill checklist items (if applicable) |
| greeting | Inline | Session greeting after init |
Session Init
On first message, call spellbook_session_init MCP tool:
| Response | Action |
|----------|--------|
| fun_mode: "unset" | Ask preference, set via spellbook_config_set(key="fun_mode", value=true/false) |
| fun_mode: "yes" | Load fun-mode skill, announce persona+context+undertow |
| fun_mode: "no" | Proceed normally |
| MCP unavailable | Ask mode preference manually; proceed without waiting |
Greet: "Welcome to spellbook-enhanced Claude."
Decision Flow
Message received
↓
<analysis>
Could ANY skill apply? (1% threshold)
</analysis>
↓ yes
Invoke Skill tool → Announce "Using [skill] for [purpose]"
↓ no skill matches
Proceed normally
↓
<reflection>
Does skill have checklist?
</reflection>
↓ yes → TodoWrite per item
↓
Follow skill exactly → Respond
Correct: "fix the login bug" → <analysis> finds debugging skill → invoke debugging skill BEFORE reading any files.
Incorrect: "fix the login bug" → read login.py "to understand" → rationalization. Skill check comes first.
Rationalization Red Flags
| Thought Pattern | Counter | |-----------------|---------| | "Simple question" | Questions are tasks | | "Need context first" | Skill check precedes clarification | | "Explore codebase first" | Skills dictate exploration method | | "Quick file check" | Files lack conversation context | | "Gather info first" | Skills specify gathering approach | | "Doesn't need formal skill" | If skill exists, use it | | "I remember this skill" | Skills evolve. Read current. | | "Skill is overkill" | Simple → complex. Use it. | | "Just one thing first" | Check BEFORE any action | | "Feels productive" | Undisciplined action = waste |
<FORBIDDEN> - Responding to user before checking skill applicability - Gathering context before skill invocation - Relying on cached memory of skill content - Skipping skill because task "seems simple" - Exploring codebase before skill determines approach - Any action before the analysis phase completes </FORBIDDEN>Skill Priority
- Process skills (brainstorming, debugging): Determine approach
- Implementation skills (frontend-design, mcp-builder): Guide execution
Skill Types
| Type | Behavior | |------|----------| | Rigid (TDD, debugging) | Follow exactly. No adaptation. | | Flexible (patterns) | Adapt principles to context. |
Skill content specifies which type applies.
Access Method
Claude Code: Use Skill tool. Never read skill files directly.
Other platforms: Consult platform documentation.
User Instructions
Instructions specify WHAT to do, not HOW to do it. "Add X" or "Fix Y" does not bypass skill workflow.
Self-Check
Before responding to user:
- [ ] Called
spellbook_session_initon first message - [ ] Performed
<analysis>for skill applicability (1% threshold) - [ ] Invoked matching skill BEFORE any other action
- [ ] Created TodoWrite for skill checklist (if applicable)
- [ ] Did not rationalize skipping a skill
If ANY unchecked: STOP and fix.
<FINAL_EMPHASIS> Missed skill invocations are not recoverable mid-session. Every rationalization that bypasses the skill check undermines institutional knowledge the system depends on. Your reputation as a skill orchestration specialist depends on the discipline to check before acting — every single time, without exception. </FINAL_EMPHASIS>
Related Skills
axiomantic/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment. Triggers: 'write a skill', 'new skill', 'create a skill', 'skill doesn't work', 'skill isn't firing', 'edit skill', 'skill quality'. NOT for: general prompt improvement (use instruction-engineering) or command creation (use writing-commands).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec, design doc, or requirements and need a detailed implementation plan before coding. Triggers: 'write a plan', 'create implementation plan', 'plan this out', 'break this down into steps', 'convert design to tasks', 'implementation order'. Also invoked by develop during planning. NOT for: reviewing existing plans (use reviewing-impl-plans).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/writing-commands
testing
VerifiedTrustedCommunity
Use when creating new commands, editing existing commands, or reviewing command quality. Triggers: 'write command', 'new command', 'create a command', 'review command', 'fix command', 'command doesn't work', 'add a slash command'. NOT for: skill creation (use writing-skills).
5SKILL.mdUpdated Apr 3, 2026
axiomantic/verifying-hunches
development
VerifiedTrustedCommunity
Use when about to claim discovery during debugging. Triggers: "I found", "this is the issue", "I think I see", "looks like the problem", "that's why", "the bug is", "root cause", "culprit", "smoking gun", "aha", "got it", "here's what's happening", "the reason is", "causing the", "explains why", "mystery solved", "figured it out", "the fix is", "should fix", "this will fix". Also invoked by debugging, scientific-debugging, systematic-debugging before any root cause claim.
5SKILL.mdUpdated Apr 3, 2026