review-a-skill — Claude Code skill: review and install
review-a-skill reviews a skill before it enters a library by checking metadata, structure, safety, and dependencies. Use it when the choice is keep, curate, or remove.
MIT 177 installs ★ 1,161 updated 2026-09-21
npx skills add MoizIbnYousaf/ai-agent-skills --skill review-a-skill -a claude-codeWhat review-a-skill does
This skill guides a review of one library entry. It previews the content with npx ai-agent-skills preview <skill-name>, inspects selected catalog fields as JSON, validates the SKILL.md frontmatter structure, and supports a keep, curate, or remove decision. Automated pipelines should use --format json and narrow catalog output with --fields.
Changes start with --dry-run. Before removal, inspect dependencies with info --format json, including dependencies.usedBy; removing a skill used by others breaks the dependency graph. The preview command fully works only for vendored skills, while validate checks frontmatter structure rather than content quality.
What it helps with
- inspect a skill for suspicious instructions
- check catalog metadata and frontmatter
- validate the
SKILL.mdstructure - choose whether to keep, curate, or remove a skill
Example prompts for the agent
- Review
my-skillbefore adding it to the library. - Show
my-skillmetadata as JSON and inspect its dependencies. - Run a dry removal for
my-skill, then checkdependencies.usedBy.
How to install review-a-skill
1Skills CLI (Vercel)
npx skills add MoizIbnYousaf/ai-agent-skills --skill review-a-skill -a claude-code2Manually: put the files in place
~/.claude/skills/review-a-skill/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-a-skill/
1Skills CLI (Vercel)
npx skills add MoizIbnYousaf/ai-agent-skills --skill review-a-skill -a codex2Manually: put the files in place
.agents/skills/review-a-skill/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add MoizIbnYousaf/ai-agent-skills --skill review-a-skill -a cursor2Manually: put the files in place
.cursor/skills/review-a-skill/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install MoizIbnYousaf/ai-agent-skills skills/review-a-skill2Manually: put the files in place
.github/skills/review-a-skill/SKILL.md1Skills CLI (Vercel)
npx skills add MoizIbnYousaf/ai-agent-skills --skill review-a-skill -a gemini-cli2Platform CLI
gemini skills install https://github.com/MoizIbnYousaf/ai-agent-skills --path skills/review-a-skillManually: put the files in place
.devin/skills/review-a-skill/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add MoizIbnYousaf/ai-agent-skills --skill review-a-skill -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-a-skill
How do I install review-a-skill in Claude Code?
Run npx skills add MoizIbnYousaf/ai-agent-skills --skill review-a-skill -a claude-code, then use ~/.claude/skills/review-a-skill/SKILL.md.
What does review-a-skill do?
It previews a skill, checks catalog metadata and SKILL.md structure, then supports a keep, curate, or remove decision.
What should I check before removing a skill?
Inspect dependencies with info --format json and review dependencies.usedBy. Removing a skill that other skills use breaks the dependency graph.
Source text
SKILL.md · MIT
--- name: review-a-skill description: Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove. category: workflow version: 4.1.0 --- # Review A Skill ## Goal Evaluate a single skill's quality, relevance, and safety before it enters or stays in a library. ## Guardrails - Always use `--format json` for machine-readable output in automated pipelines. - Always use `--fields` to limit output size when inspecting catalog entries. - Always use `--dry-run` before curating or removing a skill. - Never remove a skill without first checking if other skills depend on it via `info --format json` dependencies. ## Workflow 1. Preview the skill content to check for quality and safety. ```bash npx ai-agent-skills preview <skill-name> ``` The preview command sanitizes content — if it flags sanitization, investigate before proceeding. 2. Inspect the catalog entry for metadata completeness. ```bash npx ai-agent-skills info <skill-name> --format json --fields name,description,tags,collections,dependencies ``` 3. Validate the skill's SKILL.md structure. ```bash npx ai-agent-skills validate <skill-name> ``` 4. If the skill needs curation (notes, collections, verification): ```bash npx ai-agent-skills curate <skill-name> --notes "Reviewed: solid patterns" --verify --dry-run npx ai-agent-skills curate <skill-name> --notes "Reviewed: solid patterns" --verify ``` 5. If the skill should be removed: ```bash npx ai-agent-skills curate <skill-name> --remove --dry-run npx ai-agent-skills curate <skill-name> --remove --yes ``` ## Decision Criteria - **Keep**: Clear description, valid frontmatter, useful to the library's audience, no injection patterns. - **Curate**: Needs better whyHere, collection placement, or verification status. - **Remove**: Duplicate, outdated, broken source, or contains suspicious content. ## Gotchas - The `preview` command only works for vendored (house) skills. Upstream skills show description and whyHere only. - The `validate` command checks frontmatter structure but not content quality — that requires human or agent judgment. - Removing a skill that other skills depend on will break the dependency graph. Always check `dependencies.usedBy` first.
© MoizIbnYousaf · MIT · MoizIbnYousaf/ai-agent-skills