cost-optimization

Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/cloud-infrastructure/skills/cost-optimization/SKILL.md

Quality

Content

65%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.

The body is a well-organized, largely actionable catalog with concrete Terraform examples and savings figures, but it functions more as an inlined reference manual than a lean overview. Workflow clarity is capped by missing validation steps around destructive/batch cost actions.

Suggestions

Add a validation/verification step before destructive actions like deleting unused resources or downsizing instances (e.g., confirm utilization thresholds, snapshot first).

Move per-cloud detail sections into separate reference files (e.g., references/aws-cost.md) and keep SKILL.md as a concise overview with signaled links.

Trim the redundant 'Purpose' section and opening line that restate the description.

Dimension	Reasoning	Score
Conciseness	Mostly lean bullet lists and code blocks with concrete savings percentages, but the 'Purpose' and opening line restate the frontmatter description and a few bullet sections could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready Terraform for S3 lifecycle, tagging, budgets, and autoscaling alarms, though several Azure/GCP/OCI sections remain high-level bullet advice without executable commands.	4 / 5
Workflow Clarity	The four-stage framework (Visibility, Right-Sizing, Pricing, Architecture) gives a rough sequence but lacks explicit validation checkpoints, and destructive/batch actions like 'Delete unused resources' have no verification step, capping this at 3.	3 / 5
Progressive Disclosure	There is a clearly signaled one-level reference (references/tagging-standards.md) and good section structure, but ~310 lines of per-cloud detail that could live in separate reference files are inlined in SKILL.md.	3 / 5
	Total	14 / 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.

The description is strong: it states concrete capabilities, names all four target clouds, and includes an explicit 'Use when' trigger clause. It is held back only by slightly less-than-comprehensive action coverage and a few missing natural synonyms.

Suggestions

Add spot/preemptible instances and cost anomaly detection to the action list for fuller coverage.

Include user-natural synonyms like 'cut cloud costs' or 'lower my AWS bill' in the trigger clause.

Tighten distinctiveness by contrasting with general FinOps governance skills.

Dimension	Reasoning	Score
Specificity	Names four concrete actions ('resource rightsizing, tagging strategies, reserved instances, and spending analysis') across four clouds, but omits techniques covered in the body like spot/preemptible instances and anomaly detection, so it stops short of comprehensive.	4 / 5
Completeness	Explicitly answers both 'what' (optimize cloud costs across AWS/Azure/GCP/OCI via named techniques) and 'when' ('Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases ('reducing cloud expenses', 'analyzing infrastructure costs', 'implementing cost governance policies') align with what users would say, though common synonyms like 'cloud bill', 'cut costs', or specific provider billing terms are missing.	4 / 5
Distinctiveness Conflict Risk	The multi-cloud cost-optimization niche is distinct with specific provider names, but it could overlap with a generic FinOps or cloud-governance skill, leaving minor conflict risk.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Path: plugins/cloud-infrastructure/skills/cost-optimization/SKILL.md
Commit: d6837ae

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

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.