skills.rest
j5ik2o
j5ik2oCOMMUNITY
Explore all skills by this author →
Website𝕏@j5ik2oGitHub

reviewing-skills

Review SKILL.md files against official best practices and generate improvement reports.

Updated Jun 23, 2026
Search Tags:#code quality#best practices#validation#claude code#frontmatter#skill.md#skill review
One-click install
npx skills add https://github.com/j5ik2o/marp-ai-base --skill reviewing-skills-j5ik2o
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-skills
Source: https://github.com/j5ik2o/marp-ai-base/tree/main/.agents/skills/reviewing-skills
Command: npx skills add https://github.com/j5ik2o/marp-ai-base --skill reviewing-skills-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing high-quality Claude Code skills requires following many official best practices, and manually checking SKILL.md files against all of them is error-prone and time-consuming. This Skill automates the review process and produces actionable, severity-ranked feedback. ## Core Features & Use Cases - Structured Review Workflow: Locates the target SKILL.md, loads a best-practices checklist, and evaluates frontmatter, body structure, workflows, and content quality. - Severity-Ranked Reports: Classifies findings as Critical, Warning, or Info and outputs a standardized Markdown review report with concrete recommendations. - Interactive Improvement: After reporting, guides step-by-step fixes with re-validation after each change. - Use Case: You just wrote a new pdf-processor skill and want to verify it follows official conventions before publishing—run this review to catch missing descriptions, oversized bodies, and anti-patterns. ## Quick Start Review the SKILL.md file in my current skill directory and generate a report with improvement suggestions.

Frequently Asked Questions about reviewing-skills

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

FAQPage Schema
How do I review a Claude Code skill for best practices?▼

Point the reviewer at your SKILL.md file and it loads a best-practices checklist covering frontmatter, body structure, workflows, and content quality. It then outputs a report classifying issues as Critical, Warning, or Info with concrete fixes.

What makes a good SKILL.md description field?▼

A good description is under 1024 characters, written in third person, explains what the skill does and when to use it, and includes concrete trigger words or scenarios. Empty or vague descriptions are flagged as Critical issues.

How long should a SKILL.md file be?▼

The body should stay under 500 lines. Detailed content should be moved into separate reference files using progressive disclosure, with links no deeper than one level from SKILL.md.

What anti-patterns should I avoid when writing skills?▼

Avoid Windows-style paths, time-sensitive information, magic constants without explanation, multiple options without a default, deeply nested file references, and assuming packages are preinstalled. Scripts must also handle error conditions explicitly.

Can the skill reviewer fix issues automatically?▼

After generating the report, it offers an interactive improvement phase where Critical issues are fixed first, changes are applied incrementally, and each fix is re-validated before proceeding.

Related Skills

Explore More Software Engineering Skills→
hidonguyenhidonguyen

ck:template-skill

Scaffold Claude skill directories with a starter SKILL.md and YAML frontmatter.

Community
Basic
ProSkillsMDProSkillsMD
11

skill-multi-publisher

Validate SKILL.md metadata and submit pull requests to multiple skill directories.

Official
Intermediate
LegalQuantsLegalQuants
116

beta-minimal

Validate skill loader discovery using minimal YAML frontmatter with name and description.

Official
Basic
StudentCristianStudentCristian

nw-dr-review-criteria

Automate documentation review critiques against a standardized verdict matrix.

Community
Advanced