Guide for creating effective skills following best practices. Use when creating or updating skills that extend agent capabilities.
69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, and tool integrations.
Skills are modular, self-contained packages that extend agent capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks.
The 200-line rule is critical. SKILL.md must be under 200 lines. If you need more, split content into references/ files.
skill-name/
├── SKILL.md (required, <200 lines)
│ ├── YAML frontmatter metadata (required)
│ │ ├── name: (required)
│ │ └── description: (required)
│ └── Markdown instructions (required)
└── Bundled Resources (optional)
├── scripts/ - Executable code
├── references/ - Documentation loaded as needed
└── assets/ - Files used in outputThe context window is a shared resource. Your skill shares it with everything else the agent needs. Be concise and challenge each piece of information:
Skills act as additions to models, so effectiveness depends on the underlying model. Test your skill with all models you plan to use it with.
For detailed guidance, see:
references/progressive-disclosure.md - 200-line rule and references patternreferences/skill-structure.md - SKILL.md format and frontmatter detailsreferences/examples.md - Good skill examplesreferences/best-practices.md - Comprehensive best practices guidee6ec8ed
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.