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.
74
61%
Does it follow best practices?
Impact
98%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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 well-crafted skill description that follows best practices closely. It uses third person voice, lists specific concrete capabilities, includes an explicit 'Use when' clause with natural trigger terms, and occupies a clearly distinct niche. The description is concise yet comprehensive, covering both the what and when effectively.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'resource rightsizing', 'tagging strategies', 'reserved instances', and 'spending analysis'. These are distinct, well-defined cloud cost optimization activities. | 3 / 3 |
Completeness | Clearly answers both 'what' (optimize cloud costs through rightsizing, tagging, reserved instances, spending analysis) and 'when' (explicit 'Use when' clause covering reducing expenses, analyzing costs, implementing governance policies). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'cloud costs', 'rightsizing', 'reserved instances', 'spending analysis', 'cloud expenses', 'infrastructure costs', 'cost governance'. These cover common variations of how users discuss cloud cost optimization. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly occupies a distinct niche around cloud cost optimization with specific triggers like 'rightsizing', 'reserved instances', 'tagging strategies', and 'cost governance' that are 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's overly broad, covering three cloud providers at a surface level with mostly generic advice Claude already knows. The few Terraform examples are valuable but are buried in verbose, catalog-style content that lacks clear workflows, validation steps, or specific commands for actually performing cost analysis and optimization.
Suggestions
Add a concrete step-by-step workflow for performing cost optimization (e.g., 1. Run `aws ce get-cost-and-usage` to analyze current spend, 2. Run `aws compute-optimizer get-ec2-instance-recommendations` to find rightsizing opportunities, 3. Validate changes in staging, 4. Apply changes with rollback plan).
Remove generic bullet-point advice Claude already knows (e.g., 'Use managed services', 'Implement caching') and focus on specific, executable commands and scripts for each optimization action.
Split per-cloud-provider content into separate reference files and keep SKILL.md as a concise overview with the core workflow and decision framework.
Add validation checkpoints and rollback procedures, especially for destructive operations like deleting resources or changing instance types.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250 lines, with much content Claude already knows (what reserved instances are, what spot instances are, basic cloud pricing concepts). Bullet-point lists like 'Use managed services', 'Implement caching' are generic advice that don't add value. The multi-cloud coverage is broad but shallow, padding token count without providing deep 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, much of the content is vague bullet points ('Analyze resource utilization', 'Downsize over-provisioned resources') without specific commands or scripts to actually perform these actions. No concrete CLI commands for cost analysis or rightsizing recommendations. | 2 / 3 |
Workflow Clarity | There is no clear sequential workflow for performing cost optimization. The content is organized as a reference catalog of options rather than a step-by-step process. For a skill involving potentially destructive operations (deleting resources, changing instance types), there are no validation checkpoints, rollback procedures, or feedback loops. The checklist at the end is a flat list without sequencing or verification steps. | 1 / 3 |
Progressive Disclosure | There are references to external files (references/tagging-standards.md, assets/cost-analysis-template.xlsx) and related skills, which is good. However, the main file is monolithic with extensive inline content that could be split into separate files per cloud provider or per optimization strategy. The structure has sections but they're all dumped into one long document. | 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
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.