Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is feature-rich with concrete gh CLI commands and complete code samples, but it is far too verbose and repetitive, leans on unverified ruv-swarm subcommands, and ships as a monolithic file with no progressive disclosure or bundle references. Verification checkpoints are missing for the destructive/batch workflows.
Suggestions
Cut repetition: collapse the near-identical per-agent review command sections into one parameterized example plus a short agent list, and remove 'Benefits' checklists and marketing prose.
Add explicit validation/verification steps before destructive or batch operations (e.g. validate review output and run tests before `--push-changes` or `gh pr merge --auto`).
Move detailed reference material (agent check lists, config schemas, templates) into separate files under references/ and link to them from a concise overview, so SKILL.md acts as a lean entry point.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | At ~1138 lines the body is heavily padded with a large table of contents, 'Benefits' checklists, repeated near-identical `npx ruv-swarm` command blocks across agent sections, and feature-marketing JSON lists, much of which restates the product's capabilities rather than adding what Claude does not already know. | 1 / 3 |
Actionability | Provides many concrete, real `gh` commands and complete code blocks, but the central `npx ruv-swarm` subcommands (e.g. review-security, review-learn, pr-topology) appear unverified/aspirational rather than confirmed-executable, leaving key details uncertain. | 2 / 3 |
Workflow Clarity | Multi-step workflows are present and sequenced (e.g. the security review branch on severity, the GitHub Actions pipeline), but destructive/batch operations like auto-fix-with-push and auto-merge lack explicit validation checkpoints, capping this dimension at 2. | 2 / 3 |
Progressive Disclosure | The skill is a single monolithic file with no bundle references (references/, scripts/, assets/ are absent); collapsible <details> blocks and a ToC offer some structure, but large amounts of content that belong in separate reference files remain inline. | 2 / 3 |
Total | 7 / 12 Passed |