microsoft/skill-authoring
Guidelines for writing Agent Skills that comply with the agentskills.io specification. WHEN: \"create a skill\", \"new skill\", \"write a skill\", \"skill template\", \"skill structure\", \"review skill\", \"skill PR\", \"skill compliance\", \"SKILL.md format\", \"skill frontmatter\", \"skill best practices\".
npx skills add https://github.com/microsoft/GitHub-Copilot-for-Azure --skill skill-authoring
This skill provides guidance for writing Agent Skills that comply with the agentskills.io specification.
name: 1-64 chars, lowercase + hyphens, match directorydescription: 1-1024 chars, ≤60 words, explain WHAT and WHENWHEN: with quoted trigger phrases (preferred over USE FOR:)DO NOT USE FOR: unless the skill has trigger overlap with a broader skill (see frontmatter guidelines)>- folded scalars)SKILL.md (required) - Instructionsreferences/ (optional) - Detailed docsscripts/ (optional) - Executable codeFrontmatter: name (lowercase-hyphens), description (WHAT + WHEN)
Metadata (~100 tokens) loads at startup. SKILL.md (<5000 tokens) loads on activation. References load only when explicitly linked (not on activation). Keep SKILL.md lean.
References are JIT (just-in-time) loaded:
text loadRecipes not RecipesSee REFERENCE-LOADING.md for details.
# Run from the scripts directory
cd scripts
npm run references # Validate all skill links
npm run tokens -- check # Check token limits
When reviewing or authoring skills, verify:
See Validation for detailed procedures.
Take microsoft/skill-authoring from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.