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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is well-organized and concise with a clear step sequence and a useful error-handling table, but it underuses its own bundle — templates, the generator script, and the examples reference are never linked, and validation lacks an explicit retry loop. Wiring these in would lift actionability and progressive disclosure.

Suggestions

Reference the bundle's executable assets from the body — e.g., point step 1/Output to assets/nginx_template.conf and assets/haproxy_template.conf, and mention scripts/generate_config.py as the generator — so Claude actually uses them.

Add an explicit validation feedback loop: after generating config, 'run nginx -t / haproxy -c; if it fails, consult the Error Handling table, fix, and re-test before deploying'.

Replace the inline Examples section with a link to references/examples.md (or merge them) to avoid duplication and make the references one level deep and consistently signaled.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding explaining what load balancers, SSL, or health checks are, and each section (Prerequisites, Instructions, Output, Error Handling) earns its place.	3 / 3
Actionability	Instructions give specific values (interval 10-30s, timeout 5s, TLS 1.2) and commands (nginx -t), but the most executable assets — assets/nginx_template.conf, assets/haproxy_template.conf, and scripts/generate_config.py — are never referenced from the body, leaving the guidance incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	The 9-step sequence is clear and step 9 includes validation (nginx -t, verify traffic, confirm failover), but validation is end-only with no explicit validate→fix→retry feedback loop, and checkpoints are not interleaved through the process.	2 / 3
Progressive Disclosure	Only one bundle file is signaled ('${CLAUDE_SKILL_DIR}/references/errors.md'); the templates in assets/, generate_config.py in scripts/, and references/examples.md all exist but are orphaned, and the inline Examples section duplicates content that already lives in examples.md.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is specific, complete, and distinctive with explicit trigger guidance and concrete capability claims. The only blemish is the grammatically awkward opening 'Configure use when configuring load balancers', which reads like a malformed verb-first clause but does not undermine the trigger or capability information.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'health checks, SSL termination, sticky sessions, and traffic distribution rules' across 'ALB, NLB, Nginx, and HAProxy' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Answers both 'what' ('Generates production-ready configurations...') and 'when' with explicit trigger guidance ('Trigger with phrases like...'), satisfying the anchor for clearly answering both with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural user phrasings ('configure load balancer', 'create ALB', 'setup nginx load balancing', 'haproxy configuration') that a user would actually say, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Load balancer configuration scoped to ALB/NLB/Nginx/HAProxy is a clear niche with distinct triggers, unlikely to conflict with unrelated skills.	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
Commit: 3022dd3

Reviewed: 2 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.