CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cost-optimization

Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity. Use this skill when reviewing monthly cloud or SaaS spend, finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning for budget cuts. Triggers on cost optimization, cloud spend, SaaS spend, rightsizing, unused resources, FinOps, infrastructure audit, vendor consolidation, budget cut, cost review. Also triggers when finance flags rising costs or when a contract renewal is up.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, disciplined instruction-only skill: a 5-lever framework, a 10-step workflow with validation checkpoints, concrete failure patterns, an output format, an honest data-gap policy, and one appropriately scoped reference file. The body leans on summary-level specifics where a few executable commands or an explicit rollback loop would make the guidance fully executable.

Suggestions

Add an explicit error-recovery step to the workflow (e.g., in Step 6: if monitoring shows unexpected impact after a change, revert and re-assess) to close the feedback loop for destructive actions like canceling subscriptions and tearing down resources.

Include one or two example commands for pulling spend data (e.g., an AWS Cost Explorer CLI call or a billing-export command) so Step 1 is copy-paste executable rather than portal-level guidance.

Consolidate the "Common opportunities by category" section into the cloud-audit-checklist reference (or trim it to category names with one-line pointers), reducing duplication with the Lever sections and shrinking the body's token footprint.

DimensionReasoningScore

Conciseness

Terse bullet style throughout that assumes competence and adds curated judgment (80/20 focus, 2x2 prioritization, discount ranges) rather than explaining known concepts. Minor trims available: the mirrored "Build vs buy"/"Buy vs build" lines, overlap between "Common opportunities by category" and the Lever sections, and the "Pre-pandemic/Post-pandemic" aside — anchor 4, not 5.

4 / 5

Actionability

Concrete specifics throughout — "12 months minimum", "60-90 days before renewal", "30-70% discount", the lever question table, and a defined output format — but stops short of executable commands for pulling spend data (e.g., a cloud CLI cost-export example), keeping it at anchor 4 rather than fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

A clear 10-step sequence with real validation checkpoints (owner approval, "Test in staging", "Monitor for unexpected impact", "Confirm cost reduction in next billing cycle", risk-tiered prioritization), which clears the destructive-operation cap. It falls short of anchor 5 only because no explicit recovery loop exists for when a change causes impact or savings fail to materialize.

4 / 5

Progressive Disclosure

A single, clearly signaled, one-level-deep reference whose description accurately matches the actual file content, over a well-sectioned body. Anchor 4 rather than 5 because the ~50-line "Common opportunities by category" section partially duplicates the reference checklist's territory and could be consolidated into it.

4 / 5

Total

16

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capabilities, an explicit "Use this skill when" clause with scenario-based triggers, and a dedicated trigger-term list with synonyms. The only weakness is that a few common user phrasings around saving money are missing from the trigger list.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "finding unused resources, rightsizing infrastructure, negotiating vendor contracts, deciding what to consolidate, or planning for budget cuts" — with comprehensive coverage of the audit-to-savings lifecycle; no gaps that would place it at anchor 4.

5 / 5

Completeness

Explicitly answers both what ("Audit and reduce infrastructure and tooling costs without sacrificing reliability or velocity") and when ("Use this skill when reviewing monthly cloud or SaaS spend...") with concrete trigger phrases — a direct match for anchor 5.

5 / 5

Trigger Term Quality

Ten explicit trigger terms including the synonym "FinOps" plus scenario triggers ("finance flags rising costs", "contract renewal is up"), but a few natural everyday phrasings users would say ("save money", "cut costs", "reduce spend", "our cloud bill is too high") are absent. This fits anchor 4 rather than 5's comprehensive-synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear FinOps/cost niche with distinct triggers (rightsizing, budget cut, vendor consolidation) unlikely to pull the wrong skill, though "negotiating vendor contracts" carries minor overlap risk with a vendor-evaluation or procurement skill — anchor 4, not 5.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/cost-optimization/SKILL.md

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.