skill-review
Use when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template ownership, output readability, validation gaps, or whether a skill should be edited.
npx skills add QoderAI/better-harness --skill skill-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill Review Review a skill as an execution contract, not as prose. Trace how an agent would enter, load, delegate, produce artifacts, and verify results; then report the smallest changes that would improve that chain. ## Review Workflow 1. Resolve the target skill or prompt chain. If the user names a path, stay on that path and its directly linked resources. 2. Read repo instructions first: nearest `AGENTS.md`, plugin manifests, and the target `SKILL.md` frontmatter/body. 3. Trace the chain from entrypoint to references, templates, scripts, detectors, tests, generated artifacts, and validation commands. Build an ownership map: what file owns workflow, output structure, runtime rules, style, and tests. 4. Audit the contract before editing. Use [Audit Checklist](references/audit-checklist.md) and [Reference Patterns](references/reference-patterns.md) as lenses. 5. If the user asked for changes, patch only the smallest owning files. Keep generated helpers, smoke scripts, and local experiments outside `SKILL.md` unless they are durable resources the skill must use. 6. Validate with the lightest real gate available: skill validator, repo tests, plugin validation, or a bounded agent s
- Review Workflow
- Review Lenses
- Finding Severity
- Report Shape
What does the skill-review skill do?
Use when reviewing Codex, Qoder, or repo-local skills and their prompt chains for trigger quality, workflow clarity, progressive disclosure, duplicated instructions, template ownership, output readability, validation gaps, or whether a skill should be edited.
How do I install it?
Run `npx skills add QoderAI/better-harness --skill skill-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From QoderAI/better-harness, a repository with 1,619 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.