agent-raft-manager

Agent skill for raft-manager - invoke with $agent-raft-manager

0.96x

Quality

Does it follow best practices?

Impact

90%

0.96x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-raft-manager/SKILL.md

Quality

Discovery

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 is an extremely weak description that provides virtually no useful information for skill selection. It only names the skill and its invocation command without describing any capabilities, use cases, or trigger conditions. It is essentially unusable for Claude to make informed skill selection decisions.

Suggestions

Describe what raft-manager actually does by listing specific concrete actions (e.g., 'Manages Raft consensus protocol configurations, monitors cluster health, handles leader election')

Add an explicit 'Use when...' clause with natural trigger terms that users would say when they need this skill (e.g., 'Use when the user asks about cluster management, consensus protocols, or distributed system coordination')

Remove the invocation instruction ('invoke with $agent-raft-manager') from the description and replace it with functional information that helps Claude decide when to select this skill

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for raft-manager' 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, providing no functional or contextual information.	1 / 3
Trigger Term Quality	The only keyword is 'raft-manager', which is a technical/internal name rather than a natural term a user would say. No natural language trigger terms are present.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that Claude would have no basis to distinguish this skill from others. 'Agent skill' is entirely generic and provides no domain or niche specificity.	1 / 3
	Total	4 / 12 Passed

Implementation

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 design document describing what a Raft consensus manager should do, rather than an actionable skill teaching Claude how to do it. It lacks any concrete code, commands, configuration examples, or step-by-step workflows. The entire content could be replaced by 'Implement Raft consensus' since Claude already understands the algorithm's components.

Suggestions

Replace abstract descriptions with concrete, executable code examples for key operations (e.g., election timeout configuration, AppendEntries RPC implementation, log entry format)

Add a clear step-by-step workflow for critical operations like leader election with explicit validation checkpoints (e.g., 'Verify quorum achieved before committing')

Remove explanations of Raft fundamentals that Claude already knows and focus on project-specific implementation details, configurations, and constraints

Include specific commands or tool invocations that this agent skill should use, along with expected inputs/outputs and error handling procedures

Dimension	Reasoning	Score
Conciseness	The content is verbose and describes concepts Claude already knows well (Raft consensus, leader election, log replication). It reads like a textbook summary rather than actionable instructions, with phrases like 'Ensure reliable propagation of entries to followers' that add no operational value.	1 / 3
Actionability	There are zero concrete commands, code examples, or executable steps. Every bullet point is an abstract description ('Execute randomized timeout-based elections') rather than a specific instruction with parameters, commands, or code. Nothing is copy-paste ready.	1 / 3
Workflow Clarity	Despite describing multi-step processes like leader election and log replication, there are no sequenced steps, no validation checkpoints, and no error recovery procedures. The content lists responsibilities without defining how to actually perform them.	1 / 3
Progressive Disclosure	The content has reasonable section structure with headers and subsections, but there are no references to external files for detailed implementations. Everything is inline at the same level of abstraction (high-level descriptions) with no deeper resources linked.	2 / 3
	Total	5 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Commit: 398f7c2

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.