CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A well-organized, actionable reference with executable Terraform and concrete savings data, but it is a long, near-monolithic body that repeats patterns across providers and lacks explicit validation checkpoints in its optimization workflow.

Suggestions

Tighten conciseness by collapsing the repetitive AWS/Azure/GCP/OCI pricing-model sections into a comparison table and removing overlap with the high-level Cost Optimization Framework.

Add explicit validation checkpoints to the workflow (e.g., 'verify utilization data before downsizing', 'confirm savings via Cost Explorer after switching to reserved capacity') with a feedback loop for batch right-sizing operations.

Move per-provider deep-dive detail into separate reference files (e.g., references/aws-cost.md) and keep SKILL.md as a concise overview that links to them, improving progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient reference content (savings percentages, Terraform blocks, tool lists) without explaining basics Claude already knows, but the ~300-line body repeats a similar pattern across AWS/Azure/GCP/OCI and the high-level 'Cost Optimization Framework' overlaps the per-provider sections, so it could be tightened.

2 / 3

Actionability

Provides executable Terraform for S3 lifecycle, tagging, budgets, and autoscaling plus specific savings figures and named tooling — concrete and copy-paste ready rather than abstract direction.

3 / 3

Workflow Clarity

The four-phase 'Cost Optimization Framework' and end checklist give a sequence, but steps are categorical bullet lists without explicit validation checkpoints or feedback loops, so checkpoints are only implicit.

2 / 3

Progressive Disclosure

There is one clearly signaled, real, one-level-deep reference ('See references/tagging-standards.md', which exists), but the bulk of per-provider detail lives inline in SKILL.md rather than being split into well-organized separate files.

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.

A strong, concise description that names concrete capabilities across four cloud providers and includes an explicit 'Use when' trigger clause in third person. It answers both 'what' and 'when' clearly with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'resource rightsizing, tagging strategies, reserved instances, and spending analysis' — naming the domain (AWS, Azure, GCP, OCI) and specific optimization techniques rather than vague language.

3 / 3

Completeness

Clearly states both what it does (optimize cloud costs across providers via named techniques) and when to use it with an explicit 'Use when...' trigger clause.

3 / 3

Trigger Term Quality

The 'Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies' clause provides several natural phrases a user would say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The multi-cloud cost-optimization niche with provider names and cost-specific triggers is distinct and unlikely to conflict with unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.