Content
12%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an extremely verbose, largely non-actionable feature catalog for a hypothetical 'ruv-swarm' tool. Most code examples contain path syntax errors and reference non-existent CLI commands, making them non-executable. The document would benefit enormously from being reduced to a focused, tested workflow with actual working commands, splitting advanced topics into separate referenced files.
Suggestions
Replace hypothetical 'npx ruv-swarm github' commands with actual executable workflows using the MCP tools listed in the frontmatter (mcp__claude-flow__swarm_init, etc.) and gh CLI commands that actually work.
Fix all path syntax errors (e.g., 'repos$org/$repo' should be 'repos/org/repo', '$dev$null' should be '/dev/null') and verify scripts are executable.
Reduce the document to under 150 lines covering core workflows, and move communication strategies, synchronization patterns, advanced features, and troubleshooting into separate referenced files.
Add explicit validation checkpoints to the main workflows (e.g., verify PR creation succeeded, confirm test results before proceeding, validate repository access before batch operations).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400+ lines with massive amounts of speculative, non-executable content. Includes conceptual sections (GraphQL federation, Kafka config, Raft consensus, synchronization patterns) that are architectural abstractions rather than actionable instructions. Many sections repeat the same pattern of 'npx ruv-swarm github <command> --flags' without adding real value. The skill explains concepts Claude already knows (what eventual consistency is, what circuit breakers are) and includes best practices that are generic software engineering advice. | 1 / 3 |
Actionability | The vast majority of commands reference 'npx ruv-swarm' which appears to be a hypothetical/non-standard tool with no installation or verification instructions. Most code blocks are not executable - they're aspirational CLI invocations with invented flags. The bash scripts in sections 1-3 contain syntax errors (using '$' instead of '/' in paths like 'repos$org/$repo$contents$package.json') making them non-functional. The JavaScript, GraphQL, and YAML configuration examples are illustrative rather than executable. | 1 / 3 |
Workflow Clarity | Some workflows like 'Synchronized Operations' and 'Dependency Management' have reasonable step sequences (clone, modify, test, create PR, report failures). However, there are no explicit validation checkpoints, no error recovery loops beyond basic test failure reporting, and the overall document lacks a clear workflow for when/how to use this skill. The relationship between the many sections is unclear - it reads more like a feature catalog than a guided workflow. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no content split into supporting files despite the massive length. References to 'swarm-pr.md' and 'project-board-sync.md' at the bottom, but no bundle files are provided. The document dumps everything inline - configuration examples, communication strategies, synchronization patterns, troubleshooting, use cases - all in one enormous file that would be far better organized across multiple referenced documents. | 1 / 3 |
Total | 5 / 12 Passed |