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 options.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Coordinates multi-agent brainstorming sessions, synthesizes diverse perspectives, and aggregates collective insights').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks for group brainstorming, collective decision-making, synthesizing multiple viewpoints, or coordinating multi-agent collaboration').
Remove the invocation syntax from the description and replace it with functional content that helps Claude distinguish this skill from others.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides 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 other skills. 'Collective intelligence coordinator' could overlap with collaboration, brainstorming, multi-agent, or any number of other 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 an aspirational architecture document than an actionable skill for Claude. It is filled with abstract concepts (Byzantine fault tolerance, split-brain scenarios, mesh topology) without concrete implementations, and explains high-level ideas Claude already understands. The JavaScript examples provide some structure but use placeholder values and lack real executable context.
Suggestions
Replace abstract descriptions ('Apply weighted voting based on expertise', 'Resolve conflicts through Byzantine fault tolerance') with concrete, executable code or step-by-step procedures showing exactly how to perform these operations using available MCP tools.
Remove verbose conceptual explanations and role-playing framing ('neural nexus of the hive mind system') — focus only on what Claude needs to do differently from its default behavior.
Add a clear sequential workflow with validation checkpoints: e.g., Step 1: Check existing collective state → Step 2: Gather agent inputs → Step 3: Validate quorum → Step 4: Store consensus decision, with explicit error handling at each step.
Extract coordination patterns and integration points into separate reference files, keeping SKILL.md as a concise quick-start guide with links to detailed documentation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose and filled with abstract concepts Claude already understands (consensus building, Byzantine fault tolerance, cognitive load balancing). Much of the content reads like a design document rather than actionable instructions, and terms like 'neural nexus of the hive mind system' are pure padding. | 1 / 3 |
Actionability | The JavaScript code blocks show concrete MCP tool calls with specific keys and namespaces, which is somewhat actionable. However, much of the content is vague direction ('Apply weighted voting based on expertise', 'Detect split-brain scenarios') without concrete implementation details or executable steps. | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for how to actually coordinate collective intelligence. The 'Handoff Patterns' section lists abstract flows without concrete steps or validation checkpoints. The '30 seconds' memory requirement is arbitrary with no mechanism for verification or error recovery. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no bundle files to support it. All content is inline with no clear hierarchy between essential quick-start information and advanced/reference material. | 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
619b263
- 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.