agent-load-balancer
Agent skill for load-balancer - invoke with $agent-load-balancer
35
0%
Does it follow best practices?
Impact
96%
1.11xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-load-balancer/SKILL.mdQuality
Discovery
0%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 specific capabilities it offers. It reads more like a label than a functional description that Claude could use for skill selection.
Suggestions
Add 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.'
Specify the type of load balancer (e.g., AWS ALB/NLB, Nginx, HAProxy) to improve distinctiveness and reduce conflict risk with other infrastructure skills.
| 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. 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 lacks any natural user terms. The invocation syntax '$agent-load-balancer' is technical jargon, not something a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from any other networking, infrastructure, or DevOps-related skill. 'Load-balancer' alone is insufficient for clear differentiation. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%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 masquerading as an actionable agent skill. It contains extensive non-executable pseudocode for well-known algorithms (work-stealing, EDF, CFS, circuit breaker) that Claude already understands, without providing any concrete, usable implementation tied to a real system. The content lacks any clear workflow, validation steps, or practical guidance for when and how to apply these patterns.
Suggestions
Replace conceptual algorithm implementations with concrete, executable code tied to the actual claude-flow system, or remove code entirely and provide specific CLI commands with expected inputs/outputs.
Add a clear step-by-step workflow: e.g., 1) Assess current load → 2) Choose balancing strategy → 3) Execute rebalancing → 4) Validate results, with explicit validation checkpoints.
Remove explanations of well-known patterns (circuit breaker, EDF, CFS, genetic algorithms) and focus only on project-specific configuration and usage.
Split into a concise SKILL.md overview (~30-50 lines) with references to separate files for algorithm details, MCP integration, and benchmarking if that depth is needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines. Contains massive code blocks that are conceptual/illustrative rather than practically useful. Explains well-known patterns (circuit breaker, EDF, CFS, genetic algorithms) that Claude already knows. The 'Agent Profile' section and closing summary sentence add zero value. | 1 / 3 |
Actionability | The code is not executable — it references undefined classes (PriorityQueue, RedBlackTree, ConstraintSolver, WeightedRoundRobinQueue, FairShareQueue), undefined MCP methods, and incomplete implementations. The bash commands reference 'claude-flow' subcommands without explaining if they actually exist or how to set them up. This is conceptual pseudocode dressed up as real code. | 1 / 3 |
Workflow Clarity | There is no clear workflow or sequence of steps for actually performing load balancing. The content is a collection of disconnected code snippets and algorithm implementations with no guidance on when to use which approach, no validation checkpoints, and no error recovery steps. The operational commands section lists commands but doesn't sequence them into a workflow. | 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 — advanced scheduling algorithms, benchmarking, MCP integration, and basic queue management are all at the same level with no navigation structure or separation of concerns. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
100%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
9d4a9ea
- Reviewed
Table of Contents
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.