configuring-load-balancers
Configure use when configuring load balancers including ALB, NLB, Nginx, and HAProxy. Trigger with phrases like "configure load balancer", "create ALB", "setup nginx load balancing", or "haproxy configuration". Generates production-ready configurations with health checks, SSL termination, sticky sessions, and traffic distribution rules.
57
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/load-balancer-configurator/skills/configuring-load-balancers/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 strong skill description that clearly identifies the domain (load balancer configuration), lists specific technologies and capabilities, and provides explicit trigger phrases. It uses third person voice appropriately and covers both the 'what' and 'when' dimensions effectively. Minor note: the description starts with 'Configure use when' which appears to be a slight grammatical issue but doesn't significantly impact clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: configuring ALB, NLB, Nginx, HAProxy, and generating configurations with health checks, SSL termination, sticky sessions, and traffic distribution rules. | 3 / 3 |
Completeness | Clearly answers both what (generates production-ready configurations with health checks, SSL termination, sticky sessions, traffic distribution) and when (explicit trigger phrases like 'configure load balancer', 'create ALB', etc.). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'configure load balancer', 'create ALB', 'setup nginx load balancing', 'haproxy configuration', plus mentions of NLB and specific feature terms like SSL termination and sticky sessions. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to load balancer configuration with specific technologies (ALB, NLB, Nginx, HAProxy) that create a distinct niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill covers an extremely broad topic (ALB, NLB, GCP LB, Nginx, HAProxy) but provides no concrete, executable configuration examples for any of them. The instructions read as a high-level checklist rather than actionable guidance, and the 'Examples' section contains natural language prompts instead of actual configuration snippets. The error handling table is a useful addition, but the skill fundamentally fails to deliver the 'production-ready configurations' it promises.
Suggestions
Add concrete, copy-paste-ready configuration snippets for at least Nginx upstream blocks, HAProxy frontend/backend sections, and Terraform ALB resources — these are the core deliverables the skill promises.
Replace the natural language 'Examples' section with actual input/output pairs showing a request and the resulting configuration file content.
Split the skill into separate reference files per load balancer type (e.g., `references/nginx.md`, `references/haproxy.md`, `references/aws-alb.md`) and keep SKILL.md as a concise overview with routing logic for which file to consult.
Create the referenced `${CLAUDE_SKILL_DIR}/references/errors.md` file or remove the dangling reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some unnecessary verbosity. The prerequisites section explains things Claude would know (what ACM and Let's Encrypt are), and the overview restates the description. The examples section lists natural language prompts rather than providing executable configurations, which wastes tokens. | 2 / 3 |
Actionability | Despite covering a complex topic, the skill provides zero executable code, no concrete configuration snippets, no Terraform HCL examples, no Nginx config blocks, and no HAProxy config blocks. The instructions are entirely abstract descriptions of what to do rather than showing how to do it. The 'Output' section lists what should be produced but gives no templates or examples. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence and step 9 mentions validation (`nginx -t`, HAProxy config check), but there are no explicit feedback loops for error recovery during the configuration process. For a skill involving production infrastructure changes, the validation is mentioned only at the end rather than integrated throughout the workflow. | 2 / 3 |
Progressive Disclosure | The content references `${CLAUDE_SKILL_DIR}/references/errors.md` but no bundle files exist to support it. The skill covers four different load balancer types inline which could benefit from separate reference files for each. The structure has clear sections but the monolithic approach for such a broad topic is suboptimal. | 2 / 3 |
Total | 7 / 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
4801da6
- 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.