CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

This is a well-structured strategic/process skill with a strong framework (5 levers) and a clear 10-step workflow with appropriate validation checkpoints. Its main weaknesses are verbosity — several sections could be condensed or moved to reference files — and a lack of concrete executable artifacts like templates, scripts, or specific tool commands. The content is solid guidance but reads more like a consulting playbook than a tightly optimized skill file.

Suggestions

Move 'Common opportunities by category' and 'Failure patterns' sections into separate reference files (e.g., references/opportunities-by-category.md, references/failure-patterns.md) to reduce the main file length and improve progressive disclosure.

Add a concrete template or example for the output document — even a markdown skeleton showing what the final cost optimization report looks like with sample numbers.

Trim commentary that doesn't add actionable value, such as the pre/post-pandemic vendor negotiation observation and percentage estimates like 'Often 10-30% of spend' that Claude can assess contextually.

Add specific tool commands or references (e.g., 'aws ce get-cost-and-usage', 'gcloud billing accounts list') to make the data-gathering step more actionable.

DimensionReasoningScore

Conciseness

The skill is well-organized and mostly efficient, but it's quite long (~300+ lines) with some sections that could be tightened. The 'failure patterns' section lists 12 anti-patterns with explanations that, while useful, add significant length. The 'common opportunities by category' section partially duplicates guidance already covered in the 5 levers framework. Some commentary like 'Pre-pandemic, many vendors auto-renewed at increases. Post-pandemic, many are hungry for retention.' is unnecessary context Claude doesn't need.

2 / 3

Actionability

The skill provides a clear framework (5 levers) and a structured 10-step workflow, which is good directional guidance. However, it lacks concrete executable artifacts — no scripts, no specific CLI commands, no template files, no example cost spreadsheet structure, no sample output document. Guidance like 'the billing console and cost-explorer tools' is vague rather than specific. The 2x2 prioritization matrix is described but not templated. For a process/strategy skill this is acceptable but still falls short of fully actionable.

2 / 3

Workflow Clarity

The 10-step workflow is clearly sequenced and logically ordered: gather data → categorize → identify big items → apply framework → prioritize → execute easy wins → plan larger work → set up monitoring → negotiate renewals → document policy. It includes validation checkpoints (monitor for unexpected impact, confirm cost reduction in next billing cycle, test in staging, roll out incrementally, validate cost impact) and feedback loops. The step for larger work explicitly calls out incremental rollout and validation.

3 / 3

Progressive Disclosure

The skill references one external file (references/cloud-audit-checklist.md) and one other skill (pm-spec-writing), showing some awareness of progressive disclosure. However, the main file is very long and several sections (common opportunities by category, failure patterns) could be split into reference files. The 'when NOT to use' section nicely cross-references other skills. But overall, too much detail is inline for a skill of this length.

2 / 3

Total

9

/

12

Passed

Description

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 defines its purpose, lists concrete actions, provides explicit trigger guidance with both a 'Use this skill when...' clause and enumerated trigger terms, and occupies a distinct niche. The description is comprehensive without being padded, uses third person voice correctly, and covers both proactive scenarios (budget planning) and reactive ones (finance flagging costs).

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: audit/reduce infrastructure costs, review cloud/SaaS spend, find unused resources, rightsize infrastructure, negotiate vendor contracts, consolidate services, and plan for budget cuts.

3 / 3

Completeness

Clearly answers both 'what' (audit and reduce infrastructure/tooling costs) and 'when' (explicit 'Use this skill when...' clause with detailed trigger scenarios, plus additional trigger terms and situational triggers like finance flagging costs or contract renewals).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'cost optimization', 'cloud spend', 'SaaS spend', 'rightsizing', 'unused resources', 'FinOps', 'infrastructure audit', 'vendor consolidation', 'budget cut', 'cost review', 'contract renewal', 'rising costs'. These are terms users and finance teams would naturally use.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche around infrastructure/tooling cost optimization and FinOps. The specific domain of cost auditing, vendor negotiation, and resource rightsizing is distinct and unlikely to conflict with general infrastructure management or finance skills.

3 / 3

Total

12

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
rampstackco/claude-skills
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.