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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, well-structured instruction skill with concrete parameters and a clear step sequence, but it under-leverages its own bundle: the config templates and helper script are never referenced from the body, and the workflow lacks an explicit validation feedback loop.

Suggestions

Link the bundled artifacts inline — e.g., in the Output or Instructions section, point to assets/nginx_template.conf, assets/haproxy_template.conf, and scripts/generate_config.py so Claude uses them directly.

Turn step 9 into an explicit validate->fix->retry loop ('if nginx -t or HAProxy check fails, fix the reported line and re-run before deploying') integrated into the workflow rather than relying on the separate error table.

Reference references/examples.md from the Examples section to keep the body lean while still disclosing the worked examples.

Dimension	Reasoning	Score
Conciseness	Lean and well-organized with no padding of concepts Claude already knows (it does not explain L4/L7 or what a load balancer is); every section earns its place. Not a 2 because it avoids unnecessary explanation throughout.	3 / 3
Actionability	Gives concrete parameters (intervals 10-30s, thresholds 3/2, TLS 1.2) and commands ('nginx -t', 'openssl s_client'), but the actual config templates in assets/ (nginx_template.conf, haproxy_template.conf) and the generate_config.py script are never linked from the body, leaving key executable artifacts unreferenced.	2 / 3
Workflow Clarity	The 9-step sequence is clearly ordered and step 9 provides a validation checkpoint, but there is no explicit validate->fix->retry feedback loop in the workflow itself; error recovery lives in a separate table rather than an integrated loop. Not a 3 because the recovery loop is implicit, not a 1 because sequencing and a test step are present.	2 / 3
Progressive Disclosure	Section structure is clean and errors.md is correctly referenced one level deep, but the bundle's other files (examples.md, the two assets templates, scripts/generate_config.py) are not signaled or linked from the body, so navigation to bundled detail is incomplete.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit capability and trigger coverage that clearly occupies a distinct niche. The opening clause 'Configure use when configuring load balancers' is a grammatical redundancy but does not undermine the dimension scores.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'ALB, NLB, Nginx, and HAProxy' plus 'health checks, SSL termination, sticky sessions, and traffic distribution rules' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Answers both what ('Generates production-ready configurations with...') and when ('use when configuring load balancers' plus an explicit 'Trigger with phrases like...' clause), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Explicit natural trigger phrases ('configure load balancer', 'create ALB', 'setup nginx load balancing', 'haproxy configuration') are terms a user would actually say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (load balancer configuration across named technologies) with distinct triggers, making conflict with unrelated skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/load-balancer-configurator/skills/configuring-load-balancers/SKILL.md
Commit: c4eafaf

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.