agent-load-balancer
Agent skill for load-balancer - invoke with $agent-load-balancer
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-load-balancer40
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 96%
↑ 1.11xAgent success when using this skill
Validation for skill structure
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 to use it, or what user requests should trigger it. The description reads more like a technical label than a functional description that would help Claude select the appropriate skill.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Configures load balancer rules, monitors traffic distribution, manages backend server pools')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user mentions traffic distribution, server balancing, request routing, or high availability')
Remove the invocation syntax '$agent-load-balancer' from the description - this is implementation detail, not selection criteria
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for load-balancer' is completely abstract with no indication of 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, not its purpose or triggers. | 1 / 3 |
Trigger Term Quality | The only keyword is 'load-balancer' which is technical jargon. No natural user terms are provided - users wouldn't naturally say 'invoke with $agent-load-balancer'. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic - 'Agent skill for load-balancer' could mean anything related to load balancing. No specific niche or distinct triggers are defined. | 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 computer science textbook chapter on load balancing algorithms than an actionable agent skill. It contains extensive theoretical implementations (work-stealing, CFS, EDF schedulers) that Claude already understands, while lacking practical guidance on how to actually invoke and use the load-balancer agent. The CLI commands at the end are helpful but disconnected from the preceding code.
Suggestions
Replace algorithm implementations with a concise quick-start section showing how to invoke the load-balancer agent and configure basic options
Add a clear workflow: 1) spawn agent, 2) configure strategy, 3) monitor metrics, 4) validate load distribution
Move advanced algorithm details to a separate ALGORITHMS.md reference file, keeping only essential configuration in the main skill
Add concrete examples showing expected inputs/outputs when using the CLI commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive code examples that explain concepts Claude already knows (work-stealing algorithms, circuit breakers, CFS schedulers). The 400+ lines could be reduced to essential configuration and invocation patterns. | 1 / 3 |
Actionability | Contains executable code examples and CLI commands, but they appear to be conceptual implementations rather than actual working code for the claude-flow system. The relationship between the JavaScript classes and the CLI commands is unclear. | 2 / 3 |
Workflow Clarity | No clear workflow for how to actually use this agent. The document presents algorithms and code snippets but lacks a step-by-step process for invoking the load balancer, configuring it, or validating its operation. | 1 / 3 |
Progressive Disclosure | Monolithic wall of code with no references to external files. All content is inline regardless of complexity, with no clear hierarchy between quick-start usage and advanced algorithm details. | 1 / 3 |
Total | 5 / 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.
- 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.