testing-load-balancers
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill testing-load-balancersThis 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.
Validation
69%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 11 / 16 Passed | |
Implementation
7%This skill content is largely descriptive rather than instructive. It explains what the skill does conceptually but fails to provide any executable commands, actual syntax for the load-balancer-tester plugin, or concrete examples with expected outputs. The content reads like marketing copy rather than technical guidance Claude can act on.
Suggestions
Add actual executable command syntax for the `lb-test` command with all relevant parameters (e.g., `lb-test --distribution --servers server1,server2,server3`)
Replace descriptive examples with concrete input/output pairs showing exact commands and expected results
Remove the 'How It Works' and 'When to Use' sections - this information is already in the skill description and wastes tokens
Add validation steps showing how to interpret test results and what to do when tests fail
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Verbose and padded with unnecessary context. Explains obvious concepts like 'how it works' and 'when to use' that Claude doesn't need. The overview restates the description, and sections like 'Best Practices' contain generic advice Claude already knows. | 1 / 3 |
Actionability | No concrete commands, code, or executable guidance provided. 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 vague and lack specificity. No actual command syntax, no validation checkpoints, no error handling guidance. 'Execute the lb-test command' without showing how is not actionable workflow guidance. | 1 / 3 |
Progressive Disclosure | Content is organized into sections with headers, but everything is inline in one file. No references to external documentation for advanced topics. The structure exists but content that could be separate (detailed examples, API reference) is missing entirely. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%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 states both what the skill does and when to use it, and carves out a distinct niche that minimizes conflict with other skills.
| 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 users would naturally 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'. Also specifies the exact plugin used, reducing ambiguity. | 3 / 3 |
Total | 12 / 12 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.