agent-gossip-coordinator

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

1.03x

Quality

16%

Does it follow best practices?

Impact

85%

1.03x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

28%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 content is a well-organized but hollow outline: it names the right concepts (push/pull gossip, anti-entropy, Merkle trees, vector clocks) yet provides nothing executable — no code, commands, or concrete procedure. The stray second YAML frontmatter block is pure token waste and should be deleted. The body reads like an agent registry entry rather than skill instructions.

Suggestions

Delete the duplicate YAML frontmatter block at the top of the body; frontmatter belongs only in the header, and the shell hooks/emoji echo lines add no instructional value.

Replace abstract directives with concrete guidance, e.g., a code snippet showing push/pull gossip message exchange, or specific commands a coordinator should issue at each step.

Convert the 'Core Responsibilities' taxonomy into a sequenced workflow with checkpoints, e.g., '1. Establish peer list 2. Run gossip rounds 3. Verify convergence via anti-entropy 4. Resolve conflicts with vector clocks'.

Dimension	Reasoning	Score
Conciseness	The body opens with a stray 24-line duplicate YAML frontmatter block (redundant metadata, priority, and emoji-laden shell hooks) that is pure padding, and the remaining bullets are abstract filler; this is noticeably verbose with several unnecessary sections.	2 / 5
Actionability	Every instruction is a high-level directive like 'Deploy push gossip protocol', 'Execute Merkle tree comparison', and 'Manage vector clocks' — no code, commands, parameters, or specific steps anywhere, so it describes rather than instructs.	2 / 5
Workflow Clarity	The numbered 'Core Responsibilities' list is a topic taxonomy, not a sequenced process; there is no ordering of when to do what, and no validation or convergence checkpoints despite the skill being about ensuring eventual consistency.	2 / 5
Progressive Disclosure	At ~38 lines with no bundle files, the skill qualifies for the simple-skill exception and its sections are cleanly headed, but the misplaced duplicate YAML block at the top muddies navigation and signals unclear authorship of the structure.	3 / 5
	Total	9 / 20 Passed

Description

3%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 description is effectively non-functional as a trigger: it communicates only an invocation command, not capabilities or use conditions. A user (or Claude) reading it could not decide when this skill should activate. It should be rewritten to state concrete actions and an explicit 'Use when...' clause.

Suggestions

Rewrite the description to state concrete capabilities, e.g., 'Coordinates gossip-based consensus protocols: push/pull epidemic dissemination, anti-entropy with Merkle trees, vector-clock conflict resolution, and membership management for eventually consistent systems.'

Add an explicit trigger clause, e.g., 'Use when the user mentions gossip protocols, epidemic dissemination, anti-entropy, eventual consistency, or peer-to-peer state synchronization.'

Remove the meta-instruction 'invoke with $agent-gossip-coordinator' — it wastes the description budget and adds no capability or trigger information.

Dimension	Reasoning	Score
Specificity	The description 'Agent skill for gossip-coordinator - invoke with $agent-gossip-coordinator' contains no concrete actions whatsoever; it is pure meta-instruction about how to invoke the skill, matching the 'entirely vague; no concrete actions' anchor.	1 / 5
Completeness	Neither 'what does this skill do' nor 'when should it be used' is stated; the description only says the skill exists and how to invoke it, matching the 'missing both what and when' anchor.	1 / 5
Trigger Term Quality	The only terms present are the skill name and '$agent-gossip-coordinator' invocation syntax — technical jargon rather than natural phrases a user would say (e.g., 'gossip protocol', 'eventual consistency', 'peer synchronization' are all absent).	1 / 5
Distinctiveness Conflict Risk	The 'Agent skill for...' framing is generic boilerplate that invites mis-triggering, though the niche term 'gossip-coordinator' limits overlap with unrelated skills — falling between the 'entirely generic' and 'very broad' anchors.	2 / 5
	Total	5 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/agent-gossip-coordinator/SKILL.md
Commit: b14c79e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.