agent-gossip-coordinator
Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator
33
0%
Does it follow best practices?
Impact
85%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-gossip-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 critically deficient across all dimensions. It provides no information about what the skill does, when it should be used, or what domain it operates in. The only content is a generic label ('Agent skill for gossip-coordinator') and an invocation command, which is insufficient for Claude to make any informed selection decision.
Suggestions
Add a clear description of what the gossip-coordinator skill actually does — list specific concrete actions it performs (e.g., 'Coordinates gossip protocol messages across distributed nodes, manages peer membership, and handles failure detection').
Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios when this skill should be selected (e.g., 'Use when the user asks about gossip protocol configuration, cluster membership, or node communication').
Remove the invocation instruction ('invoke with $agent-gossip-coordinator') from the description field, as this is operational metadata rather than descriptive content that helps with skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Agent skill for gossip-coordinator' is entirely vague and does not describe 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 it's an agent skill and how to invoke it, with no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'gossip-coordinator', which is technical jargon unlikely to be used naturally by users. There are no natural trigger terms that a user would say when needing this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from other skills. 'Agent skill' is entirely generic and provides no niche or distinct triggers. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a high-level description of gossip protocol concepts rather than actionable instructions for Claude. It lacks any concrete code, commands, specific tools, workflows, or examples. The content describes what gossip protocols are rather than teaching Claude how to implement or coordinate them in a specific system.
Suggestions
Replace abstract descriptions with concrete, executable code examples showing how to implement gossip dissemination, peer selection, and state synchronization with specific libraries or tools.
Add a clear step-by-step workflow with validation checkpoints, e.g., '1. Initialize peer list → 2. Send gossip round → 3. Verify convergence metric → 4. If not converged, adjust fanout and retry'.
Remove explanations of well-known distributed systems concepts (vector clocks, Merkle trees, anti-entropy) and instead provide specific configuration parameters, thresholds, and decision criteria Claude should use.
Add supporting bundle files (e.g., example configurations, protocol implementations, test scripts) and reference them from the SKILL.md for progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and describes concepts at a high level that Claude already understands (gossip protocols, anti-entropy, vector clocks, Merkle trees). It reads like a textbook overview rather than actionable instructions, with many bullet points that restate well-known distributed systems concepts without adding novel, specific guidance. | 1 / 3 |
Actionability | There is no concrete code, no executable commands, no specific examples, and no copy-paste ready guidance. Every bullet point is a vague description like 'Deploy push gossip protocol' or 'Execute Merkle tree comparison' without any implementation details, parameters, APIs, or tools to use. | 1 / 3 |
Workflow Clarity | There is no clear sequenced workflow, no step-by-step process, and no validation checkpoints. The content lists categories of responsibilities but never defines when or how to perform them, nor provides any error recovery or feedback loops for these distributed system operations. | 1 / 3 |
Progressive Disclosure | The content is a monolithic list of abstract responsibilities with no references to supporting files, no links to detailed documentation, and no bundle files to support it. There is no navigation structure or layered content organization. | 1 / 3 |
Total | 4 / 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
d29d87f
- 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.