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
Traffic distribution testing
lb-test command used
0%
0%
Traffic distribution focus
100%
100%
Multiple backends covered
100%
100%
Realistic traffic patterns
75%
66%
Configuration pre-check
100%
100%
Even distribution assertion
100%
100%
Results summary produced
100%
100%
Issues/improvements highlighted
91%
100%
Without context: $0.5398 · 2m 24s · 19 turns · 20 in / 8,843 out tokens
With context: $0.5491 · 2m 11s · 26 turns · 996 in / 7,449 out tokens
Failover and health check testing
lb-test command used
0%
100%
Server failure simulation
61%
100%
Traffic redirection verified
86%
100%
Health check validation
60%
100%
Realistic failure scenarios
58%
83%
Failover success reported
92%
100%
Results summary with issues
91%
100%
Without context: $0.6115 · 2m 49s · 14 turns · 15 in / 11,351 out tokens
With context: $0.5489 · 2m 18s · 24 turns · 439 in / 8,542 out tokens
Comprehensive load balancer validation
lb-test command used
0%
0%
Traffic distribution tested
100%
100%
Failover tested
30%
70%
Sticky sessions tested
93%
93%
Health checks tested
40%
80%
Configuration pre-check
80%
60%
All four aspects present
100%
100%
Results summary with issues
33%
66%
Without context: $0.6480 · 3m 38s · 12 turns · 13 in / 14,821 out tokens
With context: $0.7277 · 3m 31s · 26 turns · 331 in / 13,517 out tokens
Sticky session verification
lb-test command used
0%
0%
Session persistence verified
93%
93%
Multiple requests per client
100%
100%
Backend identity tracked
88%
88%
Multiple backends present
100%
100%
Configuration pre-check
50%
0%
Session failure case covered
25%
12%
Realistic client simulation
75%
75%
Results summary produced
87%
100%
Issues and improvements noted
100%
100%
Without context: $0.5215 · 2m 21s · 17 turns · 18 in / 8,448 out tokens
With context: $0.7579 · 2m 57s · 35 turns · 1,044 in / 9,714 out tokens
Health check and degraded server testing
lb-test command used
0%
0%
Unhealthy server removal verified
33%
80%
Realistic failure mode used
25%
66%
Recovery scenario included
60%
90%
No traffic to failed server
37%
75%
Failure detection timing
50%
87%
Configuration pre-check
75%
50%
Multiple backend coverage
87%
100%
Results summary produced
87%
87%
Issues and improvements noted
100%
100%
Without context: $0.4687 · 3m 2s · 17 turns · 15 in / 8,935 out tokens
With context: $0.8019 · 4m 7s · 31 turns · 331 in / 12,247 out tokens
Realistic traffic pattern testing
lb-test command used
0%
0%
Realistic traffic volume
100%
86%
Traffic pattern variety
100%
80%
Concurrency or rate specified
100%
90%
Distribution assertion present
100%
90%
Backend imbalance detection
100%
90%
Configuration pre-check
0%
12%
Multiple backends covered
100%
100%
Results summary produced
100%
100%
Issues and improvements noted
100%
100%
Without context: $0.4414 · 4m 4s · 11 turns · 12 in / 8,580 out tokens
With context: $0.5976 · 2m 51s · 22 turns · 72 in / 9,844 out tokens
Table of Contents
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.