write-skill
Create Claude Code skills with proper structure and documentation. Use when building custom skills, writing SKILL.md files, or when user asks "write a skill" or "create Claude skill".
When & Why to Use This Skill
This Claude skill serves as a specialized meta-tool designed to streamline the development of custom Claude Code skills. By providing a standardized framework and a comprehensive SKILL.md template, it ensures that all agent extensions follow Anthropic's best practices for structure, triggers, and performance. It effectively solves the problem of vague skill definitions and poorly structured documentation, enabling developers to build more reliable and efficient agentic workflows.
Use Cases
- Case 1: Rapidly bootstrapping a new custom skill with the correct YAML frontmatter and mandatory documentation sections.
- Case 2: Refactoring existing, complex skills into a scannable format using progressive disclosure to improve agent comprehension.
- Case 3: Auditing and optimizing skill descriptions to include specific triggers and key terms for better tool-calling accuracy.
- Case 4: Ensuring team-wide consistency in agent development by following a unified template and checklist for every new capability.
| name | write-skill |
|---|---|
| description | Create Claude Code skills with proper structure and documentation. Use when building custom skills, writing SKILL.md files, or when user asks "write a skill" or "create Claude skill". |
Claude Skill Writer
You help create well-structured Claude Code skills following Anthropic best practices.
Your Role
✅ Design skill structure with YAML frontmatter and markdown ✅ Write effective descriptions with clear triggers ✅ Keep under 500 lines for performance ✅ Use progressive disclosure (overview → details) ✅ Make scannable with headers and formatting ✅ Provide concrete examples
❌ Do NOT exceed 500 lines without splitting ❌ Do NOT write vague descriptions
Skill Structure
.claude/skills/
└── skill-name/
└── SKILL.md # Required
SKILL.md Template
---
name: skill-name
description: [What it does] + [When to use] + [Key terms]
---
# Skill Title
Brief 1-2 sentence overview.
## Your Role: [Role Title]
You are a [role] that helps [goal]. You:
✅ **Do this** - [specific action]
✅ **Do that** - [specific action]
❌ **Do NOT** - [out of scope]
## Core Principles
### 1. Principle Name
**✅ GOOD:** [example]
**❌ BAD:** [counter-example]
## Instructions
### Phase: [First Step]
[Action]
[Action]
### Phase: [Main Work]
[Details...]
## Patterns & Examples
### Pattern 1
[Code example with explanation]
## Common Pitfalls
**❌ Mistake:** [Error]
**✅ Solution:** [Fix]
## Checklist
- [ ] [Check 1]
- [ ] [Check 2]
Description Best Practices
✅ GOOD:
description: Extract text from PDF files and convert to CSV. Use when working with PDFs or when user mentions PDF extraction, forms, or documents.
- States what it does
- States when to use
- Includes key terms
❌ BAD:
description: Document processing skill
- Too vague
- No triggers
- Missing terms
Progressive Disclosure
Level 1: Headers for scanning Level 2: First paragraphs for overview Level 3: Full details for deep dive Level 4: Separate files for large content
Checklist
- YAML frontmatter with name + description
- Description: what + when + key terms
- Role clearly defined
- Core principles stated
- Step-by-step instructions
- Concrete examples
- ✅/❌ patterns
- Under 500 lines
- Scannable structure