Source profileQuality 84/100

daymade/claude-code-skills/daymade-skill/skill-reviewer/SKILL.md

skill-reviewer

Reviews and improves Claude Code skills against official best practices. Supports three modes - self-review (validate your own skills), external review (evaluate others' skills), and auto-PR (fork, improve, submit). Use when checking skill quality, reviewing skill repositories, or contributing improvements to open-source skills.

Source repository stars
1,315
Declared platforms
1
Static risk flags
0
Last source update
2026-08-04
Source checked
2026-08-04

Decision brief

What it does—and where it fits

Review and improve Claude Code skills against official best practices.

Best for

  • Use when checking skill quality, reviewing skill repositories, or contributing improvements to open-source skills.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeDeclaredSource recordInstall path and trigger
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/daymade/claude-code-skills --skill "daymade-skill/skill-reviewer"
Safe inspection promptEditorial

Inspect the Agent Skill "skill-reviewer" from https://github.com/daymade/claude-code-skills/blob/b04f8a55ee3f5a390acbe05aed25db67f8067422/daymade-skill/skill-reviewer/SKILL.md at commit b04f8a55ee3f5a390acbe05aed25db67f8067422. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Quick Start

    Run the bundled reviewer with PyYAML declared explicitly through uv:

    Run the bundled reviewer with PyYAML declared explicitly through uv:The reviewer delegates YAML, schema, and internal-path validation to the canonical skill-creator validator bundled in the same suite. It then checks frontmatter quality, directory structure, SKILL.md size, hardcoded pat…Interpret exit codes as follows: 0 = clean, 1 = warnings only, 2 = review errors, 3 = invocation or runtime failure. Codes 1 and 2 describe the target skill; code 3 means the reviewer could not complete a trustworthy re…
  2. 02

    Mode 1: Self-Review

    Check your own skill before publishing.

    Check your own skill before publishing.Extended security validation:
  3. 03

    Mode 2: External Review

    Evaluate someone else's skill repository.

    Evaluate someone else's skill repository.
  4. 04

    Issue: No Workflow Pattern

    Add checklist for complex tasks:

    Add checklist for complex tasks:
  5. 05

    Workflow

    \\\ Task Progress: - [ ] Step 1: ... - [ ] Step 2: ... \\\

    [ ] Step 1: ...[ ] Step 2: ...\\\ Task Progress: - [ ] Step 1: ... - [ ] Step 2: ... \\\

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score84/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars1,315SourceRepository attention, not individual Skill quality
Compatibility1 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
daymade/claude-code-skills
Skill path
daymade-skill/skill-reviewer/SKILL.md
Commit
b04f8a55ee3f5a390acbe05aed25db67f8067422
License
MIT
Collected
2026-08-04
Default branch
main
View the original SKILL.md

Skill Reviewer

Review and improve Claude Code skills against official best practices.

Quick Start

Run the bundled reviewer with PyYAML declared explicitly through uv:

uv run --with PyYAML python <this-skill-path>/scripts/review_skill.py <target-skill-path>
uv run --with PyYAML python <this-skill-path>/scripts/review_skill.py <target-skill-path> --json

The reviewer delegates YAML, schema, and internal-path validation to the canonical skill-creator validator bundled in the same suite. It then checks frontmatter quality, directory structure, SKILL.md size, hardcoded paths and secrets, script hygiene, subagent_type validity, and instruction-style heuristics.

Interpret exit codes as follows: 0 = clean, 1 = warnings only, 2 = review errors, 3 = invocation or runtime failure. Codes 1 and 2 describe the target skill; code 3 means the reviewer could not complete a trustworthy review.

Use the sibling skill-creator scripts for the deeper security scan and packaging checks.

Three Modes

Mode 1: Self-Review

Check your own skill before publishing.

Automated review:

uv run --with PyYAML python <this-skill-path>/scripts/review_skill.py <target-skill>

Extended security validation:

# Security scan
uv run python <this-skill-path>/../skill-creator/scripts/security_scan.py <target-skill> --verbose

Manual evaluation: See references/evaluation_checklist.md.

Mode 2: External Review

Evaluate someone else's skill repository.

Review Workflow:
- [ ] Clone repository to /tmp/
- [ ] Read ALL documentation first
- [ ] Identify author's intent
- [ ] Run evaluation checklist
- [ ] Generate improvement report

Mode 3: Auto-PR

Fork, improve, and submit PR to external skill repository.

Auto-PR Workflow:
- [ ] Fork repository (gh repo fork)
- [ ] Create feature branch
- [ ] Apply additive improvements only
- [ ] Self-review: respect check passed?
- [ ] Create PR with detailed explanation

Evaluation Checklist (Quick)

CategoryCheckStatus
Frontmattername present?
description present?
description in third-person?
includes trigger conditions?
Instructionsimperative form?
under 500 lines?
workflow pattern?
Resourcesno hardcoded paths?
scripts have error handling?

Full checklist: references/evaluation_checklist.md

Core Principle: Additive Only

When improving external skills, NEVER:

  • Delete existing files
  • Remove functionality
  • Change primary language
  • Rename components

ALWAYS:

  • Add new capabilities
  • Preserve original content
  • Explain every change
❌ "Removed metadata.json (non-standard)"
✅ "Added marketplace.json (metadata.json preserved)"

❌ "Rewrote README in English"
✅ "Added README.en.md (Chinese preserved as default)"

Common Issues & Fixes

Issue: Description Not Third-Person

# Before
description: Browse YouTube videos and summarize them.

# After
description: Browses YouTube videos and generates summaries. Use when...

Issue: Missing Trigger Conditions

# Before
description: Processes PDF files.

# After
description: Extracts text from PDFs. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.

Issue: No Workflow Pattern

Add checklist for complex tasks:

## Workflow

Copy this checklist:

\`\`\`
Task Progress:
- [ ] Step 1: ...
- [ ] Step 2: ...
\`\`\`

Issue: Missing Marketplace Support

Adding or validating marketplace.json (plugin boundaries, source/skills layout, whether skills are independently toggleable) is the marketplace-dev skill's domain — don't author it from a template here. Invoke daymade-claude-code:marketplace-dev, then follow its workflow and its cache and source patterns reference.

PR Guidelines

When submitting PRs to external repos:

Tone

❌ "Your skill doesn't follow best practices"
✅ "This PR aligns with best practices for better discoverability"

❌ "Fixed the incorrect description"
✅ "Improved description with trigger conditions"

Required Sections

  1. Summary - What this PR does
  2. What's NOT Changed - Show respect for original
  3. Rationale - Why each change helps
  4. Test Plan - How to verify

Template: references/pr_template.md

Self-Review Checklist

Before submitting any PR:

Respect Check:
- [ ] No files deleted?
- [ ] No functionality removed?
- [ ] Original language preserved?
- [ ] Author's design decisions respected?
- [ ] All changes are additive?
- [ ] PR explains the "why"?

References

Alternatives

Compare before choosing