Review Skill

Name: Review Skill
Author: aviz85

aviz85/claude-skills-library

46 installs
44 repo stars
Updated July 8, 2026
aviz85/claude-skills-library

review-skill is a Claude skill that provides a review checklist to verify new skills meet the claude-skills-library structure, frontmatter, and quality standards.

About

review-skill is a checklist for reviewing new skills before adding them to the claude-skills-library. It verifies file structure, required frontmatter fields, content length limits, absence of credentials, and docs-site sync. A skill author uses it to confirm a new skill meets the library's quality and structure requirements.

Checklist to verify new skills meet claude-skills-library structure and quality standards
Covers required skill.md frontmatter, SETUP.md, .env.example, and line-count limits
Includes a review checklist and docs-site sync steps

Review Skill by the numbers

46 all-time installs (skills.sh)
Ranked #337 of 779 Skill Development skills by installs in the Skillselion catalog
Data as of Jul 28, 2026 (Skillselion catalog sync)

At a glance

review-skill capabilities & compatibility

Free; runs ls, head, and wc against a skill folder with no API keys.

Capabilities: reality check · documentation
Use cases: documentation · code review
Pricing: Free

From the docs

What review-skill says it does

Review new skills before adding to the library.

skill.md

**Concise** - Under 100 lines ideal, max 150

skill.md

No credentials or API keys in any file

skill.md

npx skills add https://github.com/aviz85/claude-skills-library --skill review-skill

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/aviz85/claude-skills-library/review-skill.svg)](https://skillselion.com/skills/aviz85/claude-skills-library/review-skill)

Installs	46
repo stars	★ 44
Last updated	July 8, 2026
Repository	aviz85/claude-skills-library ↗

What it does

Review a new Claude skill's structure, frontmatter, and docs before adding it to a skills library.

Who is it for?

Verifying a new skill's file structure, frontmatter, and docs before adding it to a skills library.

Skip if: Authoring the skill logic itself; it only reviews an existing skill against standards.

When should I use this skill?

Adding new skills to a library and needing to verify they meet quality and structure requirements.

What you get

A completed review checklist confirming the skill meets library standards, with docs-site cards synced.

Completed review checklist
Docs-site skill card

By the numbers

Content under 100 lines ideal, max 150
Review checklist with 9 items

Files

skill.mdMarkdownGitHub ↗

Skill Review Checklist

Review new skills before adding to the library.

File Structure Check

Required	File	Purpose
✅	`skill.md`	Main skill file (lowercase!)
⚠️	`SETUP.md`	Setup guide (if skill needs API/config)
⚠️	`scripts/`	Helper scripts (if needed)
⚠️	`.env.example`	Example env file (never actual credentials!)

skill.md Requirements

Frontmatter (YAML header)

---
name: skill-name           # Required: kebab-case
description: "..."         # Required: trigger phrases
setup: "./SETUP.md"        # If SETUP.md exists
enhancedBy:                # Optional: complementary skills
  - other-skill: "Benefit description. Without it: fallback behavior"
usedBy:                    # Optional: for helper skills
  - parent-skill
---

Content Guidelines

Concise - Under 100 lines ideal, max 150
Workflow focused - How to use, not how to set up
Examples - Quick command examples
No setup instructions - Those go in SETUP.md

SETUP.md Requirements (if needed)

Step-by-step setup guide
API/account creation instructions
Credential configuration (.env)
Test commands to verify setup
Troubleshooting table

Docs Site Sync

After adding a skill, update docs/index.html:

1. Add skill card in skills-grid section 2. If skill has enhancedBy, add the combo badge:

<div class="skill-combo" style="...">
  <span style="color: var(--green-primary);">🔗 עובד טוב יותר עם:</span>
  <span style="color: var(--text-secondary);">skill-a, skill-b</span>
</div>

3. Create docs/skills/[skill-name].html guide page 4. Create docs/downloads/[skill-name].zip for download

Review Checklist

Before approving a new skill:

[ ] skill.md exists (lowercase)
[ ] Frontmatter has name and description
[ ] setup: "./SETUP.md" if SETUP.md exists
[ ] Content is under 150 lines
[ ] No credentials or API keys in any file
[ ] .gitignore includes .env and sensitive files
[ ] If scripts exist, they have --dry-run option
[ ] Docs site updated with skill card
[ ] Download ZIP created

Quality Standards

Good Descriptions (trigger phrases)

# Good - tells Claude when to use
description: "Send WhatsApp messages. Use when user says 'send message', 'whatsapp', 'הודעה'."

# Bad - too vague
description: "WhatsApp integration"

Good enhancedBy Format

# Good - explains benefit and fallback
enhancedBy:
  - get-contact: "Auto-lookup contact by name. Without it: ask user for phone directly"

# Bad - no context
enhancedBy:
  - get-contact

Command

Run review on a skill folder:

# Check structure
ls -la skills/[skill-name]/

# Check frontmatter
head -20 skills/[skill-name]/skill.md

# Check line count
wc -l skills/[skill-name]/skill.md