| name | skill-authoring |
| description | Create high-quality skills: scoped, procedural, and durable. Prefer updates over duplicates. Use when working with SKILL.md files, authoring new skills, improving existing skills, or understanding skill structure and best practices. |
| license | MIT |
| compatibility | opencode |
| metadata | {"created_at":"2026-01-27T17:03:09.731823+00:00","updated_at":"2026-01-27T17:03:09.731823+00:00","version":"1","tags":"skills,authoring"} |
Creating Agent Skills
This skill teaches how to create effective OpenCode skills following the skill format used in this repository.
Core Principles
1. Skills Are Prompts
All prompting best practices apply. Be clear, be direct. Assume the agent is smart - only add context the agent doesn't have.
2. Standard Markdown Format
Use YAML frontmatter + markdown body. No XML tags - use standard markdown headings.
---
name: my-skill-name
description: What it does and when to use it
---
# My Skill Name
## Quick Start
Immediate actionable guidance...
## Instructions
Step-by-step procedures...
## Examples
Concrete usage examples...
3. Progressive Disclosure
Keep SKILL.md under 500 lines. Split detailed content into reference files. Load only what's needed.
my-skill/
├── SKILL.md # Entry point (required)
├── reference.md # Detailed docs (loaded when needed)
├── examples.md # Usage examples
└── scripts/ # Utility scripts (executed, not loaded)
4. Effective Descriptions
The description field enables skill discovery. Include both what the skill does AND when to use it. Write in third person.
Good:
description: Extracts text and tables from PDF files, fills forms, merges documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.
Bad:
description: Helps with documents
Skill Structure
Required Frontmatter
| Field | Required | Max Length | Description |
|---|
name | Yes | 64 chars | Lowercase letters, numbers, hyphens only |
description | Yes | 1024 chars | What it does AND when to use it |
allowed-tools | No | - | Tools the agent can use without asking |
model | No | - | Specific model to use |
Naming Conventions
Use gerund form (verb + -ing) for skill names:
processing-pdfsanalyzing-spreadsheetsgenerating-commit-messagesreviewing-code
Avoid: helper, utils, tools, vendor/runtime-prefixed names
Body Structure
Use standard markdown headings:
# Skill Name
## Quick Start
Fastest path to value...
## Instructions
Core guidance the agent follows...
## Examples
Input/output pairs showing expected behavior...
## Advanced Features
Additional capabilities (link to reference files)...
## Guidelines
Rules and constraints...
What Would You Like To Do?
- Create new skill - Build from scratch
- Audit existing skill - Check against best practices
- Add component - Add workflow/reference/example
- Get guidance - Understand skill design
Creating a New Skill
Step 1: Choose Type
Simple skill (single file):
- Under 500 lines
- Self-contained guidance
- No complex workflows
Progressive disclosure skill (multiple files):
- SKILL.md as overview
- Reference files for detailed docs
- Scripts for utilities
Step 2: Create SKILL.md
---
name: your-skill-name
description: [What it does]. Use when [trigger conditions].
---
# Your Skill Name
## Quick Start
[Immediate actionable example]
```[language]
[Code example]
Instructions
[Core guidance]
Examples
Example 1:
Input: [description]
Output:
[result]
Guidelines
- [Constraint 1]
- [Constraint 2]
### Step 3: Add Reference Files (If Needed)
Link from SKILL.md to detailed content:
```markdown
For API reference, see [REFERENCE.md](REFERENCE.md).
For form filling guide, see [FORMS.md](FORMS.md).
Keep references one level deep from SKILL.md.
Step 4: Add Scripts (If Needed)
Scripts execute without loading into context:
## Utility Scripts
Extract fields:
```bash
python scripts/analyze.py input.pdf > fields.json
### Step 5: Test With Real Usage
1. Test with actual tasks, not test scenarios
2. Observe where the agent struggles
3. Refine based on real behavior
4. Test across multiple models (at least one fast/cheap and one strong)
## Auditing Existing Skills
Check against this rubric:
- [ ] Valid YAML frontmatter (name + description)
- [ ] Description includes trigger keywords
- [ ] Uses standard markdown headings (not XML tags)
- [ ] SKILL.md under 500 lines
- [ ] References one level deep
- [ ] Examples are concrete, not abstract
- [ ] Consistent terminology
- [ ] No time-sensitive information
- [ ] Scripts handle errors explicitly
## Common Patterns
### Template Pattern
Provide output templates for consistent results:
```markdown
## Report Template
```markdown
# [Analysis Title]
## Executive Summary
[One paragraph overview]
## Key Findings
- Finding 1
- Finding 2
## Recommendations
1. [Action item]
2. [Action item]
### Workflow Pattern
For complex multi-step tasks:
```markdown
## Migration Workflow
Copy this checklist:
**Step 1: Backup database**
Run: `./scripts/backup.sh`
...
Conditional Pattern
Guide through decision points:
## Choose Your Approach
**Creating new content?** Follow "Creation workflow" below.
**Editing existing?** Follow "Editing workflow" below.
Anti-Patterns to Avoid
- XML tags in body - Use markdown headings instead
- Vague descriptions - Be specific with trigger keywords
- Deep nesting - Keep references one level from SKILL.md
- Too many options - Provide a default with escape hatch
- Windows paths - Always use forward slashes
- Punting to the agent - Scripts should handle errors
- Time-sensitive info - Use "old patterns" section instead
Reference Files
For detailed guidance, see:
Success Criteria
A well-structured skill:
- Has valid YAML frontmatter with descriptive name and description
- Uses standard markdown headings (not XML tags)
- Keeps SKILL.md under 500 lines
- Links to reference files for detailed content
- Includes concrete examples with input/output pairs
- Has been tested with real usage
Sources:
Manual notes
This section is preserved when the skill is updated. Put human notes, caveats, and exceptions here.
