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, sets up health checks, and monitors backend server pools.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to configure load balancing, distribute traffic, set up reverse proxies, or manage server pools.'

Remove the invocation syntax ('invoke with $agent-load-balancer') from the description and replace it with domain-specific keywords that help Claude distinguish this skill from other infrastructure or networking 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	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 trigger guidance.	1 / 3
Trigger Term Quality	The only keyword is 'load-balancer', which is somewhat relevant but the description lacks any natural user terms like 'traffic distribution', 'routing', 'scaling', 'health checks', or other terms a user might say. The invocation syntax '$agent-load-balancer' is not a natural trigger term.	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

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

This skill is a conceptual reference document about load balancing algorithms rather than an actionable skill for Claude. It contains extensive non-executable pseudocode implementing well-known CS concepts (work-stealing, EDF, CFS, circuit breakers) that Claude already understands, references fictional APIs and tools, and provides no clear workflow for when or how to apply any of these techniques. The content would need a complete rewrite to be useful as a skill.

Suggestions

Replace conceptual algorithm implementations with concrete, executable instructions for actual load balancing tasks Claude would perform, using real tools and APIs available in the environment.

Add a clear workflow with numbered steps, decision points (e.g., 'when to rebalance'), and validation checkpoints instead of presenting disconnected code blocks.

Remove explanations of well-known algorithms (EDF, CFS, circuit breaker) that Claude already knows, and focus only on project-specific configuration and usage patterns.

Add a concise quick-start section (under 20 lines) that shows the most common load balancing operation end-to-end with real, working commands.

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. Much of this reads like a textbook rather than actionable skill instructions.	1 / 3
Actionability	The code examples are pseudocode-like JavaScript that references non-existent classes (PriorityQueue, RedBlackTree, ConstraintSolver, WeightedRoundRobinQueue) and fictional MCP methods (mcp.performance_report, mcp.bottleneck_analyze, etc.). The bash commands reference 'npx claude-flow' subcommands that may not exist. Nothing is copy-paste executable; it describes conceptual algorithms rather than providing concrete, working instructions.	1 / 3
Workflow Clarity	There is no clear workflow or sequence of steps. The skill presents a collection of algorithm implementations and code snippets without explaining when or how to use them, in what order, or how they connect. No validation checkpoints, no error recovery steps, no decision points for choosing between approaches.	1 / 3
Progressive Disclosure	Monolithic wall of code with no external references, no bundle files, and no clear navigation structure. All content is dumped inline with no separation of overview from detail. The sections are organized by algorithm type but there's no quick-start or summary that points to deeper content.	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
Commit: 0aac1e1

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.