Writing skills

Process

1. Gather requirements - ask user about:
   • What task/domain does the skill cover?
   • What specific use cases should it handle?
   • Does it need executable scripts or just instructions?
   • Any reference materials to include?
2. Draft the skill - create:
   • SKILL.md with concise instructions
   • Additional reference files, if required
   • Utility scripts if deterministic operations needed
3. Review with user - present draft and ask:
   • Does this cover your use cases?
   • Anything missing or unclear?
   • Should any section be more/less detailed?

Skill structure

skill-name/
├── SKILL.md               # Main instructions (required)
├── reference.md           # Detailed docs (if needed)
├── examples.md            # Usage examples (if needed)
├── scripts/               # Scripts (if needed)
│   └── helper-script.sh   # Utility script (if needed)
└── templates/             # Templates (if needed)
    ├── template-1.md
    └── template-2.md

SKILL.md template

---
name: skill-name
description: Brief description of capability. Use when [specific triggers].
---

# Skill name

## Quick start

[Minimal working example]

## Workflows

[Step-by-step processes with checklists for complex tasks]

## Advanced features

[Link to separate files: See [reference.md](reference.md)]

Description requirements

The description is the only thing your agent sees when deciding which skill to load. It's surfaced in the system prompt alongside all other installed skills. Your agent reads these descriptions and picks the relevant skill based on the user's request.

Goal: Give your agent just enough info to know:

1. What capability this skill provides
2. When/why to trigger it (specific keywords, contexts, file types)

Format:

• Max 1024 chars
• Write in third person
• First sentence: what it does
• Second sentence: "Use when [specific triggers]"

Good example:

Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when user mentions PDFs, forms, or document extraction.

Bad example:

Helps with documents.

The bad example gives your agent no way to distinguish this from other document skills.

When to add scripts

Add utility scripts when:

• Operation is deterministic (validation, formatting)
• Same code would be generated repeatedly
• Errors need explicit handling

Scripts save tokens and improve reliability vs generated code.

When to split files

Split into separate files when the skill contains optional elements that don't always apply and don't always need to be read.

For example, a review-pr skill keeps its core workflow in SKILL.md but stores language-specific conventions in java.md or rust.md — only loaded when reviewing code in that language.

Review checklist

After drafting, verify:

• Description includes triggers ("Use when...")
• SKILL.md
• No time-sensitive info
• Consistent terminology
• Concrete examples included
• References one level deep
• Optional or context-specific content is split into separate files