CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cost-optimization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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-organized reference with executable Terraform examples and concrete savings figures, but it carries generic padding, lacks validation checkpoints for destructive rightsizing operations, and inlines provider-specific detail that would benefit from progressive disclosure.

Suggestions

Remove the generic 'Instructions' and 'Purpose' boilerplate and let the description plus framework carry intent, tightening conciseness.

Add an explicit validation/verification step (e.g., confirm utilization metrics before downsizing, re-check spend after changes) to the Right-Sizing and idle-removal workflow.

Split the AWS/Azure/GCP sections into separate reference files referenced from SKILL.md to improve progressive disclosure and token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient bullet lists and code blocks, but the generic 'Instructions' section ('Clarify goals... Apply relevant best practices...') and redundant 'Purpose'/'Use this skill when' sections add padding Claude does not need.

3 / 5

Actionability

Provides copy-paste-ready Terraform for S3 lifecycle, tagging, budget alerts, and autoscaling plus concrete savings percentages, with only minor gaps such as missing commands for actually invoking cost tools.

4 / 5

Workflow Clarity

The four-step framework (Visibility, Right-Sizing, Pricing, Architecture) is sequenced and a checklist exists, but rightsizing and idle-resource removal are destructive/batch operations with no explicit validation or verify-fix-retry checkpoint, capping the score at 3.

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the ~280-line body inlines per-provider detail (AWS/Azure/GCP) that could live in separate reference files, and no bundle references are signaled.

3 / 5

Total

13

/

20

Passed

Description

83%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 that explicitly states concrete capabilities and clear use-when triggers in third person. It is comprehensive on completeness with only minor gaps in specificity and trigger synonym coverage.

DimensionReasoningScore

Specificity

Names four concrete actions — 'resource rightsizing, tagging strategies, reserved instances, and spending analysis' — giving solid coverage, though it omits techniques detailed in the body (anomaly detection, lifecycle policies), keeping it just below a 5.

4 / 5

Completeness

Clearly answers both what ('Optimize cloud costs through...') and when ('Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies' are natural user phrases with good coverage, but it misses common synonyms like 'lower my AWS bill' or 'cut spending'.

4 / 5

Distinctiveness Conflict Risk

'Optimize cloud costs' is a clear niche with distinct triggers and minimal conflict risk, though it could overlap slightly with general cloud-architecture or FinOps skills.

4 / 5

Total

17

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-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.