Topics
- Documentation
- skill-creation
- workflow
- claude
- ai-agents
- prompt-engineering
- context-management
What it does
This skill provides guidance for structuring and writing SKILL.md files—the instruction templates that AI agents load to extend their capabilities with specialized knowledge, workflows, and tool integrations. It covers skill anatomy (required SKILL.md frontmatter and body, optional bundled scripts/references/assets), context management principles (conciseness, progressive disclosure, appropriate degrees of freedom), and a five-step creation process (understand use cases, plan reusable contents, initialize, implement, package). Use this skill when designing a new skill or refactoring an existing one to meet the skilld.dev standard.
Generated from the current SKILL.md.
Frequently asked
What is the difference between a skill and a plugin or package?
A skill is a modular instruction file (SKILL.md) with optional bundled scripts, references, and assets that extend Claude's capabilities on-demand. It is not a package, plugin, or extension—it is an onboarding guide that transforms Claude into a specialized agent for specific domains or tasks.
How much content should I put in SKILL.md versus bundled reference files?
Keep SKILL.md under 500 lines with only essential procedural instructions and workflow guidance. Move detailed reference material, schemas, examples, and variant-specific details into separate reference files and link them from SKILL.md so Claude loads them only when needed.
When should I create a script versus putting instructions in SKILL.md?
Create a script when the same code is rewritten repeatedly or deterministic reliability is critical. Use text-based SKILL.md instructions when multiple approaches are valid and decisions depend on context.
What files should I avoid including in a skill?
Do not include auxiliary documentation like README.md, INSTALLATION_GUIDE.md, CHANGELOG.md, or other files not directly needed for the skill to function. Keep only SKILL.md and bundled resources (scripts, references, assets) that support the skill's core functionality.
How do I organize a skill that supports multiple frameworks or domains?
Create separate reference files organized by framework or domain (e.g., references/aws.md, references/gcp.md) and link them from SKILL.md. Claude will only load the relevant reference file when the user specifies their choice, avoiding unnecessary context bloat.
Generated from the current SKILL.md. These answers refresh after source changes.