Content
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely verbose and largely built around hypothetical CLI tools (ruv-swarm, claude-flow) with invented subcommands that cannot be verified as real or executable. The document reads more like a product feature wishlist or marketing spec than actionable instructions for Claude. While it demonstrates some structural organization with collapsible sections and a quick reference, the sheer volume of speculative content overwhelms any useful guidance.
Suggestions
Verify that all CLI commands (especially npx ruv-swarm and mcp__claude-flow__ calls) are real, documented tools - remove or clearly mark any hypothetical/aspirational commands
Reduce the document to under 150 lines focusing only on proven, executable workflows using gh CLI and real tools, moving templates and configs to separate bundle files
Add explicit validation checkpoints and error handling to multi-step workflows (e.g., check if gh project commands succeed before proceeding)
Replace the pseudo-JavaScript MCP tool calls with actual executable code or clearly document the expected tool interface
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at 700+ lines. Massive amounts of speculative CLI commands for tools (ruv-swarm, claude-flow) that appear hypothetical. Includes extensive templates, dashboard JSON configs, and repetitive patterns that bloat the document enormously. Much content describes aspirational features rather than providing actionable instructions Claude needs. | 1 / 3 |
Actionability | Nearly all commands reference 'npx ruv-swarm github ...' with dozens of subcommands and flags that appear to be invented/hypothetical rather than documented real tools. The gh CLI commands are real but basic. The JavaScript blocks use pseudo-API syntax (mcp__claude-flow__swarm_init) that isn't executable. Most content describes what a tool *would* do rather than providing verified, executable guidance. | 1 / 3 |
Workflow Clarity | The 'Complete Workflow Example' section at the end provides a reasonable 5-step sequence, and some individual sections have logical ordering. However, there are no validation checkpoints, no error handling guidance, no feedback loops for when commands fail, and the overall document is so sprawling that the actual workflow gets lost among dozens of disconnected command snippets. | 2 / 3 |
Progressive Disclosure | Uses HTML <details> tags for collapsible sections which is a reasonable progressive disclosure technique. Has a Quick Reference section at the end. However, with no bundle files, all 700+ lines are crammed into one file. The templates, workflow configs, and detailed analytics sections should be in separate referenced files. The document is essentially a monolithic wall despite the collapsible sections. | 2 / 3 |
Total | 6 / 12 Passed |