Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator
35
3%
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 problem it solves. It reads as a placeholder or auto-generated stub rather than a functional description for skill selection.
Suggestions
Add concrete actions describing what gossip-coordinator actually does (e.g., 'Coordinates gossip protocol messages across distributed nodes' or whatever its actual function is).
Add an explicit 'Use when...' clause with natural trigger terms that describe the scenarios where this skill should be selected.
Replace the generic 'Agent skill for' prefix with a substantive description of capabilities, inputs, and outputs so Claude can distinguish this from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains 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 provides no clear niche. 'Agent skill' is generic and 'gossip-coordinator' is opaque, making it impossible to distinguish from other skills or know when it should be selected. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
7%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 feature wishlist or capability description rather than an actionable skill. It lacks any concrete implementation guidance—no code, no commands, no algorithms, no data structures, no examples. Every bullet point describes what to do at a conceptual level without explaining how, making it nearly useless as operational guidance for Claude.
Suggestions
Add concrete, executable code examples for core operations like implementing a push-pull gossip round, peer selection, or Merkle tree comparison
Define a clear step-by-step workflow for common gossip protocol tasks (e.g., 'when a new node joins' or 'when propagating an update') with explicit validation/convergence checks
Remove or drastically condense the abstract bullet points that describe concepts Claude already knows (e.g., 'Ensure eventual consistency through state synchronization') and replace with specific implementation details
Add concrete data structure definitions (e.g., message format, vector clock schema, membership list structure) that Claude can directly use
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and describes concepts at a high level that Claude already understands. Phrases like 'Implement push-pull hybrid approach for optimal convergence' and 'Ensure eventual consistency through state synchronization' are abstract descriptions that don't add actionable knowledge. The entire body reads like a feature list rather than instructions. | 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 directive like 'Deploy push gossip protocol' or 'Execute Merkle tree comparison' without any implementation details, algorithms, data structures, or code snippets. | 1 / 3 |
Workflow Clarity | There is no clear sequencing of steps, no validation checkpoints, and no feedback loops. The content lists responsibilities and approaches as unordered bullet points without defining when or how to execute them, or how to verify correctness of gossip protocol operations. | 1 / 3 |
Progressive Disclosure | The content has some structural organization with headers and subsections, which provides basic navigability. However, there are no references to external files for detailed implementations, and the sections themselves contain only shallow bullet points rather than useful overview content that points to deeper resources. | 2 / 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.
f547cec
Table of Contents
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.