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 only an invocation command and a label ('coordinator-swarm-init') without explaining what the skill does, when to use it, or what problem it solves. Claude would have no meaningful basis for selecting this skill from a list of available options.
Suggestions
Describe the concrete actions this skill performs (e.g., 'Initializes a multi-agent swarm by spawning coordinator agents, distributing tasks, and setting up inter-agent communication').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user wants to set up parallel agent workflows, coordinate multiple sub-agents, or distribute a large task across a swarm').
Remove the invocation syntax from the description and replace it with functional content—invocation details belong in the skill body, not the description used for skill selection.
| 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 the invocation command, providing no functional or contextual information. | 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 distinguishing characteristics. Without knowing what the skill does, it could conflict with any agent or coordination-related skill. | 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 conceptual overview or README than an actionable skill file. It describes what the swarm initializer does at a high level but fails to provide concrete, executable guidance for actually performing initialization. The content is verbose with obvious advice and lacks the specific commands, code examples, and validation checkpoints needed to make it useful.
Suggestions
Replace the vague 'Usage Examples' section with concrete, executable CLI commands showing how to actually initialize a swarm (e.g., full `npx claude-flow` commands with real arguments and expected outputs).
Add executable code examples for the Mandatory Memory Coordination Protocol showing the exact memory store/retrieve commands each agent should run, rather than just listing key patterns.
Add explicit validation checkpoints to the workflow, such as verifying all agents have written their initial status before proceeding to task orchestration, with error recovery steps if agents fail to register.
Remove obvious best practices and conceptual explanations (e.g., topology descriptions Claude already knows) to reduce token usage by at least 50%.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains many concepts Claude already knows (what topologies are, what resource allocation means, generic best practices like 'choose topology based on task characteristics'). Much of the content is descriptive rather than instructive, and sections like 'Integration Points' and 'Best Practices' are padded with obvious advice. | 1 / 3 |
Actionability | Despite describing a complex coordination task, the skill provides no executable code, no concrete commands for initializing a swarm, and no specific configuration examples. The 'Usage Examples' section just lists vague prompts rather than showing actual commands or code. The memory coordination protocol lists key patterns but without executable examples of the actual CLI calls. | 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 verification steps to confirm agents are actually writing to memory as required. | 2 / 3 |
Progressive Disclosure | The content has reasonable section structure with headers, but it's a monolithic document with no references to external files for detailed content. The topology details, memory protocol specifics, and integration patterns could be split into separate reference files. No bundle files are provided to support 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
9d4a9ea
- 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.