claude-code-skills

name: claude-code-skills description: "Use when you need to understand, create, trigger, or debug Claude Code skills—reusable workflows defined in SKILL.md files with YAML frontmatter." user-invocable: true

Claude Code Skills

A skill = a workflow saved in SKILL.md with YAML frontmatter that Claude loads on demand and applies when relevant.

Core Concepts

• SKILL.md: Required markdown file with YAML frontmatter (name, description) + markdown body (instructions). Lives in ~/.claude/skills/<name>/, .claude/skills/<name>/, or plugin skills/<name>/.
• Frontmatter: YAML block between --- markers. description is how Claude decides when to use the skill (recommended). Other fields: disable-model-invocation, user-invocable, allowed-tools, disallowed-tools, model, effort, context, agent, paths, shell, argument-hint, arguments.
• Invocation: Type /skill-name to invoke manually, or Claude loads it automatically when relevant. Plugin skills use namespace: /plugin-name:skill-name.
• Content lifecycle: When invoked, the rendered SKILL.md enters the conversation as a single message and stays for the rest of the session. Claude Code does NOT re-read the file on later turns. Auto-compaction carries skills forward; after compaction, the most recently invoked skill keeps the first 5,000 tokens.

Quick Skill Creation

File structure:

~/.claude/skills/my-skill/
├── SKILL.md (required)
├── scripts/ (optional, for executables)
└── references/ (optional, detailed docs)

Minimal SKILL.md template:

---
description: Use when [trigger condition]. [Concrete signals].
---

## Instructions

[Markdown body with step-by-step instructions.]

Triggering: The description field is the trigger. Write it to start with "Use when..." and name concrete signals (e.g., "Use when the user asks about changes, wants a commit message, or asks to review their diff"). Combined description + optional when_to_use text is capped at ~1,536 characters; put the key use case first.

Frontmatter Fields Reference

Dynamic Context Injection

Inject live data into the prompt using !`command` (inline) or ```! (multi-line) blocks. Commands run BEFORE Claude sees the skill—output replaces the placeholder:

Inline:

Current changes: !`git diff HEAD`

Multi-line:

```!
git status --short
npm --version
```

Command output is plain text. Substitution runs once; output is NOT re-scanned for further placeholders.

String Substitutions in Skill Body

To escape a literal $ before a digit (e.g., $1.00), use \$.

Where Skills Live (Resolution Order)

Enterprise overrides personal, personal overrides project. Plugin skills don't conflict.

Limiting Skill Visibility

Prevent auto-trigger without disabling the skill:

disable-model-invocation: true  # Only you can invoke manually (/my-skill)

Hide from / menu (Claude only):

user-invocable: false  # Hidden from menu; Claude can still invoke if relevant

Default behavior: Both you and Claude can invoke any skill unless one of the above is set.

Control with settings.json

Override individual skill visibility in skillOverrides (persists in settings, not in SKILL.md):

{
  "skillOverrides": {
    "legacy-context": "name-only",    // Show name only, no description
    "deploy": "off"                    // Hide completely
  }
}

Values: "on" (full), "name-only", "user-invocable-only" (hidden from menu but invocable), "off".

Creating the Skill vs. Editing It

• Live change detection: Skills in ~/.claude/skills/, .claude/skills/, or --add-dir directories reload automatically mid-session when SKILL.md is edited. Creating a NEW skills directory requires restarting.
• For plugin skills (with hooks, agents, MCP servers), reload with /reload-plugins.
• Working tree edits: If a skill is installed via npx skills add, edits to the source repo do NOT auto-propagate. Re-run npx skills add . -g -y or symlink the working tree to ~/.claude/skills/<name>/ for live editing.

Supporting Files & Progressive Disclosure

Keep SKILL.md under 500 lines. Move detailed reference docs to separate files:

my-skill/
├── SKILL.md (overview & navigation)
├── reference.md (full API docs, loaded on demand)
├── examples.md (usage examples, loaded on demand)
└── scripts/validate.sh (executable, not loaded)

Reference from SKILL.md:

## Additional resources
- For complete API details, see [reference.md](reference.md)
- For usage examples, see [examples.md](examples.md)

Claude loads supporting files only when you ask for them—they don't cost context until invoked.

Common Patterns

Manual-invoke only (deploy, send-message):

---
name: deploy
description: Deploy to production
disable-model-invocation: true
---
Deploy to $ARGUMENTS with safeguards: ...

Background knowledge (Claude only, not a command):

---
name: legacy-system-context
description: How the old auth system works
user-invocable: false
---
The legacy system uses... [reference material]

Auto-grant tools (reduce approval prompts):

---
name: commit
allowed-tools: Bash(git add *) Bash(git commit *) Bash(git status *)
---
Stage and commit changes...

Isolated subagent task:

---
name: deep-research
description: Research a topic thoroughly
context: fork
agent: Explore
---
Research $ARGUMENTS thoroughly...

Troubleshooting

When to Create a Skill

• You keep pasting the same instructions, checklist, or multi-step procedure into chat.
• A section of CLAUDE.md has grown into a workflow rather than a fact.
• You want Claude to recognize a specific trigger phrase and auto-load guidance.
• You need to control timing (deploy, send-message) → use disable-model-invocation: true.
• You bundle scripts or supporting docs alongside instructions.