L’interface est localisée ; les présentations et documents des Skills sont traduits automatiquement par IA dans votre langue. Le code, les commandes, chemins et termes techniques restent en version originale, et le document de l’auteur fait foi.
Explorer les Skills
Développement · SKILL.md

skill-reviewer

skill-reviewer

Reviews newly created or modified Claude Code skills against the writing-skills spec. Checks Iron Law presence, description quality, allowed-tools declaration, body line count, progressive disclosure structure, and cross-reference patterns. Use after creating or modifying any skill in .claude/skills/.

Independent GitHub snapshot · Automated classification · Original documentation governs

Documentation de la Skill

GitHub

name: skill-reviewer description: Reviews newly created or modified Claude Code skills against the writing-skills spec. Checks Iron Law presence, description quality, allowed-tools declaration, body line count, progressive disclosure structure, and cross-reference patterns. Use after creating or modifying any skill in .claude/skills/. allowed-tools: Read, Glob, Grep agent: skill-reviewer context: fork metadata: triggers: review skill, audit skill, check skill, skill compliance, new skill, skill authoring, writing-skills spec related-skills: writing-skills, audit-skills domain: meta role: specialist scope: review output-format: report last-reviewed: "2026-03-16"

Iron Law: Load writing-skills/references/skill-authoring-spec.md before reviewing any skill — never assess skill quality from memory.

Skill Reviewer

Audits a Claude Code skill in .claude/skills/ against the writing-skills spec. Ensures the skill is correctly structured, discoverable, and usable.

When to Use

  • After creating a new skill with /new-skill-creation
  • After modifying an existing skill's SKILL.md or reference files
  • Before committing a skill to verify it will function correctly

Review Criteria (10 checks)

#CriterionFAIL condition
1name matches directoryname field ≠ directory name
2Description has trigger wordsNo "Use when..." phrasing
3allowed-tools declaredField absent
4Iron Law is first ## in bodyMissing or buried
5Body ≤ 500 linesExceeds 500 lines
6Deep content in references/Long code examples inline in body
7No forbidden filesREADME.md, CHANGELOG.md present
8Cross-references use "see X"Content copy-pasted verbatim
9Each references/ file < 300 linesAny reference file > 300 lines
10references/ exists for stack patternsStack-specific code but no references/

Process

  1. Identify target skill directory from $ARGUMENTS
  2. Load writing-skills/references/skill-authoring-spec.md
  3. Read SKILL.md in full + list all files in the directory
  4. Apply all 10 criteria
  5. Report with PASS/WARN/FAIL per criterion + file:line evidence

Verdict

VERDICT: [PASS|CONDITIONAL PASS|FAIL] — PASS: N | WARN: N | FAIL: N
Skills enregistrées