agent-load-balancer

Agent skill for load-balancer - invoke with $agent-load-balancer

1.11x

Quality

Does it follow best practices?

Impact

96%

1.11x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agents/skills/agent-load-balancer/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 reads more like a label than a functional description.

Suggestions

Add concrete actions the skill performs, e.g., 'Configures load balancer rules, manages traffic distribution, monitors backend health, and updates routing policies.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about load balancing, traffic routing, backend servers, health checks, or network distribution.'

Remove the invocation instruction ('invoke with $agent-load-balancer') from the description field, as this is operational metadata rather than descriptive content that helps with skill selection.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. 'Agent skill for load-balancer' is entirely vague and does not describe what the skill actually does.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent.	1 / 3
Trigger Term Quality	The only keyword is 'load-balancer', which is somewhat relevant but the description provides no natural user-facing trigger terms. '$agent-load-balancer' is an invocation command, not a trigger term users would naturally say.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's unclear what domain it covers. 'Load-balancer' hints at a niche but without any specifics about what actions it performs, it could conflict with networking, infrastructure, or deployment skills.	1 / 3
	Total	4 / 12 Passed

Implementation

14%

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

This skill is an extensive reference document of load balancing concepts and algorithms rather than an actionable skill for Claude. It explains well-known CS concepts (work-stealing, CFS, EDF, circuit breaker) that Claude already knows, uses fictional/undefined dependencies making code non-executable, and lacks any clear workflow or step-by-step process for actually performing load balancing tasks.

Suggestions

Replace the extensive algorithm implementations with a concise workflow: when to apply load balancing, specific steps to execute, and how to validate results.

Remove explanations of well-known algorithms (CFS, EDF, circuit breaker) that Claude already understands—instead, just reference them by name and specify when to use each.

Add explicit validation checkpoints and error recovery steps (e.g., what to do when task migration fails, how to verify load is actually balanced after rebalancing).

Split content into a concise SKILL.md overview with references to separate files for algorithm details, MCP integration, and benchmarking.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Contains extensive code examples for well-known algorithms (work-stealing, CFS, EDF, circuit breaker) that Claude already knows. The 'Agent Profile' section, integration points descriptions, and concluding summary sentence are all unnecessary padding.	1 / 3
Actionability	The operational commands section provides concrete CLI commands, and code examples are syntactically complete. However, the code relies on undefined classes (PriorityQueue, RedBlackTree, ConstraintSolver, WeightedRoundRobinQueue) and fictional MCP methods, making it not truly executable or copy-paste ready.	2 / 3
Workflow Clarity	There is no clear multi-step workflow or sequenced process for actually performing load balancing. The content presents isolated code snippets and concepts without a coherent operational sequence, validation checkpoints, or error recovery steps.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content—algorithms, MCP integration, benchmarking, commands—is inlined in a single massive document with no navigation structure or content splitting.	1 / 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.