CtrlK
BlogDocsLog inGet started
Tessl Logo

cost-optimization

Strategies and patterns for optimizing cloud costs across AWS, Azure, and GCP.

47

Quality

51%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/cost-optimization/SKILL.md

The canonical home for this skill is cost-optimization in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 information-dense and largely actionable, with real Terraform and concrete savings figures, but it is essentially a monolithic reference dumped into SKILL.md: validation is implicit, generic boilerplate pads the opening, and every cross-reference points to files (and one wrong directory) that do not exist. The content works as a cheat sheet but fails as a progressively-disclosed skill.

Suggestions

Move the per-cloud deep dives and Terraform blocks into reference files (e.g. references/aws-cost-optimization.md, references/azure.md, references/gcp.md) and keep SKILL.md a concise overview with clearly signaled one-level-deep links.

Fix or remove the dangling references — create the referenced files or drop the pointers, and correct the inconsistent "resources/" vs "references/" directory name (line 23).

Add explicit validation/checkpoint steps to the framework and checklist (e.g. verify utilization before downsizing, confirm budget alert delivery after applying) since several listed actions are destructive or batch operations.

Trim the generic "Instructions" boilerplate and the repeated tagline so the body opens directly with cost-specific guidance.

DimensionReasoningScore

Conciseness

The body is mostly bullet lists, concrete savings percentages, and executable Terraform, but it carries non-minor boilerplate — the repeated tagline (line 11), the generic "Instructions" section ("Clarify goals... Apply relevant best practices and validate outcomes") that applies to any skill, and tautological "Do not use" bullets — fitting the score-3 anchor of mostly efficient with unnecessary explanation that could be tightened.

3 / 5

Actionability

It provides concrete, copy-paste-ready Terraform for S3 lifecycle, budget alerts, tagging locals, and auto-scaling plus specific instance types and percentages, but the Azure and GCP sections are bullet-only with no code and there are no CLI/analysis commands, leaving minor gaps versus the score-5 anchor.

4 / 5

Workflow Clarity

A 4-phase Cost Optimization Framework and an end checklist give a sequence, but validation checkpoints are only implicit and the generic "validate outcomes" carries no concrete verification; the checklist includes destructive/batch actions (delete unused EBS/EIPs/snapshots, downsize) with no validation step, which per the rubric caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle directories exist, yet the body points to non-existent files including a misnamed path ("resources/implementation-playbook.md" on line 23 vs "references/" elsewhere) and dangling "references/tagging-standards.md" and "assets/cost-analysis-template.xlsx"; meanwhile ~280 lines of per-cloud deep dives and four large code blocks that belong in separate reference files are all inlined in SKILL.md — broken references plus monolithic inlining fit the score-2 anchor.

2 / 5

Total

12

/

20

Passed

Description

48%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 third-person and names a clear, distinct niche but stays at an abstract level — it states what the skill is about without listing concrete actions or any explicit 'when to use it' guidance. It reads as a tagline rather than a trigger-rich, action-specific skill description.

Suggestions

Replace the abstract "Strategies and patterns for optimizing..." with concrete actions, e.g. "Right-size resources, set up budget alerts, and apply reserved-capacity savings plans across AWS, Azure, and GCP."

Add an explicit trigger clause, e.g. "Use when reducing cloud spend, right-sizing resources, implementing cost governance, or meeting budget constraints."

Include natural user phrases and synonyms ("cloud bill", "cost savings", "cut spend") so the skill triggers on how users actually phrase the need.

DimensionReasoningScore

Specificity

The description "Strategies and patterns for optimizing cloud costs across AWS, Azure, and GCP" names the domain and the three clouds concretely but offers no concrete actions — "Strategies and patterns" is abstract with no verbs, matching the score-2 anchor that names the domain with minimal/generic actions.

2 / 5

Completeness

It states a clear 'what' (strategies/patterns for optimizing cloud costs across the three clouds) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

"cloud costs", "optimizing", and the provider names AWS/Azure/GCP are relevant natural keywords, but it misses common variations users say like "reduce cloud spend", "AWS bill", "cost savings", or "budget" — some keywords present, missing common synonyms.

3 / 5

Distinctiveness Conflict Risk

"Cloud cost optimization across AWS, Azure, and GCP" is a fairly distinct niche with only minor overlap risk against adjacent cloud-architecture or terraform skills, fitting the score-4 anchor; not a 5 because there are no distinct trigger phrases to separate it from related cloud skills.

4 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.