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.
72
67%
Does it follow best practices?
Impact
Pending
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 its domain (load balancer configuration), lists specific technologies and capabilities, and provides explicit trigger phrases. The description is concise yet comprehensive, covering both the 'what' and 'when' effectively. Minor note: the description starts with 'Configure use when' which reads slightly awkwardly 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 specific technologies like NLB. These are phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around load balancer configuration with specific technology names (ALB, NLB, Nginx, HAProxy) that are 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 reads more like a high-level checklist or study guide than an actionable skill for Claude. Its biggest weakness is the complete absence of executable code examples—no Nginx configs, no HAProxy configs, no Terraform blocks—despite the output section promising all of these. The error handling table is a useful addition, but the skill fundamentally fails to provide the concrete, copy-paste-ready configurations that would make it effective.
Suggestions
Add concrete, executable configuration examples for at least 2-3 of the covered technologies (e.g., a complete Nginx upstream block, a HAProxy frontend/backend config, a Terraform ALB resource block).
Replace the natural language 'Examples' section with actual input/output pairs showing a request and the resulting configuration file content.
Split per-technology details into separate reference files (e.g., nginx.md, haproxy.md, alb-terraform.md) and reference them from the main skill to improve progressive disclosure.
Add explicit validation checkpoints with feedback loops: e.g., after generating Nginx config, run `nginx -t`, if it fails, fix the identified line, re-validate before proceeding.
| 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 commands (`nginx -t`, HAProxy config check), but there are no explicit feedback loops for error recovery. For a skill involving production infrastructure configuration, the lack of validate-fix-retry loops and the absence of concrete validation checkpoints between steps is a notable gap. | 2 / 3 |
Progressive Disclosure | The content references `${CLAUDE_SKILL_DIR}/references/errors.md` but no bundle files exist to support it, making it a broken reference. The skill covers four different load balancer types inline which could benefit from being split into separate reference files per technology. The structure has clear sections but everything is monolithic. | 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
3a2d27d
- 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.