Individual skill
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.
skills/review-a-skill/SKILL.md
Source commit 6d95c788aa22ce39a4807b9a4c31c758a2036dc6
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 10, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,156
- Repository last updated
- Sep 21, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- claude-code Repository topic
- cli Repository topic
- codex Repository topic
- cursor Repository topic
- developer-tools Repository topic
- productivity Repository topic
- ai-agents Repository topic
- mcp Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# 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