agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-collective-intelligence-coordinator40
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 label and invocation instruction rather than a functional description that would help Claude select the appropriate skill. Without any explanation of capabilities, use cases, or trigger conditions, this skill would be essentially invisible to Claude's skill selection process.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Coordinates multiple AI agents to solve complex problems, synthesizes diverse perspectives, manages collaborative workflows').
Include an explicit 'Use when...' clause with natural trigger terms users might say (e.g., 'Use when the user needs multi-agent collaboration, consensus building, or coordinating multiple perspectives on a problem').
Remove the invocation command from the description field - this belongs in usage instructions, not the description used for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for collective-intelligence-coordinator' is entirely 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 triggers. | 1 / 3 |
Trigger Term Quality | The only terms present are technical jargon ('agent skill', 'collective-intelligence-coordinator') and an invocation command. No natural keywords a user would say when needing this capability. | 1 / 3 |
Distinctiveness Conflict Risk | While the name 'collective-intelligence-coordinator' is unique, the description provides no context about what domain or tasks it handles, making it impossible to distinguish from other skills based on user intent. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
50%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 reasonable structure for a coordination agent with concrete memory operation examples, but suffers from abstract descriptions of core responsibilities (consensus building, Byzantine fault tolerance) without actionable implementation. The code examples have syntax issues and the workflow lacks explicit validation checkpoints for the complex distributed operations described.
Suggestions
Replace abstract descriptions of consensus building and Byzantine fault tolerance with concrete, executable code or specific step-by-step procedures
Fix JavaScript code syntax (add quotes to object keys) and ensure examples are copy-paste executable
Add explicit validation checkpoints and error recovery workflows for split-brain detection and quorum-based recovery
Consider linking to separate documentation files for detailed coordination patterns (Hierarchical, Mesh, Adaptive modes) to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary conceptual framing ('neural nexus of the hive mind system') and verbose descriptions of patterns that could be more compact. However, it does include concrete code examples and avoids excessive explanation of basic concepts. | 2 / 3 |
Actionability | Provides JavaScript code snippets for memory operations which are somewhat concrete, but the code uses non-standard syntax (missing quotes on object keys) and the broader coordination patterns (Byzantine fault tolerance, consensus building) are described abstractly without executable implementation details. | 2 / 3 |
Workflow Clarity | Lists responsibilities and patterns but lacks clear sequential workflows with validation checkpoints. The 'EVERY 30 SECONDS' requirement is specific but there's no error recovery flow or validation steps for the coordination processes described. | 2 / 3 |
Progressive Disclosure | Content is organized into logical sections with headers, but everything is inline in one file. References to other agents (swarm-memory-manager, queen-coordinator) could link to their documentation. The skill is moderately long and could benefit from splitting detailed patterns into separate files. | 2 / 3 |
Total | 8 / 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.
- 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.