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 a clear 'Use when' clause with natural trigger terms, and occupies a distinct niche. The description is concise yet comprehensive, covering both the actions performed and the scenarios that should trigger its selection.
| 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 reference guide or study material than an actionable skill for Claude. While it includes some useful Terraform examples, the majority of content is generic cloud knowledge that Claude already possesses, and it lacks a clear workflow for actually performing cost optimization tasks. The content would benefit significantly from being restructured into a concise overview with specific procedures and delegating cloud-specific details to reference files.
Suggestions
Replace generic bullet-point advice (e.g., 'Analyze resource utilization', 'Use managed services') with specific CLI commands or scripts that Claude should run to identify optimization opportunities (e.g., AWS CLI commands to find underutilized instances).
Add a clear sequenced workflow: e.g., 1) Run cost analysis commands, 2) Identify top spending categories, 3) Generate rightsizing recommendations, 4) Validate changes won't impact performance, 5) Apply changes with verification.
Move cloud-specific details (AWS, Azure, GCP sections) into separate reference files and keep only a concise overview with links in the main skill file.
Remove explanatory content Claude already knows (what reserved instances are, what spot instances do, basic cloud pricing concepts) and focus only on decision criteria and implementation specifics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose and padded with information Claude already knows (what reserved instances are, what spot instances are, general cloud pricing concepts). Bullet lists like 'Use managed services', 'Implement caching' are generic advice that don't add value. Much of the content reads like a cloud certification study guide rather than actionable instructions for Claude. | 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-point advice ('Analyze resource utilization', 'Downsize over-provisioned resources') without specific commands or procedures for actually performing cost analysis or identifying waste. | 2 / 3 |
Workflow Clarity | There is no clear sequenced workflow for performing cost optimization. The content is organized as a reference catalog of options rather than a step-by-step process. The checklist at the end is helpful but lacks sequencing, validation checkpoints, or feedback loops. For operations that could have significant financial impact (deleting resources, changing instance types), there are no 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 a monolithic wall of content (~200+ lines) with much that could be split into separate reference files (AWS-specific, Azure-specific, GCP-specific details). The inline content is too extensive for an overview skill. | 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
47823e3
- 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.