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. It only names the skill and its invocation command without describing any capabilities, use cases, or trigger conditions. It fails on every dimension of the rubric.

Suggestions

Describe what raft-manager actually does with 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 Raft configuration')

Remove the invocation syntax from the description and replace it with domain-specific keywords that distinguish this skill from other agent skills

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. There is no 'Use when...' clause and no description of functionality.	1 / 3
Trigger Term Quality	The only keyword is 'raft-manager', which is technical jargon. There are no natural language terms a user would say when needing this skill. The invocation syntax '$agent-raft-manager' is not a trigger term.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it provides no distinguishing characteristics. Without knowing what 'raft-manager' does, Claude cannot differentiate this from any other agent skill.	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 reads as a high-level architectural overview of the Raft consensus algorithm rather than an actionable skill for Claude. It contains no executable code, no concrete commands, no specific tool usage, and no validation steps. The content restates well-known Raft concepts that Claude already understands, making it both verbose and unhelpful as operational guidance.

Suggestions

Replace abstract descriptions with concrete, executable code or commands (e.g., specific CLI invocations for triggering elections, checking cluster state, or replicating logs).

Add a clear step-by-step workflow with validation checkpoints for critical operations like leader election and node recovery, including error handling and retry logic.

Remove explanations of standard Raft concepts Claude already knows and focus only on project-specific implementation details, configurations, and tool-specific commands.

Either create supporting bundle files (e.g., ELECTION.md, REPLICATION.md) with detailed procedures and reference them from the skill, or inline the concrete operational details directly.

Dimension	Reasoning	Score
Conciseness	The content is verbose and describes concepts Claude already understands (Raft consensus, leader election, log replication). It reads like a high-level design document rather than actionable instructions, with padded bullet points that restate well-known Raft properties without adding novel or specific guidance.	1 / 3
Actionability	There are no concrete commands, executable code, specific configurations, or copy-paste-ready examples. Every section describes what to do abstractly ('Execute randomized timeout-based elections', 'Implement append entries protocol') without showing how to actually do it—no code, no CLI commands, no specific tool invocations.	1 / 3
Workflow Clarity	There is no clear sequenced workflow for any operation. The content lists responsibilities and features as bullet points but never defines step-by-step processes, validation checkpoints, or error recovery loops for critical operations like leader election or log replication.	1 / 3
Progressive Disclosure	The content is a monolithic description with no references to supporting files, no links to detailed guides, and no bundle files to support it. There is no layered structure—everything is at the same shallow level of abstraction with nowhere to go for deeper information.	1 / 3
	Total	4 / 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: 619b263

Reviewed: about 9 hours 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.