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 high-level strategic advice Claude already knows with some useful but scattered Terraform examples. The lack of a clear workflow, validation steps, and heavy reliance on descriptive bullet points significantly reduce its effectiveness as operational guidance.
Suggestions
Add a clear sequential workflow (e.g., 'Step 1: Audit current costs using X command, Step 2: Identify idle resources by running Y, Step 3: Validate changes before applying') with explicit validation checkpoints.
Remove or drastically condense the framework overview, 'When to Use', and 'Purpose' sections—Claude already understands cloud cost optimization concepts.
Move cloud-specific details (AWS, Azure, GCP, OCI) into separate reference files and keep only a concise summary with links in the main skill.
Add executable code examples for Azure, GCP, and OCI sections comparable to the AWS Terraform examples, or remove those sections if they can't be made actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines, with significant padding. Sections like 'When to Use', 'Cost Optimization Framework', and cloud-specific bullet lists largely restate common knowledge Claude already possesses. The 'Purpose' section and framework overview add little actionable value beyond what any cloud practitioner would know. | 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 just bullet-point descriptions ('Analyze resource utilization', 'Use managed services') without concrete commands, scripts, or specific thresholds. The Azure, GCP, and OCI sections are almost entirely descriptive with no executable code. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow or sequenced process for actually 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 financial decisions. | 1 / 3 |
Progressive Disclosure | There is one reference to 'references/tagging-standards.md' and links to related skills at the bottom, showing some awareness of progressive disclosure. However, the bulk of the content is a monolithic wall of text that could benefit greatly from splitting cloud-specific details into separate files, with the main skill serving as a concise overview with navigation. | 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
27a7ed9
- 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.