agent-collective-intelligence-coordinator
Agent skill for collective-intelligence-coordinator - invoke with $agent-collective-intelligence-coordinator
39
7%
Does it follow best practices?
Impact
94%
1.74xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-collective-intelligence-coordinator/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 essentially a label and invocation command with zero functional content. It fails on every dimension: it doesn't describe what the skill does, when to use it, or provide any natural trigger terms. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Add a clear 'what' clause describing the concrete actions this skill performs (e.g., 'Coordinates multiple agents to synthesize diverse perspectives, aggregate responses, and resolve conflicting viewpoints').
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks for brainstorming with multiple perspectives, consensus building, or aggregating diverse viewpoints').
Remove the invocation syntax from the description and replace it with functional content that distinguishes this skill from other collaboration or multi-agent skills.
| 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 | 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 keyword is 'collective-intelligence-coordinator', which is a technical/internal name, not a natural term a user would say. No natural language trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from any other agent skill. 'Collective intelligence coordinator' could overlap with collaboration, brainstorming, multi-agent, or aggregation skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
14%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 design document than actionable instructions for Claude. It is filled with abstract buzzwords ('hive mind', 'neural nexus', 'Byzantine fault tolerance') without concrete implementations, and the few code examples use placeholder values. The skill lacks clear sequential workflows, validation steps, and any progressive disclosure structure despite covering many complex topics superficially.
Suggestions
Replace abstract descriptions ('Apply weighted voting based on expertise', 'Resolve conflicts through Byzantine fault tolerance') with concrete, executable code examples showing exactly how to implement these patterns using the available MCP tools.
Add a clear step-by-step workflow with validation checkpoints for the core coordination loop (e.g., 1. Read current state → 2. Aggregate inputs → 3. Validate consensus threshold → 4. If below threshold, retry → 5. Store decision).
Remove verbose conceptual explanations Claude already knows (distributed systems concepts, topology descriptions) and focus on the specific tool calls, key naming conventions, and data schemas required.
Split detailed topics (consensus algorithms, error handling, coordination patterns) into separate referenced files, keeping SKILL.md as a concise overview with clear navigation links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with many abstract concepts Claude already understands (Byzantine fault tolerance, mesh topologies, cognitive load balancing). Heavy use of buzzwords like 'neural nexus of the hive mind' and 'distributed cognitive processes' that add no actionable value. Much of the content describes concepts rather than providing concrete instructions. | 1 / 3 |
Actionability | The JavaScript code blocks show specific MCP tool calls with concrete key/namespace patterns, which is somewhat actionable. However, much of the skill is abstract guidance ('Apply weighted voting based on expertise', 'Resolve conflicts through Byzantine fault tolerance') with no concrete implementation. The code examples use placeholder values rather than real executable patterns. | 2 / 3 |
Workflow Clarity | Despite describing complex multi-step coordination processes, there are no clear sequential workflows with validation checkpoints. The 'Handoff Patterns' section lists abstract sequences without concrete steps. The 'EVERY 30 SECONDS' requirement has no validation or error recovery mechanism. No feedback loops for detecting or recovering from failures despite mentioning 'split-brain scenarios' and 'quorum-based recovery' without explaining how. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files for detailed topics. Complex subjects like consensus building, cognitive load balancing, and error handling are all crammed into one file with shallow treatment. No navigation aids or links to deeper documentation. | 1 / 3 |
Total | 5 / 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/ruflo
- Commit
398f7c2
- 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.