Review Skill PRs Like a Maintainer: The skill-reviewer Dispatch

Where this fits

You're maintaining a growing catalog of agent skills, and a teammate opens a PR that tweaks the routing logic in plugins/{plugin}/skills/calendar-sync/SKILL.md. You know it's subtle — a misspelled trigger or an extra token in the description could break other agents' routing. skill-reviewer steps in to scan the changed files, check them against a rigorous checklist, and give you severity-rated findings before you merge.

Why agents benefit

• Structured severity classification — every finding is labeled critical/major/minor with a concrete fix, so the agent can prioritize or request changes autonomously.
• Token budget and routing conflict checks — catches oversized descriptions that exceed model context limits and conflicting WHEN triggers that would steal invocations from other skills.
• Repo convention validation — verifies required sections (frontmatter, examples, references) and aligns with Microsoft's skill metadata standards, reducing maintainer back-and-forth.
• Meta-skill awareness — correctly distinguishes .github/skills/ meta-skills from plugins/*/skills/ service skills, applying only the relevant sections (8–9) where required.
• Audit and pre-submit mode — works not just on PRs but also as a standalone quality check before opening a PR, turning review into a proactive practice.

Practical scenarios

Pre-submit compliance check

Before pushing to your feature branch, run the skill against your changed skill file. The agent immediately flags a missing license field and a description that exceeds the recommended token budget, saving you a CI failure.

Rapid PR triage in a multi-plugin repository

A bot comments on every skill PR with a summary table and severity breakdown. The agent points out that your new WHEN phrase overlaps with an existing skill, suggesting an alternative trigger that avoids the conflict.

Auditing an inherited skill library

You've taken over a legacy set of skills. Run skill-reviewer on the whole folder and get a prioritized list of fixes — from missing references to duplicate routing — turning a messy audit into an actionable backlog.

Add it to your agent workflow

Install the skill directly from GitHub Copilot for Azure:

npx skills add microsoft/GitHub-Copilot-for-Azure --skill skill-reviewer

Then invoke it in a PR review context by saying: "review skill PR" or "check skill quality". For example, in your agent's system prompt, add:

- When someone requests a skill review, run skill-reviewer and surface the severity table.
- For meta-skills under `.github/skills/`, only apply checklist sections 1–7.

Compare before adopting

Before committing to skill-reviewer, look at three things: quality signals — does it produce actionable, severity-rated findings that reduce review time? maintenance freshness — check the repo's commit activity and issues; Microsoft maintains it, but forks may lag. alternatives — some teams use custom linters or manual checklists; compare if you need deeper integration with your CI. workflow fit — does it match your skill directory layout and review cadence? For more context on where this fits in the broader skills ecosystem, see the OpenAgentSkill listing.

Why it is worth tracking

With 244 stars and an active Microsoft maintainer, skill-reviewer signals a growing standard for skill quality. Its structured severity system and meta-skill differentiation fill a real gap in agent development—most teams lack a formal review process for skills. Track it if you're building a shared skill registry, if PR reviews on skills are ad-hoc, or if you need a baseline for skill compliance. The checklist can also be adapted to your own conventions, making it a durable reference beyond just the tool itself.