reviewing-skills

Evaluate SKILL.md frontmatter and body quality against official best practices.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nm7-jp/morpheus-operator --skill reviewing-skills-nm7-jp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-skills
Source: https://github.com/nm7-jp/morpheus-operator/tree/main/.claude/skills/reviewing-skills
Command: npx skills add https://github.com/nm7-jp/morpheus-operator --skill reviewing-skills-nm7-jp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code Skill units often vary in quality and structure. This guide defines a consistent review process to validate SKILL.md frontmatter, body quality, and overall architecture against official best practices, producing actionable improvement suggestions.

Core Features & Use Cases

  • Frontmatter validation: ensures name and description are present and well-formed.
  • Body quality assessment: checks conciseness, structure, progressive disclosure, and workflow design.
  • Improvement reporting: outputs a structured review report with critical and recommended actions.
  • Use Case: run a skill through a review to obtain a gap analysis and concrete edits.

Quick Start

Review the target SKILL.md against the official best practices and generate a structured improvement plan.

Frequently Asked Questions about reviewing-skills

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

FAQPage Schema
How do I validate SKILL.md frontmatter and structure against best practices?

Reviewing skill quality involves evaluating the SKILL.md body for conciseness, correct sections, progressive disclosure, and workflow design, then generating a structured improvement report with critical and recommended actions to align with official best practices.

What is the best way to check Claude Code skills for quality and structure gaps?

To generate an improvement plan for skill validation, review the target SKILL.md against official best practices, identify frontmatter and body quality gaps, and output a structured report with concrete edits and critical actions.

Do I need specific dependencies to review skill documentation and architecture?

No dependencies are required to review skill documentation and architecture, as the validation process applies standard checks to the SKILL.md frontmatter and body structure to generate a gap analysis without external tools.

What should a structured skill review report include for documentation quality?

A structured skill review report for documentation quality should include frontmatter validation results, body quality assessments for conciseness and structure, and a clear list of critical and recommended improvement actions.