skill-reviser

Review existing skills by auditing frontmatter quality, identifying framing flaws, and checking validation loops to produce actionable improvement recommendations for maintainability and portability.

A skill documentation validation process should look for misframing, vague instructions, missing validation loops, redundant files, and portability risks, then propose concrete improvements to fix them.

Identify overlapping scope by comparing neighboring skill artefacts to detect gaps and redundancies, enforcing review scope boundaries and ensuring references and assets are justified.

Yes, you can enforce frontmatter quality during a skill review by validating metadata fields, checking review scope, and ensuring all references, scripts, and assets are justified.

Improve skill maintainability after deployment by conducting a structured frontmatter and scope review, identifying redundant files, and applying actionable improvement recommendations to reduce portability risks.

A skill review fails to catch portability risks and missing validation when it lacks structured frontmatter enforcement, scope boundaries, and validation loops, preventing the justification of references and scripts.