
Creating Skills
Write discoverable, scannable Claude skills with proper structure and CSO optimization
What You Can Do
You can create new Claude skills from scratch or improve existing ones by following proven structural patterns, frontmatter standards, and discoverability best practices. This skill teaches you how to write skills that future Claude instances can quickly locate, scan, and effectively apply to real problems—ensuring your techniques get reused instead of forgotten.
Features
write YAML headers with proper naming conventions, descriptions, and tag structures that make skills discoverable
follow the proven layout of Overview, When to Use, Quick Reference, Implementation, and Common Mistakes sections
craft titles and descriptions that help Claude find and evaluate your skill efficiently
use gerund forms and avoid reserved words to keep skill names scannable and consistent
see working examples of well-structured skills across different domains and complexity levels
learn to distinguish between skills (broad patterns) and project conventions so you create the right artifact type
organize common operations in tables or bullet lists for fast evaluation by future Claude instances
Example Output
Well-Structured Skill Output
Frontmatter:
---
name: analyzing-performance-metrics
description: Use when debugging slow endpoints or tracking system bottlenecks - breaks down analysis patterns, common bottleneck sources, and measurement techniques
tags: performance, debugging, optimization
---
Quick Reference Table:
| Metric Type | What It Measures | Red Flag Threshold |
|---|---|---|
| Response Time | End-to-end latency | >500ms for user requests |
| Memory Usage | Heap allocation | >80% capacity |
| CPU Utilization | Processing load | >85% sustained |
Implementation Section: Shows 3-4 concrete code patterns or analysis approaches with inline examples, then links to a detailed reference document if needed.
What's Included
- SKILL.md instruction file with complete frontmatter and structure standards:
- Naming conventions checklist for gerund forms and reserved-word avoidance:
- When-to-use decision framework distinguishing skills from project conventions:
- Frontmatter template ready to copy for new skills:
- Document structure template with section guidelines and formatting examples:
- CSO optimization guide for crafting discoverable titles and descriptions:
Who It's For
- Claude skill authors and maintainers building reusable reference guides
- Engineering team leads establishing skill documentation standards across projects
- Documentation specialists improving discoverability and structure of existing skills
- AI workflow designers creating skill libraries for multi-agent systems
- Technical architects standardizing patterns and techniques across codebases
Best For
- Writing new skills from scratch with proper structure and frontmatter
- Auditing and improving existing skills for discoverability and clarity
- Establishing skill documentation standards within teams or organizations
- Creating skill naming conventions and tagging systems
- Distinguishing between skills, project conventions, and one-off solutions







