Skills Best Practices

Comprehensive reference for building Agent Skills that follow Anthropic's official guidelines. Skills are folders containing instructions, scripts, and resources that teach Claude how to handle specific tasks. They follow the Agent Skills open standard.

Quick Start

A minimal skill is a directory with a

SKILL.md

my-skill/
├── SKILL.md          # Required - instructions with YAML frontmatter
├── references/       # Optional - detailed docs loaded on demand
├── scripts/          # Optional - executable code
└── assets/           # Optional - templates, fonts, icons

Minimal

SKILL.md

---
name: my-skill-name
description: What it does. Use when [specific triggers].
---

# My Skill Name

[Instructions here]

Only

name

description

Core Design Principles

Progressive Disclosure (Most Important)

Skills load information in three levels to minimize token usage:

name

description

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

## Advanced features
- **Form filling**: See [FORMS.md](FORMS.md)
- **API reference**: See [reference.md](reference.md)

Claude reads referenced files only when the task requires them.

Composability

Skills work alongside other skills. Don't assume yours is the only one loaded.

Portability

Skills work across Claude.ai, Claude Code, API, and Agent SDK without modification (if dependencies are available).

Writing the Description (Critical)

The description is the single most important field - it determines when your skill activates. Claude uses it to decide relevance from potentially 100+ available skills.

Rules

• Write in third person ("Processes files..." not "I help you process files...")
• Include WHAT it does + WHEN to use it
• Max 1024 characters, no XML angle brackets
• Be slightly "pushy" - Claude tends to undertrigger rather than overtrigger
• Include specific trigger phrases users would naturally say

Good vs Bad

# GOOD - specific, actionable, includes triggers
description: Extract text and tables from PDF files, fill forms, merge
  documents. Use when working with PDF files or when the user mentions
  PDFs, forms, or document extraction.

# BAD - too vague
description: Helps with documents.

# BAD - missing triggers
description: Creates sophisticated multi-page documentation systems.

More examples in references/description-guide.md.

Frontmatter Reference

Required Fields

name

description

Optional Fields (Claude Code)

argument-hint

[issue-number]

disable-model-invocation

true

user-invocable

false

/

allowed-tools

Read, Grep, Glob

model

effort

low

medium

high

max

context

fork

agent

context: fork

Explore

Plan

paths

Naming Conventions

Prefer gerund form for clarity:

• processing-pdfs

  ,

  analyzing-spreadsheets

  ,

  managing-databases

• Also acceptable:

  pdf-processing

  ,

  process-pdfs

• Avoid:

  helper

  ,

  utils

  ,

  tools

  ,

  documents

Structuring Instructions

Be Concise

Claude is smart. Only add context it doesn't already have:

# GOOD (~50 tokens)
## Extract PDF text
Use pdfplumber for text extraction:
```python
import pdfplumber
with pdfplumber.open("file.pdf") as pdf:
    text = pdf.pages[0].extract_text()

BAD (~150 tokens)

Extract PDF text

PDF files are a common file format containing text and images. To extract text, you need a library. There are many available...

### Set Degrees of Freedom

- **High freedom** (text guidelines): Multiple approaches valid, context-dependent
- **Medium freedom** (pseudocode/templates): Preferred pattern exists, some variation OK
- **Low freedom** (exact scripts): Operations are fragile, consistency critical

### Recommended SKILL.md Structure

```markdown
# Skill Name

## Quick start
[Minimal working example]

## Workflow Decision Tree
[Route to the right approach based on task type]

## Detailed Instructions
[Step-by-step for each workflow]

## Examples
[Concrete input/output pairs]

## Troubleshooting
[Common errors and fixes]

Reference Files

Keep references one level deep from SKILL.md. Avoid nested chains:

# BAD: Too deep
SKILL.md -> advanced.md -> details.md -> actual info

# GOOD: One level
SKILL.md -> advanced.md (contains the info directly)
SKILL.md -> reference.md (contains the info directly)

For reference files >100 lines, include a table of contents at the top.

Patterns

Sequential Workflow

## Step 1: Analyze input
Run: `python scripts/analyze.py input.pdf`

## Step 2: Validate
Run: `python scripts/validate.py fields.json`
Fix any errors before continuing.

## Step 3: Execute
Run: `python scripts/process.py input.pdf fields.json output.pdf`

Conditional Workflow (Decision Tree)

## Workflow Decision Tree
**Creating new content?** -> Follow "Creation workflow"
**Editing existing content?** -> Follow "Editing workflow"
**Reviewing content?** -> Follow "Review workflow"

Feedback Loop

1. Make edits
2. Validate: `python scripts/validate.py`
3. If validation fails -> fix issues -> go to step 2
4. Only proceed when validation passes

Checklist Pattern (for complex tasks)

Copy this checklist and track progress:
- [ ] Step 1: Analyze input
- [ ] Step 2: Create plan
- [ ] Step 3: Validate plan
- [ ] Step 4: Execute
- [ ] Step 5: Verify output

More patterns in references/patterns.md.

Scripts

When your skill includes executable code:

• Solve, don't punt: Handle errors explicitly instead of letting them fail
• Justify constants: No magic numbers - document why each value was chosen
• Prefer execution over loading: Scripts run without entering context; only output consumes tokens
• Clarify intent: "Run

  analyze.py

  " (execute) vs "See

  analyze.py

  " (read as reference)
• List dependencies in SKILL.md and verify availability

Testing

Triggering Tests

Should trigger:
- "Help me set up a new project in [Service]"
- "I need to create a project" (paraphrased)

Should NOT trigger:
- "What's the weather?" (unrelated)
- "Write Python code" (too generic)

Functional Tests

Test normal operations, edge cases, and out-of-scope requests. Run the same request 3-5 times to check consistency.

Debug Triggering

Ask Claude: "When would you use the [skill-name] skill?" - it quotes the description back. Adjust based on what's missing.

Troubleshooting

SKILL.md

my-skill-name

Distribution

~/.claude/skills/<name>/SKILL.md

.claude/skills/<name>/SKILL.md

<plugin>/skills/<name>/SKILL.md

/v1/skills

Skills don't sync across surfaces - deploy separately to each.

Security

• Only use skills from trusted sources
• No XML angle brackets in frontmatter (injection risk)
• Audit all bundled scripts and resources before using third-party skills
• Be cautious of skills that fetch from external URLs

Additional References

• Description writing guide - detailed examples and anti-patterns
• Patterns and workflows - advanced patterns with MCP, subagents, iterative refinement
• Claude Code features - context:fork, dynamic injection, argument substitution
• Quality checklist - pre-upload validation checklist

Official Resources

• Agent Skills Spec
• Claude Code Skills Docs
• API Skills Guide
• Best Practices
• Anthropic Skills Repo
• Engineering Blog: Agent Skills
• Complete Guide PDF