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 fails on every dimension. It provides no information about what the skill does, when it should be used, or what domain it operates in. It reads more like a label than a description, making it essentially useless for skill selection among multiple options.

Suggestions

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

Add an explicit 'Use when...' clause with natural trigger terms that describe scenarios where this skill should be selected

Replace the invocation instruction ('invoke with $agent-raft-manager') with functional description content — invocation syntax belongs elsewhere, not in the description used for skill selection

Dimension	Reasoning	Score
Specificity	The description provides 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 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 users would naturally use.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's impossible to distinguish it from other skills. 'Agent skill' is completely generic and 'raft-manager' provides no clarity on the domain or purpose.	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 entirely lacks concrete commands, code examples, specific tool usage, or step-by-step workflows. The content describes what Raft does (which Claude already knows) rather than providing project-specific instructions on how to perform tasks.

Suggestions

Replace abstract descriptions with concrete, executable code or commands for each core operation (e.g., specific CLI commands to trigger leader election, code to append log entries, scripts to verify consistency).

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

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

Add concrete examples showing expected inputs and outputs for each operation (e.g., what a log entry looks like, what election success/failure responses contain).

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 concepts without adding novel or project-specific information.	1 / 3
Actionability	There are no concrete commands, executable code, specific configurations, or copy-paste-ready examples. Every section is abstract description ('Implement append entries protocol', 'Execute randomized timeout-based elections') without any actual implementation guidance, tool invocations, or specific steps Claude should take.	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 a step-by-step process for leader election, log replication, or any other task. No validation checkpoints or feedback loops are present despite these being critical distributed systems operations.	1 / 3
Progressive Disclosure	The content has some structural organization with headers and subsections, and the collaboration section references other components. However, there are no links to supporting files, no bundle files exist, and the content is a monolithic description without clear navigation to deeper resources.	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/claude-flow
Commit: e6dc21f

Reviewed: 4 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.