Skill Quality Review

VerifiedSafe

Reviews SKILL.md files for quality, frontmatter correctness, and convention compliance. Also checks the impact of changes on skills across the project.

Sby Skills Guide Bot
DevelopmentAdvanced
8/6/2026
Claude Code
#skill-authoring#code-review#frontmatter-validation#cross-reference-check#static-analysis

Recommended for

Automated summary

This skill lets a review orchestrator audit SKILL.md files for quality, frontmatter correctness, and convention compliance, then check how a change impacts other skills across the project.

Strengths

  • Cleanly separates quality auditing of in-focus files from repo-wide impact verification
  • Implements a three-tier rule resolution: local skill guidance, default rules, or a combination of both
  • Verifies file integrity by checking referenced files exist and validating $ARGUMENTS usage
  • Delegates output format and severity scoring to a dedicated review framework

Limitations

  • Depends on the availability of the local-review-skill and reviewer:reviewer-framework skills plus references/default-skill.md
  • Does not ship the checklist itself; audit quality relies entirely on the loaded rules
  • Designed to be invoked by an orchestrator, with little documentation for direct standalone use
When to use it

Use this skill when a review orchestrator needs to validate changed SKILL.md files for quality and catch broken references elsewhere in the project.

When not to use it

Do not use it to review ordinary application code, or when the review rules and output framework it depends on are unavailable in the environment.

Security analysis

Safe
Quality score88/100

The skill only reads local files, uses Glob/Grep to inspect the repository, loads other skills via the Skill tool, and fetches public documentation from two specific URLs with WebFetch. It does not execute shell commands, modify files, exfiltrate data, or disable safety mechanisms.

No concerns found

How this analysis is made

Examples

Review changed skill files
Review the SKILL.md files I just modified in skills/deploy-helper/ against the authoring checklist and tell me what they break elsewhere in the repo.
Full project skill audit
Run a quality review of every skill in this project, checking frontmatter, referenced files, and naming conventions.
Check impact of a rename
I renamed the skill reviewer:self-review to reviewer:self-audit — verify which other skills, agent definitions, and marketplace entries still reference the old name.

name: review-skill description: >- This skill should be invoked by a review orchestrator (e.g. reviewer:self-review) to review SKILL.md files for quality, frontmatter correctness, and convention compliance, and to check the impact of a change on skills across the project. allowed-tools: Read, Glob, Grep, Skill, WebFetch argument-hint: "[focus-paths]"

Review: Skill Quality

Review the SKILL.md files in focus against the authoring checklist, and verify what the focus files invalidate across the project's skills.

Input: $ARGUMENTS - focus paths. These are the changed files handed over by an orchestrator, a skill directory, or empty (whole project). When empty, every skill in the project is in focus, and step 3 is then a no-op since nothing outside the focus is left to check.

Review Procedure

  1. Load rules and framework:

    • Try to load the skill local-review-skill.
      • If it loads and its instructions say to NOT use the defaults, use only the local skill's guidance.
      • If it loads and does NOT prohibit defaults, read the default rules from references/default-skill.md and combine them with the local guidance.
      • If it does not load (skill not found), read the default rules from references/default-skill.md.
    • Load reviewer:reviewer-framework for output format, severity definitions, and confidence scoring.
  2. Audit every skill whose files are in focus against the full checklist:

    • Read the file and parse frontmatter (YAML between --- fences) and body content
    • Apply loaded review rules - run through every checklist item from the loaded guidance (defaults, local, or combined)
    • Verify file integrity - check that all referenced files exist on disk; search file contents to verify $ARGUMENTS usage and file path references
  3. Verify repo-wide what the focus affects - read the focus files and flag, across the whole project, only what they invalidate, in both directions:

    • a focus file (skill or non-skill) that invalidates a skill's content - a documented claim it makes false, a reference it leaves stale, a renamed or removed thing the skill still describes
    • a focus skill that breaks references to it elsewhere - namespace:skill-name mentions and markdown relative links, marketplace.json, README tables, agent definitions, or orchestration skills that invoke it - via rename, move, removal, or contract change

    Flag only breakage driven by the focus files; do not run the quality checklist on skills outside the focus.

  4. Report findings using the reviewer-framework output format

Upstream References

For edge cases not covered by the checklist, fetch the source that owns the field using WebFetch:

Only fetch when a field's constraints are unclear or you encounter an uncovered pattern.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/skill-quality-review-msh3ut03/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/skill-quality-review-msh3ut03' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/skill-quality-review-msh3ut03/download' --output '.skill-downloads/skill-quality-review-msh3ut03/SKILL.md.part' && mv '.skill-downloads/skill-quality-review-msh3ut03/SKILL.md.part' '.skill-downloads/skill-quality-review-msh3ut03/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Glob, Grep, Skill, WebFetch

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/skill-quality-review-msh3ut03/SKILL.md' && test -s '.skill-downloads/skill-quality-review-msh3ut03/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/review-skill' && cp -R '.skill-downloads/skill-quality-review-msh3ut03' '.claude/skills/review-skill'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/skill-quality-review-msh3ut03'

openskills read 'skill-quality-review-msh3ut03'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/skill-quality-review-msh3ut03/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills