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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill configuring-auto-scaling-policies48
Quality
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/devops/auto-scaling-configurator/skills/configuring-auto-scaling-policies/SKILL.mdDiscovery
40%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 description suffers from vague capability statements despite having reasonable trigger term coverage. The phrase 'comprehensive guidance and automation' is meaningless fluff that doesn't help Claude understand what this skill actually does. The description needs concrete actions (e.g., 'configure scaling policies', 'set thresholds', 'define scaling groups') and platform specificity.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'configure scaling policies, set CPU/memory thresholds, define scaling groups, create launch templates'
Add platform context if applicable (AWS Auto Scaling, Kubernetes HPA, Azure VMSS) to improve distinctiveness
Expand trigger terms to include common variations: 'autoscale', 'scale up', 'scale down', 'horizontal scaling', 'scaling policy'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'comprehensive guidance and automation' without listing any concrete actions. It doesn't specify what auto-scaling configurations are supported or what specific tasks can be performed. | 1 / 3 |
Completeness | Has a 'Use when' equivalent in the first line and trigger phrases, but the 'what' is extremely weak - 'comprehensive guidance and automation' tells nothing about actual capabilities. The when/trigger guidance exists but the what is essentially missing. | 2 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases ('configure auto-scaling', 'set up elastic scaling', 'implement scaling') but misses common variations users might say like 'autoscale', 'scale up/down', 'horizontal scaling', 'AWS auto scaling', or cloud-specific terms. | 2 / 3 |
Distinctiveness Conflict Risk | Auto-scaling is a specific domain which helps, but 'configuration' and 'scaling' are broad enough to potentially conflict with infrastructure, cloud deployment, or Kubernetes skills. Lacks specificity about which platforms or services. | 2 / 3 |
Total | 7 / 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 provides a reasonable conceptual framework for auto-scaling configuration across multiple cloud providers, but critically lacks actionable, executable content. The absence of any actual code examples, Terraform snippets, or YAML manifests makes it more of a checklist than a skill Claude can execute. The error handling table is useful but the overall content describes rather than instructs.
Suggestions
Add at least one complete, executable example for each major platform (e.g., full Terraform HCL for AWS ASG, complete HPA YAML for Kubernetes)
Include actual CLI commands for validation steps (e.g., `aws autoscaling describe-scaling-activities --auto-scaling-group-name <name>`)
Convert the Examples section from descriptions into actual code implementations that Claude can adapt
Add explicit validation checkpoints with concrete commands to verify each step succeeded before proceeding
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., listing all cloud providers in overview, explaining what cooldown periods are). The instructions section could be tighter since Claude understands these concepts. | 2 / 3 |
Actionability | Despite listing 9 steps and mentioning outputs, there is no actual executable code, no Terraform HCL examples, no YAML manifests, no CLI commands. The 'Output' section describes what should be generated but provides zero concrete examples. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence and step 9 mentions validation, but there are no explicit validation checkpoints, no feedback loops for error recovery, and no concrete commands to verify scaling is working correctly. | 2 / 3 |
Progressive Disclosure | Content is organized into clear sections with external resource links, but the skill is somewhat monolithic. The Examples section lists use cases without actual implementations, and there's no reference to separate detailed files for each cloud provider. | 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 | |
- 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.