cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
69
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/cloud-infrastructure/skills/cost-optimization/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly articulates specific capabilities (rightsizing, tagging, reserved instances, spending analysis) across named cloud providers, includes an explicit 'Use when' clause with natural trigger terms, and occupies a distinct niche. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: resource rightsizing, tagging strategies, reserved instances, and spending analysis across named cloud providers (AWS, Azure, GCP, OCI). | 3 / 3 |
Completeness | Clearly answers both 'what' (optimize cloud costs through rightsizing, tagging, reserved instances, spending analysis) and 'when' (explicit 'Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'cloud costs', 'AWS', 'Azure', 'GCP', 'rightsizing', 'reserved instances', 'cloud expenses', 'infrastructure costs', 'cost governance'. These cover common variations of how users discuss cloud cost optimization. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused on cloud cost optimization across specific providers. The combination of cost-specific actions and named cloud platforms makes it unlikely to conflict with general cloud infrastructure or DevOps skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a cloud cost optimization wiki page than an actionable skill for Claude. It is overly verbose, mixing well-known cloud pricing facts with some useful Terraform snippets. It lacks a clear workflow for actually performing cost optimization tasks and would benefit significantly from being restructured as a concise overview with references to detailed sub-files.
Suggestions
Restructure as a concise overview (under 80 lines) with a clear step-by-step workflow for cost optimization, moving provider-specific details into separate reference files (e.g., aws-cost-optimization.md, azure-cost-optimization.md).
Add an explicit multi-step workflow with validation checkpoints, e.g.: 1. Audit current costs → 2. Identify savings opportunities → 3. Implement changes → 4. Validate savings → 5. Set up ongoing monitoring.
Remove generic descriptions Claude already knows (e.g., what reserved instances are, what spot instances are) and focus on specific, executable patterns and decision criteria for when to use each approach.
Add concrete examples of cost analysis commands or scripts (e.g., AWS CLI commands to find unused resources, specific queries for Cost Explorer) rather than just listing tool names.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines, with significant padding. Sections like 'When to Use' bullet lists, the 4-step 'Cost Optimization Framework' of generic advice, and Azure/GCP/OCI sections that mostly list well-known facts Claude already knows (e.g., 'Up to 72% savings', 'Automatic discounts') add little value. Much of this is cloud documentation summary rather than novel, actionable guidance. | 1 / 3 |
Actionability | There are some concrete Terraform code examples (S3 lifecycle, budget alerts, auto-scaling, tagging) that are executable and copy-paste ready. However, large portions are descriptive bullet points and plain-text summaries (e.g., Azure, GCP, OCI sections) with no executable code or specific commands. The mix is uneven. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow or sequenced process for performing cost optimization. The content is organized as a reference catalog of options rather than a guided process. The checklist at the end is useful but lacks sequencing, validation checkpoints, or feedback loops for what are potentially impactful infrastructure changes. | 1 / 3 |
Progressive Disclosure | There is one reference to 'references/tagging-standards.md' and mentions of related skills at the bottom, showing some awareness of progressive disclosure. However, the bulk of the content is monolithic — the Azure, GCP, OCI, and architecture pattern sections could easily be split into separate reference files. The skill would benefit greatly from being a concise overview pointing to detailed sub-documents. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
70444e5
- 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.