aws-cost-optimizer

Comprehensive AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer

1.17x

Quality

64%

Does it follow best practices?

Impact

94%

1.17x

Average score across 3 eval scenarios

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/aws-cost-optimizer/SKILL.md

The canonical home for this skill is aws-cost-optimizer in boisenoise/skills-collections

Quality

Content

76%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 highly actionable with concrete, executable AWS CLI commands and a clear sequenced workflow, but its destructive quick-win steps lack inline validation checkpoints and several sections overlap, adding some redundancy. Structure is good though not maximally split.

Suggestions

Embed explicit validation checkpoints in the Optimization Workflow before destructive steps, e.g. 'List and review unattached volumes → confirm with owner → delete', with a verify-then-act feedback loop.

Consolidate the overlapping Cost Optimization Checklist and Best Practices into a single section to reduce redundancy.

Consider moving the full AWS CLI command catalog and Example Prompts into a reference file (e.g. references/commands.md) to keep SKILL.md a leaner overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The body is largely lean, assuming AWS knowledge and leading with concrete CLI commands; minor redundancy between the Cost Optimization Checklist, Best Practices, and Example Prompts sections and the Kiro integration block keeps it just below level-5 'every token earns its place'.	4 / 5
Actionability	Provides copy-paste-ready aws ce/ec2/cloudwatch commands with real flags and --query/--output patterns covering cost trends, unused resources, and rightsizing — fully executable guidance matching the level-5 anchor.	5 / 5
Workflow Clarity	The Optimization Workflow lists a clear 4-step sequence, but destructive/batch steps like 'Delete unattached EBS volumes' and 'Stop/terminate idle EC2 instances' lack inline validation checkpoints; per the destructive-ops cap this cannot exceed 3 even though a Safety Notes section mentions verification separately.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized section headers; it inlines a sizable command catalog and checklist that could be split out, placing it at 'good structure, minor organization gaps' rather than the level-5 ideal of one-level-deep signaled references.	4 / 5
	Total	16 / 20 Passed

Description

53%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 names a clear, distinct niche (AWS cost optimization) but is held back by a missing explicit "Use when…" trigger clause, generic action wording, an over-claim buzzword ("Comprehensive"), and absent common synonyms. It is functional but not exemplary.

Suggestions

Add an explicit 'Use when…' clause listing concrete triggers, e.g. 'Use when analyzing AWS spending, reducing cloud waste, or auditing AWS bills'.

Replace the over-claim "Comprehensive" with specific actions like 'identifies idle EC2 instances, unattached EBS volumes, and Reserved Instance opportunities'.

Include natural synonyms users actually say — "spending", "billing", "cloud waste", "reduce AWS costs" — to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Quotes "AWS cost analysis" and "optimization recommendations" name the domain plus two actions, but the actions are generic and "Comprehensive" is an over-claim buzzword; not the level-4 list of several specific actions, nor the level-2 minimal 'names domain only'.	3 / 5
Completeness	The description gives a clear "what" but contains no "Use when…" clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3; it is above level-2 (which has only a vague what) but lacks the explicit when of level-4.	3 / 5
Trigger Term Quality	Includes natural terms like "AWS cost" and "optimization" plus "Cost Explorer", but misses common synonyms a user would say ("spending", "billing", "cloud waste", "reduce costs"), so it sits at 'some relevant keywords, missing variations' rather than level-4 good coverage.	3 / 5
Distinctiveness Conflict Risk	"AWS cost analysis and optimization recommendations using AWS CLI and Cost Explorer" carves a clear niche with low conflict risk; it is not the level-5 fully-distinct trigger phrasing but is mostly distinct with only minor overlap against general optimization skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/aws-cost-optimizer/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.