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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-load-balancer/SKILL.md

Quality

Content

14%Scale 1-3

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

This skill reads more like a reference catalog of load-balancing algorithms and patterns than an actionable agent skill. It is extremely verbose, dumping hundreds of lines of illustrative JavaScript that reference undefined dependencies and fictional APIs, without providing a clear workflow for when or how to apply any of it. The content would benefit enormously from being restructured into a concise overview with clear decision criteria and concrete, executable steps.

Suggestions

Replace the algorithm showcase with a concise decision table: given symptom X, apply strategy Y with specific command Z.

Add a clear step-by-step workflow: how to detect load imbalance, choose a strategy, apply it, and validate the result, with explicit checkpoints.

Remove or drastically shorten code examples for well-known patterns (circuit breaker, EDF, CFS) that Claude already understands, keeping only project-specific configuration or invocation details.

Extract detailed algorithm implementations into separate reference files and keep SKILL.md as a concise overview with links to those files.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~350+ lines. Contains extensive code examples that are conceptual/illustrative rather than practically useful. Explains well-known patterns (circuit breaker, EDF, CFS) that Claude already knows. The 'Agent Profile' section and closing summary sentence add no value.	1 / 3
Actionability	The operational commands section provides concrete CLI commands, and code examples are syntactically complete JavaScript. However, the code references undefined classes (PriorityQueue, RedBlackTree, ConstraintSolver, WeightedRoundRobinQueue) and fictional MCP methods, making it non-executable pseudocode dressed as real code. It's unclear what framework or system this actually targets.	2 / 3
Workflow Clarity	There is no clear workflow or sequenced process for actually performing load balancing. The content is a collection of algorithm implementations and concepts without guidance on when to use which approach, how to diagnose load imbalance, or what steps to follow. No validation checkpoints or error recovery flows are defined.	1 / 3
Progressive Disclosure	Monolithic wall of code with no references to external files and no bundle files to support it. All content is inline with no clear hierarchy between essential and advanced material. The 'Integration Points' section lists connections but provides no navigable references.	1 / 3
	Total	5 / 12 Passed

Description

0%Scale 1-3

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 description is critically deficient across all dimensions. It provides no information about what the skill does, when it should be used, or what user requests should trigger it. It reads as a placeholder rather than a functional skill description.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Configures load balancer rules, manages backend pools, monitors traffic distribution, and troubleshoots routing issues.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about load balancing, traffic distribution, backend health checks, reverse proxy configuration, or scaling web services.'

Remove the invocation instruction ('invoke with $agent-load-balancer') from the description and replace it with capability and context information that helps Claude select this skill appropriately.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for load-balancer' 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, with no functional or trigger information.	1 / 3
Trigger Term Quality	The only keyword is 'load-balancer', which is a generic technical term. There are no natural user-facing trigger terms describing tasks, scenarios, or variations a user might say.	1 / 3
Distinctiveness Conflict Risk	'Agent skill for load-balancer' is extremely generic and could overlap with any networking, infrastructure, or DevOps skill. There are no distinct triggers to differentiate it.	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/claude-flow
Path: .agents/skills/agent-load-balancer/SKILL.md
Commit: 913f9ea

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.