mcpbeat

Skill Authoring

azure/skill-authoring

Write 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". DO NOT USE FOR: improving existing skills (use sensei), general documentation. INVOKES: waza CLI.

5k tokens
context cost
the whole folder, loaded on every use
6
files
instructions only
0
copies elsewhere
how many repositories repackaged it
136
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Azure/azure-sdk-tools --skill skill-authoring

What comes with it

17 180 bytes besides the instruction
evals/eval.yaml
evals/trigger.eval.yaml
references/guidelines.md
references/reference-guide.md
references/validation.md

The instruction itself

11 sections, as written by the author

Skill Authoring Guide

This skill helps write Agent Skills that comply with the agentskills.io specification by defining valid frontmatter, structure, and routing patterns, while guiding authors toward compliant SKILL.md files, supporting references, and local validation with the waza CLI.

Triggers

USE FOR: write Agent Skills that comply with the agentskills.io specification; skill template; skill structure; review skill; skill PR; skill compliance; SKILL.md format; skill frontmatter; skill best practices

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"

DO NOT USE FOR: improving existing skills (use sensei), general documentation

Rules

  • name: 1-64 chars, lowercase + hyphens, match directory
  • description: inline double-quoted, ≤60 words, ≤1024 chars
  • Use WHEN: with quoted trigger phrases (preferred over USE FOR:)
  • SKILL.md: <500 tokens (soft), <5000 (hard)
  • references/\*.md: <1000 tokens each

Structure

  • SKILL.md (required) — Frontmatter + instructions
  • references/ (optional) — Detailed docs, loaded on demand
  • scripts/ (optional) — Executable code

Formatting

  • run npm ci in .github/skills to install dependencies
  • run npm run format to auto-format markdown and yaml files using Prettier

Progressive Disclosure

Metadata loads at startup. SKILL.md on activation. References load when linked via markdown link.

MCP Tools

| Tool | Purpose |

| ---- | ------------------------------- |

| None | CLI-only; uses local file tools |

CLI fallback: Primary mode is CLI-based. No MCP servers required.

Steps

  • Create skill directory with SKILL.md
  • Add frontmatter: name, description, license
  • Run waza check {skill-name} to validate

Examples

  • "Create a new skill for code review"
  • "Review my skill for compliance"

Troubleshooting

If waza check reports broken links, verify reference file paths match exactly.

References

  • Guidelines — Writing and structure
  • Validation — Checks and procedures
  • Reference Guide — Budgets, loading, checklist

How to use it

Copy the folder

Take azure/skill-authoring from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.