aws-cost-optimizer

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

1.17x

Quality

41%

Does it follow best practices?

Impact

94%

1.17x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-aws-cost-optimizer/SKILL.md

Quality

Discovery

32%

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 identifies a clear domain (AWS cost optimization) and mentions specific tools, but lacks concrete action details and entirely omits a 'Use when...' clause. It reads more like a title than a functional description that would help Claude reliably select this skill from a large pool of available skills.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about AWS spending, cloud costs, billing analysis, cost reduction, or wants to optimize their AWS bill.'

List specific concrete actions such as 'Analyzes AWS spending by service, identifies unused resources, recommends Reserved Instance purchases, reviews cost allocation tags, and generates savings plans recommendations.'

Include natural language variations users might say, such as 'cloud spending', 'AWS bill', 'reduce costs', 'billing breakdown', 'savings plans', and 'cost allocation'.

Dimension	Reasoning	Score
Specificity	Names the domain (AWS cost) and some actions ('cost analysis' and 'optimization recommendations'), and mentions tools (AWS CLI, Cost Explorer), but doesn't list multiple specific concrete actions like identifying unused resources, rightsizing instances, or analyzing billing breakdowns.	2 / 3
Completeness	Describes what it does (AWS cost analysis and optimization recommendations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also not very detailed, so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'AWS', 'cost', 'Cost Explorer', and 'AWS CLI' which users might mention, but misses common natural variations like 'cloud spending', 'billing', 'savings', 'budget', 'cloud costs', or 'reduce AWS bill'.	2 / 3
Distinctiveness Conflict Risk	The combination of AWS cost analysis with specific tools (AWS CLI, Cost Explorer) provides some distinctiveness, but could overlap with general AWS skills or cloud infrastructure skills. Adding more specific triggers would help differentiate it.	2 / 3
	Total	7 / 12 Passed

Implementation

50%

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

The skill provides genuinely useful, executable AWS CLI commands for cost analysis and resource optimization, which is its strongest aspect. However, it suffers from significant bloat — sections like 'Example Prompts,' 'Core Capabilities' overview, and generic best practices add little that Claude doesn't already know. The workflow for destructive operations (deleting volumes, snapshots, IPs) lacks explicit validation/confirmation steps, which is a notable gap for a skill involving resource deletion.

Suggestions

Remove the 'When to Use This Skill', 'Core Capabilities', 'Example Prompts', and 'Integration with Kiro CLI' sections — these are either obvious to Claude or not actionable instructions.

Add explicit validation and dry-run steps before each destructive action (e.g., 'List volumes to delete → confirm with user → execute deletion'), rather than just mentioning safety in a separate section.

Move the checklist and best practices into a separate referenced file (e.g., CHECKLIST.md) to keep the main skill lean and focused on executable workflows.

Trim 'Best Practices' to only non-obvious, AWS-cost-specific guidance — items like 'document all actions' and 'calculate ROI' are generic advice Claude already knows.

Dimension	Reasoning	Score
Conciseness	Significant verbosity throughout. The 'When to Use This Skill' section, 'Core Capabilities' bullet list, 'Example Prompts' section, and 'Best Practices' all explain things Claude already knows or provide information that doesn't add actionable value. The 'Integration with Kiro CLI' section adds little. The checklist, while nice, is largely generic AWS knowledge. Much of this could be cut by 50%+ without losing utility.	1 / 3
Actionability	The AWS CLI commands are concrete, executable, and copy-paste ready with proper flags, JMESPath queries, and date calculations. Commands cover cost analysis, unused resource detection, and rightsizing analysis with real output formatting options.	3 / 3
Workflow Clarity	The 'Optimization Workflow' provides a clear 4-step sequence, and the Safety Notes mention verification before deletion. However, there are no explicit validation checkpoints or feedback loops for destructive operations like deleting EBS volumes or snapshots. For a skill involving deletion of cloud resources, the absence of validate-then-act patterns caps this at 2.	2 / 3
Progressive Disclosure	The content is organized into clear sections with headers, but it's monolithic — everything is inline in one file. The lengthy CLI command blocks, checklist, example prompts, and best practices could be split into referenced files. The 'Additional Resources' section links externally but there's no internal file decomposition.	2 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: boisenoise/skills-collections
Commit: f1697b6

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.