agent-gossip-coordinator
Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-gossip-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/skillEvaluation — 85%
↑ 1.03xAgent success when using this skill
Validation 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 provides only an invocation command without explaining what the skill does, when to use it, or any natural trigger terms. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what gossip-coordinator actually does (e.g., 'Coordinates distributed system gossip protocols, manages node communication, handles cluster membership')
Include a 'Use when...' clause with explicit triggers (e.g., 'Use when working with distributed systems, cluster coordination, or node-to-node communication')
Replace technical jargon with natural keywords users might say when needing this functionality
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for gossip-coordinator' is completely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides invocation syntax without any functional description or usage guidance. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'gossip-coordinator' which is technical jargon, not a natural keyword users would say. No common user language is included. | 1 / 3 |
Distinctiveness Conflict Risk | While 'gossip-coordinator' is a unique term, the description is so vague that Claude cannot determine when to use it versus any other skill. The lack of context makes proper selection impossible. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%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 high-level architecture document than actionable guidance for Claude. It describes what a gossip coordinator should do conceptually but provides no executable code, specific commands, or concrete implementation steps. The content would benefit greatly from actual protocol implementations, code examples, and clear workflows with validation steps.
Suggestions
Add executable code examples for at least one gossip protocol implementation (e.g., push-pull gossip with actual message handling)
Include a concrete workflow with numbered steps and validation checkpoints for common operations like 'adding a new node to the gossip network'
Replace abstract descriptions like 'Execute Merkle tree comparison' with actual code or specific commands that Claude can run
Add links to reference files for detailed implementations (e.g., 'See [PROTOCOLS.md](PROTOCOLS.md) for push-pull implementation details')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some unnecessary abstraction and explanation. Phrases like 'Coordinates gossip-based consensus protocols for scalable eventually consistent distributed systems' repeat information, and the responsibilities section describes concepts rather than providing actionable guidance. | 2 / 3 |
Actionability | The content is entirely abstract and descriptive with no concrete code, commands, or executable examples. Phrases like 'Deploy push gossip protocol' and 'Execute Merkle tree comparison' describe what to do conceptually but provide zero implementation details or copy-paste ready guidance. | 1 / 3 |
Workflow Clarity | While sections are organized by topic, there are no clear step-by-step workflows, no validation checkpoints, and no sequenced processes. The content lists capabilities without explaining how to actually execute them in order or verify success. | 1 / 3 |
Progressive Disclosure | The content has reasonable section organization with headers, but there are no references to external files for detailed implementation. The collaboration section mentions other components but doesn't link to them. Content is neither monolithic nor well-structured for navigation. | 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.
- 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.