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 minimal description that fails on all dimensions. It provides no information about what the skill does, when it should be used, or what specific capabilities it offers. It reads more like a label than a functional description that Claude could use to select the right skill.

Suggestions

Add concrete actions the skill performs, e.g., 'Configures load balancer rules, monitors traffic distribution, manages backend server pools, 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, server pools, health checks, or reverse proxy configuration.'

Remove the invocation syntax ('invoke with $agent-load-balancer') from the description and replace it with capability and context information that helps Claude distinguish this skill from other infrastructure-related skills.

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	Neither 'what does this do' nor 'when should Claude use it' is answered. There is no 'Use when...' clause and no description of capabilities.	1 / 3
Trigger Term Quality	The only keyword is 'load-balancer', which is somewhat relevant but the description provides no natural language terms a user would say. The invocation syntax '$agent-load-balancer' is technical jargon, not a user trigger term.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could overlap with any networking, infrastructure, or DevOps skill. 'Load-balancer' alone is insufficient to carve out a clear niche without specifying what actions are performed.	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 reads more like a reference library or textbook chapter on load balancing algorithms than an actionable agent skill. It dumps extensive code for well-known patterns (work-stealing, CFS, EDF, circuit breaker) that Claude already understands, without providing a clear operational workflow for when and how to apply them. The lack of validation steps, progressive disclosure, and concrete integration guidance makes it poorly suited as a skill file.

Suggestions

Replace the extensive algorithm implementations with a concise decision table: given X condition, use Y strategy, with brief code snippets only for project-specific patterns Claude wouldn't already know.

Add a clear step-by-step workflow: 1) Assess current load → 2) Select strategy → 3) Execute rebalancing → 4) Validate results → 5) Adjust if needed, with explicit validation checkpoints.

Split content into SKILL.md (overview + quick start + commands) and separate reference files (ALGORITHMS.md, BENCHMARKING.md) with clear navigation links.

Remove explanations of standard CS algorithms (CFS, EDF, circuit breaker) and focus on project-specific configuration, thresholds, and integration details that are unique to this system.

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 hypothetical 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 for what should be a complex multi-step coordination process.	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/claude-flow
Commit: f547cec

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.