agent-coordinator-swarm-init
Agent skill for coordinator-swarm-init - invoke with $agent-coordinator-swarm-init
44
Quality
17%
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 description is critically deficient across all dimensions. It functions only as a technical reference for invocation syntax rather than a meaningful skill description. Claude would have no basis for selecting this skill appropriately since there is no information about what it does, when to use it, or what problems it solves.
Suggestions
Add explicit capability statements describing what 'coordinator-swarm-init' actually does (e.g., 'Initializes and coordinates multiple parallel agent tasks' or 'Sets up swarm-based distributed processing').
Include a 'Use when...' clause with natural trigger terms users might say (e.g., 'Use when the user needs to coordinate multiple agents, initialize parallel workflows, or set up distributed task processing').
Remove or relocate the invocation syntax ('invoke with $agent-coordinator-swarm-init') to a separate field, as it provides no selection value and wastes description space.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for coordinator-swarm-init' is completely abstract with no indication of what the skill actually does. | 1 / 3 |
Completeness | Missing both 'what does this do' and 'when should Claude use it'. The description only provides an invocation command with no explanation of purpose or trigger conditions. | 1 / 3 |
Trigger Term Quality | Contains only technical jargon ('coordinator-swarm-init', '$agent-coordinator-swarm-init') that users would never naturally say. No natural keywords like 'coordinate', 'initialize', 'swarm', or task-related terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | While the technical name is unique, the description is so vague that Claude cannot determine when to use it versus any other agent or coordination skill. No distinguishing characteristics are provided. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a conceptual overview of swarm initialization but lacks the concrete, executable guidance needed for actionability. The memory coordination protocol is a good idea but needs actual code examples showing how to implement it. The content is moderately verbose with explanations Claude doesn't need (topology definitions, generic best practices).
Suggestions
Add executable code examples for the MANDATORY Memory Coordination Protocol showing actual npx claude-flow commands agents should run
Replace vague usage examples ('Initialize a swarm for building a REST API') with concrete command invocations and expected outputs
Add validation checkpoints to the workflow - e.g., how to verify agents are writing to memory before proceeding
Remove generic explanations of topology types and best practices that Claude already knows; focus on project-specific configurations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary explanation (e.g., describing what each topology is for when Claude knows this) and verbose sections like 'Best Practices' with generic advice. The YAML frontmatter hooks are useful but the body has padding. | 2 / 3 |
Actionability | Lacks concrete, executable code or commands in the body. Usage examples are vague prompts ('Initialize a swarm for building a REST API') rather than actual commands or code. The memory protocol lists requirements but provides no executable examples of how to implement them. | 1 / 3 |
Workflow Clarity | The MANDATORY Memory Coordination Protocol provides a numbered sequence, but lacks validation checkpoints or error recovery steps. Handoff patterns are listed but not detailed enough to execute. No feedback loops for verifying agents are actually writing to memory. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. References to other agents (Task Orchestrator, Agent Spawner) could link to their documentation. No external references for detailed configuration options. | 2 / 3 |
Total | 7 / 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
b2618f9
- 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.