MCPInstall

review-a-skill

Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.

Installs
175
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/moizibnyousaf/ai-agent-skills --skill review-a-skill
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads review-a-skill automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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.
npx ai-agent-skills preview <skill-name>

The preview command sanitizes content — if it flags sanitization, investigate before proceeding.

  1. Inspect the catalog entry for metadata completeness.
npx ai-agent-skills info <skill-name> --format json --fields name,description,tags,collections,dependencies
  1. Validate the skill's SKILL.md structure.
npx ai-agent-skills validate <skill-name>
  1. If the skill needs curation (notes, collections, verification):
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
  1. If the skill should be removed:
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.

FAQ

What does the review-a-skill skill do?

Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.

How do I install review-a-skill?

Run npx skills add https://github.com/moizibnyousaf/ai-agent-skills --skill review-a-skill in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review-a-skill/ (personal) or .claude/skills/review-a-skill/ (project).

Which AI agents can use review-a-skill?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is review-a-skill safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains review-a-skill?

It is published by moizibnyousaf in moizibnyousaf/ai-agent-skills. It has 175 recorded installs.

More from moizibnyousaf/ai-agent-skills

View all →

code-review

moizibnyousaf/ai-agent-skills

Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.

backend-development

moizibnyousaf/ai-agent-skills

Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.

Backend & APIs869 installs

database-design

moizibnyousaf/ai-agent-skills

Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases. Use for designing schemas, writing migrations, or optimizing queries.

Data & Databases604 installs

code-refactoring

moizibnyousaf/ai-agent-skills

Code refactoring patterns and techniques for improving code quality without changing behavior. Use for cleaning up legacy code, reducing complexity, or improving maintainability.

code-documentation

moizibnyousaf/ai-agent-skills

Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.

Docs & Writing563 installs

best-practices

moizibnyousaf/ai-agent-skills

Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.