CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-gossip-coordinator

Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator

52

1.03x
Quality

30%

Does it follow best practices?

Impact

85%

1.03x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-gossip-coordinator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

40%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a clean high-level catalog of gossip-protocol responsibilities with good section organization, but it is purely descriptive. It lacks executable guidance, concrete tools/parameters, and any sequenced workflow with validation checkpoints for the destructive or consistency-critical operations it coordinates.

Suggestions

Replace abstract bullet actions with concrete, executable guidance: name specific libraries/commands, fanout parameters, and code snippets for push-pull rounds and Merkle-tree reconciliation.

Add a sequenced workflow (e.g. select peers -> push-pull round -> detect drift via Merkle comparison -> resolve conflicts -> verify convergence) with explicit validation checkpoints and feedback loops, since conflict resolution and membership changes are consistency-critical.

Remove the duplicated second YAML metadata block that precedes the markdown; it inflates the body and adds noise without contributing to the skill instructions.

DimensionReasoningScore

Conciseness

The body is mostly efficient bullet points, but it re-describes well-known concepts (vector clocks, Merkle trees, push/pull gossip) that Claude already understands, and the leading extra YAML block duplicates metadata, adding some removable padding.

3 / 5

Actionability

The content only describes responsibilities at a high level ('Implement push gossip protocol', 'Execute Merkle tree comparison') with no concrete commands, code, libraries, parameters, or executable steps, matching 'minimal concrete guidance; high-level hints.'

2 / 5

Workflow Clarity

It groups responsibilities into categories but provides no sequenced procedure, no concrete workflow, and no validation checkpoints for operations (state synchronization, conflict resolution) that are inherently error-prone, matching 'rough sequence present but many gaps; validation absent.'

2 / 5

Progressive Disclosure

The body is a short, well-organized overview with clear section headers and no nested external references; the under-50-line simple-skill exception applies, though the stray duplicated YAML frontmatter block mid-file is a minor organization gap keeping it from 5.

4 / 5

Total

11

/

20

Passed

Description

21%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The frontmatter description is essentially a placeholder: it names the skill and gives an invocation syntax but states no concrete capabilities or trigger conditions. It fails to tell Claude what the skill does or when to use it.

Suggestions

Rewrite the description to state concrete actions, e.g. 'Coordinates gossip-based epidemic dissemination, peer selection, and state synchronization for eventually consistent distributed systems.'

Add an explicit 'Use when...' clause naming natural trigger phrases such as 'gossip protocol', 'epidemic dissemination', 'eventual consistency', or 'peer membership'.

Drop the redundant invocation syntax '$agent-gossip-coordinator' from the user-facing description; it does not help Claude decide when to invoke the skill.

DimensionReasoningScore

Specificity

The description 'Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator' names the domain (gossip-coordinator) but lists no concrete actions or capabilities, matching the 'names the domain but actions are minimal or generic' anchor.

2 / 5

Completeness

It offers only a vague 'what' (an 'agent skill for gossip-coordinator') and no 'when' trigger guidance; the invoke syntax is not a use-when clause, matching 'has a vague what and no when.'

2 / 5

Trigger Term Quality

The only keyword is the internal 'gossip-coordinator' token and an invocation syntax '$agent-gossip-coordinator'; there are no natural phrases a user would actually say, so it matches 'no natural keywords; only technical jargon.'

1 / 5

Distinctiveness Conflict Risk

'gossip-coordinator' is a somewhat specific niche label that reduces broad overlap, but the generic 'Agent skill for...' framing leaves it vague enough to potentially overlap with related distributed-systems coordinator skills.

3 / 5

Total

8

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/ruflo
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.