Name: cost-optimization
Rating: 46.400000000000006 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

cost-optimization

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

Quality

49%

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

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

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 content is action-rich with concrete Terraform examples and concrete savings numbers, but it is held back by generic filler, a non-sequenced framework lacking validation checkpoints, and dangling references to bundle files that are not actually present.

Suggestions

Create the referenced bundle files (references/tagging-standards.md, assets/cost-analysis-template.xlsx, resources/implementation-playbook.md) or remove the dangling references; also fix the inconsistent "resources/" vs "references/" path.

Add an explicit validation checkpoint to the workflow for destructive/batch actions, e.g. after right-sizing or deleting idle resources, verify utilization and spend before and after the change.

Remove the generic Instructions filler ("Clarify goals… Apply best practices…") and the duplicated description line to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete (savings percentages, Terraform snippets, a checklist) but includes unnecessary filler such as the generic Instructions ("Clarify goals… Apply relevant best practices and validate outcomes") and a repeated copy of the description, so it could be tightened toward anchor 4 but currently sits at 3.	3 / 5
Actionability	It provides several concrete, mostly copy-paste-ready Terraform examples (S3 lifecycle, common tags, budget alert, auto-scaling policy) plus specific savings figures, matching anchor 4 with only minor gaps such as Pattern 2 being a text list rather than code.	4 / 5
Workflow Clarity	The Cost Optimization Framework presents four areas as a taxonomy rather than a sequenced workflow, and there are no validation/verification checkpoints for batch or destructive operations (deleting idle resources, right-sizing), which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Although section headers are well-organized, the body references files that do not exist (resources/implementation-playbook.md, references/tagging-standards.md, assets/cost-analysis-template.xlsx — none of these directories are present) and inlines ~280 lines that could be split out, leaving navigation broken and matching anchor 2.	2 / 5
	Total	12 / 20 Passed

Description

45%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 clearly scopes the domain (cloud cost optimization across AWS, Azure, GCP) but stays generic, naming no concrete actions and offering no explicit "Use when" trigger guidance. It is adequately distinct but would benefit from specific capabilities and trigger phrases.

Suggestions

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

Add an explicit trigger clause such as "Use when reducing cloud spend, right-sizing resources, or meeting cloud budget constraints."

Include common synonyms users actually say ("cloud spend", "cloud bill", "FinOps", "cost savings") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and the three clouds ("optimizing cloud costs across AWS, Azure, and GCP") but the only actions are the generic "Strategies and patterns for optimizing", with no concrete actions like right-sizing or budget alerts, matching the anchor 2 example "Processes PDF files".	2 / 5
Completeness	It gives a clear "what" (strategies and patterns for optimizing cloud costs across the three clouds) but provides no "Use when…" trigger guidance, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	It includes relevant natural keywords ("cloud costs", AWS, Azure, GCP) but misses common variations and synonyms users say such as "spending", "bill", "budget", or "FinOps", so it sits at anchor 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	The cost focus plus three-cloud scoping is somewhat specific, but the generic "strategies and patterns" phrasing leaves overlap risk with general FinOps or multi-cloud architecture skills, matching anchor 3.	3 / 5
	Total	11 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/cost-optimization/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.