cost-optimization
Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
Overall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 98%
↑ 1.40xAgent success when using this skill
Validation for skill structure
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 well-crafted skill description that follows best practices. It uses third person voice, lists specific concrete capabilities, includes an explicit 'Use when' clause with natural trigger terms, and carves out a distinct niche in cloud cost optimization that wouldn't easily conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'resource rightsizing, tagging strategies, reserved instances, and spending analysis' - these are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (optimize cloud costs through specific methods) AND when (explicit 'Use when' clause covering reducing expenses, analyzing costs, implementing governance policies). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'cloud costs', 'cloud expenses', 'infrastructure costs', 'cost governance', 'rightsizing', 'reserved instances' - good coverage of terms across different user phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on cloud cost optimization with distinct triggers like 'rightsizing', 'reserved instances', 'cost governance' - unlikely to conflict with general cloud or finance skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance with executable Terraform examples and concrete savings figures across AWS, Azure, and GCP. However, it's somewhat verbose with framework sections that could be condensed, and lacks explicit validation workflows for verifying cost optimization changes. The content would benefit from better progressive disclosure by splitting cloud-specific details into separate reference files.
Suggestions
Add a validation workflow with explicit checkpoints: e.g., 'Before applying reserved instances: 1. Analyze 30-day utilization data, 2. Verify steady-state workloads, 3. Calculate break-even point, 4. Start with convertible RIs for flexibility'
Remove or condense the 'Purpose' and 'When to Use' sections - these restate obvious information that Claude can infer from the skill description
Split cloud-specific sections (AWS, Azure, GCP) into separate reference files and keep only a comparison overview in the main skill
Add a feedback loop for cost verification: 'After implementing changes, wait 7 days and compare Cost Explorer data to baseline to validate savings'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary framing (e.g., 'Purpose', 'When to Use' sections that restate obvious information). The framework sections could be more condensed, and some bullet lists repeat concepts Claude already knows about cloud cost optimization. | 2 / 3 |
Actionability | Provides fully executable Terraform/HCL code examples for S3 lifecycle policies, budget alerts, auto-scaling, and tagging. Includes specific savings percentages, concrete patterns, and copy-paste ready configurations across all three major cloud providers. | 3 / 3 |
Workflow Clarity | The checklist at the end provides a sequence, but there's no clear workflow for implementing cost optimization with validation checkpoints. Missing feedback loops for verifying cost reductions after changes, and no explicit 'validate before proceeding' steps for potentially impactful changes like rightsizing. | 2 / 3 |
Progressive Disclosure | References external files (tagging-standards.md, cost-analysis-template.xlsx) appropriately, but the main document is quite long with inline content that could be split. The multi-cloud sections could be separate files with the main skill providing an overview and navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 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.