configuring-auto-scaling-policies
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill configuring-auto-scaling-policiesConfigure 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no auto-scaling-specific content whatsoever. It could apply to literally any DevOps task by replacing the title. There are no concrete examples of scaling policies, thresholds, cloud provider APIs, or configuration syntax that would actually help Claude configure auto-scaling.
Suggestions
Add concrete, executable examples of auto-scaling configuration (e.g., AWS Auto Scaling Group policies, Kubernetes HPA manifests, or specific cloud provider CLI commands)
Remove generic software development advice (backup data, test in staging, get approval) and replace with auto-scaling-specific guidance like threshold tuning, cooldown periods, and scaling metrics
Include specific validation steps for auto-scaling such as 'trigger a load test to verify scale-out at 70% CPU' or 'verify scale-in doesn't terminate during deployment'
Provide at least one complete, copy-paste-ready configuration example with actual values and explanations of key parameters
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Explains obvious concepts like 'backup critical data' and 'test in staging' that Claude already knows. No auto-scaling-specific content despite the skill title. | 1 / 3 |
Actionability | Entirely abstract with no concrete code, commands, or auto-scaling-specific examples. Phrases like 'Execute implementation' and 'Define optimal approach' provide zero executable guidance. No actual scaling configuration syntax, API calls, or tool usage shown. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic software development steps, not auto-scaling-specific workflows. No validation checkpoints specific to scaling (e.g., verify scaling triggers work, test scale-up/down thresholds). Missing feedback loops for testing scaling behavior. | 2 / 3 |
Progressive Disclosure | References external files in Resources section with clear paths, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths that may not exist. Overview and Examples sections at the bottom are empty placeholders. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
40%This description suffers from vague capability statements that rely on buzzwords ('comprehensive guidance and automation') rather than concrete actions. While it includes some trigger phrases, it fails to explain what the skill actually does or which platforms/systems it supports. The description would benefit significantly from listing specific actions and clarifying the scope.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'Create scaling policies, configure thresholds, set up CloudWatch alarms, define scaling schedules'
Specify the target platform(s) - e.g., 'AWS Auto Scaling Groups', 'Kubernetes HPA', or 'Azure VMSS' to improve distinctiveness
Add more natural trigger terms users would say: 'scale up', 'scale down', 'handle traffic spikes', 'horizontal scaling', 'scaling policies'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'comprehensive guidance and automation' without listing any concrete actions. It doesn't specify what configurations are possible, what systems it works with, or what specific tasks it performs. | 1 / 3 |
Completeness | Has a 'Trigger with phrases like...' clause which partially addresses 'when', but the 'what' is extremely weak - 'comprehensive guidance and automation' tells nothing about actual capabilities. The trigger guidance exists but is not framed as explicit 'Use when...' format. | 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 'scale up', 'scale down', 'horizontal scaling', 'AWS auto-scaling', or specific platform terms. | 2 / 3 |
Distinctiveness Conflict Risk | Auto-scaling is a specific enough domain to avoid conflicts with most skills, but without specifying which platform (AWS, Azure, Kubernetes, etc.) or what type of scaling, it could overlap with cloud infrastructure or DevOps skills. | 2 / 3 |
Total | 7 / 12 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.