testing-load-balancers
This skill enables Claude to test load balancing strategies. It validates traffic distribution across backend servers, tests failover scenarios when servers become unavailable, verifies sticky sessions, and assesses health check functionality. Use this skill when the user asks to "test load balancer", "validate traffic distribution", "test failover", "verify sticky sessions", or "test health checks". It is specifically designed for testing load balancing configurations using the `load-balancer-tester` plugin.
68
53%
Does it follow best practices?
Impact
75%
1.25xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-batch-20251204-000554/plugins/testing/load-balancer-tester/skills/load-balancer-tester/SKILL.mdQuality
Discovery
100%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 a well-crafted skill description that clearly articulates specific capabilities (traffic distribution validation, failover testing, sticky session verification, health check assessment), provides explicit trigger terms in a 'Use this skill when...' clause, and identifies the specific tool (`load-balancer-tester` plugin). It occupies a distinct niche with minimal conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: validates traffic distribution across backend servers, tests failover scenarios, verifies sticky sessions, and assesses health check functionality. These are clear, actionable capabilities. | 3 / 3 |
Completeness | The description clearly answers both 'what does this do' (tests load balancing strategies including traffic distribution, failover, sticky sessions, health checks) AND 'when should Claude use it' with an explicit 'Use this skill when...' clause listing specific trigger phrases. | 3 / 3 |
Trigger Term Quality | The description includes natural trigger terms users would say: 'test load balancer', 'validate traffic distribution', 'test failover', 'verify sticky sessions', 'test health checks'. These cover the main variations a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche—load balancing testing using the `load-balancer-tester` plugin. The trigger terms are highly specific to load balancing and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is largely descriptive rather than instructive. It explains what the skill does in abstract terms but never provides concrete commands, configuration examples, expected outputs, or error handling guidance. The content reads more like a marketing overview than an actionable skill file, with significant verbosity and no executable examples.
Suggestions
Replace the abstract examples with concrete, executable command invocations showing exact `lb-test` CLI syntax, flags, and expected output formats (e.g., `lb-test --mode distribution --servers server1:8080,server2:8080`)
Add a validation/verification workflow with explicit checkpoints, such as how to confirm test results are valid, what error outputs look like, and how to retry or debug failures
Remove the 'How It Works', 'When to Use This Skill', and 'Best Practices' sections entirely — they add no actionable information and waste tokens on things Claude already knows or that duplicate the frontmatter description
Add concrete configuration examples showing what a load balancer test configuration file looks like and what specific output/metrics to expect from each test type
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and padded with unnecessary context. Sections like 'How It Works', 'When to Use This Skill', and 'Overview' repeat information Claude doesn't need. The description of what the skill 'empowers' Claude to do and the 'When to Use' section largely restate the frontmatter description. Best practices like 'ensure the load balancer is properly configured before testing' are obvious filler. | 1 / 3 |
Actionability | There are no concrete commands, executable code, CLI invocations, or specific configuration examples. The examples describe what the skill 'will do' in abstract terms (e.g., 'Execute the lb-test command') without showing actual command syntax, flags, expected output formats, or how to interpret results. References to 'lb-test' and 'load-balancer-tester' plugin are never given concrete usage patterns. | 1 / 3 |
Workflow Clarity | The steps listed are vague descriptions rather than actionable sequences. There are no validation checkpoints, no error handling or feedback loops, no specific commands to run, and no guidance on what to do when tests fail. For operations involving failover and health checks, the absence of verification steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, which provides some structure. However, there are no bundle files or external references, and the content that exists is mostly filler that could be condensed significantly. The section organization is reasonable but the content within each section doesn't justify the separation. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
b8c7056
- 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.