Name: agent-load-balancer
Rating: 54.400000000000006 (1 reviews)
Author: ruvnet

Blog Docs Log in Get started

agent-load-balancer

Agent skill for load-balancer - invoke with $agent-load-balancer

1.11x

Quality

30%

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

The canonical home for this skill is agent-load-balancer in ruvnet/claude-flow

Quality

Content

32%Weight 40%Scale 1-5

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

The body is a long, monolithic catalog of advanced load-balancing algorithms and claude-flow commands with section headers but no sequenced workflow, no validation checkpoints, and no progressive disclosure into reference files. Code examples look concrete but depend on undefined primitives, limiting true actionability, and the document carries notable padding (a duplicate frontmatter block and a closing fluff line).

Suggestions

Move the advanced algorithm implementations (genetic allocator, CFS/EDF schedulers, circuit breaker) into separate reference files and keep SKILL.md as a concise overview with one-level-deep links.

Add a sequenced operational workflow with explicit validation checkpoints (e.g. collect metrics -> identify imbalance -> migrate tasks -> verify load variance dropped) since task migration is a batch operation.

Make code examples executable by defining or importing the primitives they use (PriorityQueue, RedBlackTree, ConstraintSolver, mcp) or label them explicitly as illustrative pseudocode with a pointer to a working implementation.

Dimension	Reasoning	Score
Conciseness	At ~430 lines the body is noticeably verbose: it carries a duplicate frontmatter block (lines 6-11), an Agent Profile section, explanatory comments restating concepts Claude already knows, and a closing summary line that is pure padding; it does not reach 3 because several sections could be trimmed without losing clarity.	2 / 5
Actionability	Concrete bash commands (npx claude-flow ...) are provided, but the JavaScript examples rely on undefined primitives (PriorityQueue, RedBlackTree, ConstraintSolver, a global mcp object), so they read as illustrative pseudocode rather than copy-paste executable code; this matches 'some concrete guidance but incomplete'.	3 / 5
Workflow Clarity	The body catalogs capabilities and commands rather than sequencing a load-balancing workflow, and task migration / load rebalancing are batch operations with no validation checkpoints, matching 'rough sequence present but many gaps; validation absent'; the destructive/batch cap of 3 is not reached because no real sequence exists at all.	2 / 5
Progressive Disclosure	No bundle files exist and no external references are signaled, yet large bodies of algorithm code and API-like material that belong in separate reference files are inlined into one monolithic document; section headers provide some structure but it stays at 'minimal structure; content that clearly belongs in separate files is inlined'.	2 / 5
	Total	9 / 20 Passed

Description

28%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a generic invocation placeholder that names the load-balancing domain but states no concrete capabilities and provides no 'Use when...' trigger guidance. It is only marginally better than the bad-overall examples and misses the natural trigger terms a user would actually say.

Suggestions

Replace the description with concrete actions, e.g. 'Distributes tasks across agents using work-stealing and adaptive load balancing. Use when coordinating a multi-agent swarm, balancing task load, or reducing agent overload.'

Add an explicit 'Use when...' clause with natural trigger phrases users would say (load balancing, task distribution, work stealing, agent overload).

Drop the 'invoke with $agent-load-balancer' meta-instruction from the description; invocation syntax does not belong in the user-facing trigger field.

Dimension	Reasoning	Score
Specificity	The phrase "Agent skill for load-balancer" names the domain but offers no concrete actions, matching the anchor 'Names the domain but actions are minimal or generic'; it does not reach 3 because no specific capabilities (e.g. work-stealing, task migration) are named.	2 / 5
Completeness	It gives a vague 'what' (an agent skill for load-balancing) and no 'when'/Use-when clause at all, matching 'Has a vague what and no when'; the missing trigger guidance also caps completeness well below 4-5.	2 / 5
Trigger Term Quality	"invoke with $agent-load-balancer" is invocation syntax rather than a natural phrase a user would say, and only the single keyword 'load-balancer' appears; it falls below 3 because common natural variations (load balancing, task distribution, work stealing) are absent.	2 / 5
Distinctiveness Conflict Risk	'load-balancer' plus the unique $agent-load-balancer invocation gives it a recognizable niche, but the description is broad enough to overlap with general optimization or coordination skills, so it sits at 'somewhat specific but could still overlap'.	3 / 5
	Total	9 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/agent-load-balancer/SKILL.md
Commit: fa13ee4

Reviewed: about 8 hours 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.