Skill Submission Checklist
Use this checklist before submitting a new skill or updating an existing one.
Frontmatter Validation
-
namefield is present and 1-64 characters -
nameuses only lowercase letters, numbers, and hyphens -
namedoes not start or end with a hyphen -
namematches the parent directory name -
namedoes not start withclaude-oranthropic-(reserved) -
descriptionfield is present and 1-1024 characters -
descriptionexplains WHAT the skill does -
descriptionexplains WHEN to use it (useWHEN:with quoted trigger phrases) -
descriptiondoes NOT containDO NOT USE FOR:(risky in multi-skill environments — see SCORING.md check 4) -
descriptionis ≤ 60 words (cross-model density) -
descriptionuses inline double-quoted string (not>-folded scalar) - No XML angle brackets (
< >) in frontmatter
Token Budget
See Token Budgets for detailed limits.
- SKILL.md is under 500 tokens (soft limit)
- SKILL.md is under 5000 tokens (hard limit per spec)
- Reference files are each under 1000 tokens
- Run
npm run tokens -- checkfromscripts/directory
Structure
- SKILL.md exists in the skill root directory
- Optional
references/directory for detailed docs - Optional
scripts/directory for executable code - Optional
assets/directory for templates/data - File references use relative paths from skill root
- No deeply nested reference chains
Link and Reference Integrity
- All markdown links point to existing files (no broken links)
- All files in
references/are linked from SKILL.md or other references (no orphans) - References >1000 tokens are split into folder with README.md
- Duplicate content is consolidated into shared references
- No out-of-place guidance (service-specific content in generic sections)
Content Quality
- Instructions are action-oriented (step-by-step)
- Has examples section (input → expected output)
- Has error handling (common failures and recovery)
- Tables used for dense information
- No decorative emojis (only functional ones if needed)
- No repeated content across sections
- Complex details moved to
references/files - Code examples are minimal and purposeful
Azure-Specific (for this repo)
- Prefers Azure MCP tools over direct CLI commands
- Uses
azdwhere applicable - Lists relevant MCP tools in a "Tools Used" section
- Includes troubleshooting section for common issues
- Scripts include both bash and PowerShell versions (if non-trivial)
Testing
- Skill activates correctly when relevant prompts are used
- Referenced files exist and are accessible
- Scripts execute without errors
- MCP tools mentioned are available and documented
Final Steps
cd scripts
npm run references # Validate all skill links
npm run tokens -- check # Check token limitsIf any checks fail, see Guidelines for guidance.