review-skill

Reviews Claude Code skills against plugin conventions and returns a severity-ranked verdict.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill review-skill-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-skill
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/review-skill
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill review-skill-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Skill authors need an independent, clean-context check that a finished or modified skill conforms to plugin conventions before it goes live. This Skill acts as that reviewer: it validates naming, mandatory frontmatter fields, model/effort pairing, and instruction quality, then returns a verdict with findings ranked by severity — without ever editing the skill itself. ## Core Features & Use Cases - Convention compliance check: Verifies kebab-case naming, the mandatory frontmatter five (name, description, when_to_use, model, effort), the 1536-character description limit, and justification comments for omitted fields. - Instruction quality review: Checks imperative style, triggering boundaries against neighboring skills and agents, allowed-tools fit, and path anchoring rules depending on where the skill lives (plugin vs. project .claude/skills/). - Structured verdict output: Returns Approve or Return-for-rework with a findings table classified as Blocking, Recommendation, or Note, plus verification of unresolved findings from previous review rounds. - Use Case: After write-skill finishes a draft, it spawns this reviewer as a subagent each iteration; the reviewer reads the skill and the write-skill conventions, reports blocking findings, and the loop repeats until approval. ## Quick Start Ask the assistant to review the skill at a given path against the plugin conventions and return the verdict with findings.

Frequently Asked Questions about review-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a Claude Code skill against plugin conventions?

Invoke the review-skill with the absolute path to the skill, the plugin root, and the target repository. It reads the SKILL.md, compares it against the write-skill conventions, and returns a verdict with findings ranked by severity.

What does the skill review check in the frontmatter?

It verifies kebab-case naming matching the folder, the mandatory five fields (name, description, when_to_use, model, effort), the 1536-character limit on description plus when_to_use, and justification comments for every omitted optional field.

Can the reviewer fix the skill it reviews?

No. The reviewer is strictly read-only and never edits the reviewed skill. Fixes are the author's job via write-skill; the reviewer only reports findings with concrete recommendations to preserve process independence.

When is a skill approved versus returned for rework?

A skill is approved only when zero blocking findings remain. Even a single blocking finding means the verdict is returned for rework, with the blocking items listed as next steps for the author.

Why does the reviewer forbid using CLAUDE_PLUGIN_ROOT in paths?

When spawned as a subagent, the variable does not expand and remains a literal string, breaking file reads. Reviewer-type skills must take the plugin root from the caller's assignment instead.