agent-coordinator-swarm-init
Agent skill for coordinator-swarm-init - invoke with $agent-coordinator-swarm-init
39
10%
Does it follow best practices?
Impact
87%
2.80xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-coordinator-swarm-init/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an extremely weak description that fails on every dimension. It provides no information about what the skill does, when it should be used, or what user requests should trigger it. It reads as a placeholder or auto-generated stub rather than a functional skill description.
Suggestions
Replace the entire description with concrete actions the skill performs (e.g., 'Initializes a multi-agent swarm by coordinating task distribution, spawning sub-agents, and managing parallel workflows').
Add an explicit 'Use when...' clause describing the scenarios and user requests that should trigger this skill (e.g., 'Use when the user wants to set up a coordinated multi-agent workflow or parallelize tasks across multiple agents').
Include natural trigger terms that users would actually say, such as 'parallel tasks', 'multi-agent', 'swarm', 'coordinate agents', 'distribute work'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for coordinator-swarm-init' is entirely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states how to invoke it, not what it does or when it should be selected. | 1 / 3 |
Trigger Term Quality | The only terms present are technical jargon ('coordinator-swarm-init', '$agent-coordinator-swarm-init') that no user would naturally say. There are no natural language keywords that would help match user requests. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no basis for distinguishing this skill from any other. 'Agent skill for coordinator-swarm-init' gives no indication of its domain or purpose. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
20%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level design document than an actionable skill for Claude. It describes concepts and patterns abstractly without providing executable commands, concrete configuration examples, or validation steps. The verbose best practices and integration points sections add little value while consuming significant token budget.
Suggestions
Replace the abstract 'Usage Examples' with concrete, executable initialization commands (e.g., actual `npx claude-flow` commands with real arguments for each topology type)
Add a concrete workflow with validation checkpoints, e.g., 'Run X command → verify output contains Y → if not, run Z to diagnose'
Remove the generic Best Practices and Error Handling sections (Claude knows not to over-provision) and replace with specific configuration parameters, default values, and edge cases unique to this system
Provide a complete, copy-paste ready example of initializing a swarm with the memory coordination protocol, showing exact memory keys and expected JSON payloads
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with information Claude already knows (what topologies are, generic best practices like 'don't over-provision'). The 'Integration Points', 'Handoff Patterns', and 'Best Practices' sections are largely generic advice that doesn't add actionable value. The error handling section is entirely vague platitudes. | 1 / 3 |
Actionability | Despite describing a complex initialization process, there is no executable code, no concrete commands for actually initializing a swarm, no specific configuration examples, and no copy-paste ready snippets. The 'Usage Examples' section just lists natural language prompts rather than actual implementation steps. The memory key patterns use inconsistent delimiters ($ vs /) without explanation. | 1 / 3 |
Workflow Clarity | The MANDATORY Memory Coordination Protocol provides a numbered sequence of steps, and the Handoff Patterns show multi-step flows. However, there are no validation checkpoints, no error recovery feedback loops, and no concrete commands for verifying that agents have properly written to memory or that initialization succeeded. | 2 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, which aids navigation. However, it's a monolithic document with no references to external files for detailed configuration, API references, or examples. Content like topology details and memory protocol could be split out for better progressive disclosure. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
01070ed
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.