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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill testing-load-balancers70
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 — 75%
↑ 1.20xAgent success when using this skill
Validation for skill structure
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 excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly addresses both what the skill does and when to use it, and has a clear distinctive niche in load balancing testing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'validates traffic distribution across backend servers', 'tests failover scenarios', 'verifies sticky sessions', and 'assesses health check functionality'. | 3 / 3 |
Completeness | Clearly answers both what (testing load balancing strategies with specific capabilities) AND when (explicit 'Use this skill when...' clause with multiple trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'test load balancer', 'validate traffic distribution', 'test failover', 'verify sticky sessions', 'test health checks'. These are realistic phrases a user would use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on load balancing testing with distinct triggers like 'load balancer', 'traffic distribution', 'failover', 'sticky sessions'. Mentions specific plugin 'load-balancer-tester' which further distinguishes it. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
20%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 overly verbose and lacks actionable guidance. It describes what the skill does conceptually but fails to provide executable commands, concrete syntax for the load-balancer-tester plugin, or specific examples with expected outputs. The content reads more like marketing copy than technical instruction.
Suggestions
Replace abstract descriptions with actual executable commands showing exact syntax for `lb-test` (e.g., `lb-test --distribution --servers server1,server2,server3`)
Add concrete input/output examples showing what the test results look like and how to interpret them
Remove the 'Overview', 'How It Works', and 'When to Use' sections entirely - Claude doesn't need this meta-explanation
Add validation steps and error handling guidance (e.g., what to do when a test fails, how to diagnose common issues)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Verbose and padded with unnecessary context. Explains obvious concepts like 'how it works' and 'when to use' that Claude already understands. The 'Overview' section adds no actionable value, and the entire document could be reduced to a fraction of its size. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples. References 'lb-test' command but never shows actual syntax, parameters, or expected output. Examples describe what 'the skill will do' rather than providing copy-paste ready commands. | 1 / 3 |
Workflow Clarity | Steps are listed in examples but lack specificity. No validation checkpoints, no error handling guidance, and no feedback loops for when tests fail. The numbered steps describe abstract actions rather than concrete commands with verification. | 2 / 3 |
Progressive Disclosure | Content is organized into sections but everything is inline in one file. No references to external documentation for advanced usage, API reference, or detailed examples. The structure exists but doesn't leverage progressive disclosure effectively. | 2 / 3 |
Total | 6 / 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 | |
- 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.