configuring-auto-scaling-policies

Configure use when you need to work with auto-scaling. This skill provides auto-scaling configuration with comprehensive guidance and automation. Trigger with phrases like "configure auto-scaling", "set up elastic scaling", or "implement scaling".

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/devops/auto-scaling-configurator/skills/configuring-auto-scaling-policies/SKILL.md

Quality

Content

80%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.

The content is concise and actionable with concrete thresholds and commands, but its workflow lacks an explicit validation feedback loop and it fails to surface the bundled templates and scripts that already exist alongside it.

Suggestions

Add an explicit feedback loop after step 9: if validation fails, revise thresholds/cooldown and re-simulate rather than treating validation as terminal.

Link the existing bundle files in the body (e.g., 'See assets/example_hpa.yaml' and 'Use scripts/generate_config.py to produce configs') so progressive disclosure is actually navigable.

Reconcile the bundle READMEs: remove unchecked checkbox markers and delete references to non-existent scripts (validate_config.py, deploy_config.sh).

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, avoiding explanations of what auto-scaling or cloud providers are, with every section (overview, prerequisites, steps, error table, examples, resource links) earning its place.	3 / 3
Actionability	Steps give concrete, specific guidance—exact thresholds (CPU > 70%, < 30%), cooldown values (300s/600s), named output formats, and real CLI commands in the error table—which is actionable without code, and the rubric does not penalize code absence in instruction skills when guidance is actionable.	3 / 3
Workflow Clarity	The nine steps are clearly sequenced and include a validation step (step 9), but there is no explicit validate→fix→retry feedback loop integrated into the workflow, and for infra scaling (a destructive/batch-adjacent operation) the missing inline checkpoints cap this at the 'sequence present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	The body is well-sectioned, but it never references the existing bundle files (assets/config_template.yaml, example_hpa.yaml, example_aws_scaling_policy.json, scripts/generate_config.py), and the bundle READMEs are inconsistent—using unchecked checkboxes and naming scripts (validate_config.py, deploy_config.sh) that do not exist—so references are present but unsignaled, matching the 'some structure but not clearly signaled' anchor.	2 / 3
	Total	10 / 12 Passed

Description

75%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.

The description answers both 'what' and 'when' with explicit trigger phrases and occupies a distinct niche, but its capability statement is padded with buzzwords and its trigger-term coverage is narrow.

Suggestions

Replace 'comprehensive guidance and automation' with concrete capabilities, e.g. 'Generate AWS ASG, GCP MIG, Azure VMSS, and Kubernetes HPA scaling policies with thresholds and cooldowns'.

Broaden trigger terms to include common variations like 'autoscale', 'scale out', 'scale in', and 'HPA'.

Fix the opening grammar ('Configure use when...') into a clean third-person capability statement.

Dimension	Reasoning	Score
Specificity	Names the auto-scaling domain and the action 'configure', but leans on fluff ('comprehensive guidance and automation') rather than listing multiple concrete actions, so it falls short of the comprehensive-anchor and above the vague-anchor.	2 / 3
Completeness	It states what the skill does ('auto-scaling configuration') and includes an explicit 'use when' clause plus trigger phrases, satisfying both the what and the when with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural trigger phrases ('configure auto-scaling', 'set up elastic scaling', 'implement scaling') a user might say, but coverage is narrow with no common variations like 'autoscale', 'scale out', or 'HPA', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Auto-scaling/elastic scaling is a clear niche with distinct trigger terms unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	10 / 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/auto-scaling-configurator/skills/configuring-auto-scaling-policies/SKILL.md
Commit: c4eafaf

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