aws-cost-cleanup

Automated cleanup of unused AWS resources to reduce costs

1.02x

Quality

55%

Does it follow best practices?

Impact

88%

1.02x

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-cleanup/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 resource cleanup) but lacks the specificity and completeness needed for reliable skill selection. It fails to provide explicit trigger conditions and doesn't enumerate the specific cleanup actions or AWS services covered, making it difficult for Claude to confidently choose this skill over similar ones.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about AWS cost reduction, cleaning up unused cloud resources, or mentions idle EC2 instances, unattached volumes, or unused Elastic IPs'

List specific concrete actions such as 'Identifies and terminates idle EC2 instances, deletes unattached EBS volumes, removes unused Elastic IPs, cleans up old snapshots'

Include natural trigger terms users would say: 'cloud waste', 'AWS bill', 'unused instances', 'cost optimization', specific service names like 'EC2', 'S3', 'RDS'

Dimension	Reasoning	Score
Specificity	Names the domain (AWS resources) and a general action (cleanup of unused resources), but doesn't list specific concrete actions like 'terminate idle EC2 instances, delete unattached EBS volumes, remove unused Elastic IPs'.	2 / 3
Completeness	Describes what it does (cleanup unused AWS resources) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes 'AWS', 'unused', 'cleanup', and 'costs' which are relevant keywords, but misses common variations like 'cloud waste', 'EC2', 'S3', 'cost optimization', 'idle resources', or specific AWS service names users might mention.	2 / 3
Distinctiveness Conflict Risk	The AWS focus provides some distinctiveness, but 'reduce costs' is generic and could overlap with other AWS cost management skills, billing analysis skills, or general cloud optimization tools.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

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

This is a strong, actionable skill with excellent executable code examples and a well-defined safety-first workflow. The dry-run pattern and safety checklist demonstrate good awareness of the destructive nature of cleanup operations. However, the document is somewhat verbose with sections that could be trimmed or externalized, and includes some generic AWS knowledge that Claude already possesses.

Suggestions

Remove or condense the 'Example Prompts' and 'Kiro CLI Integration' sections which add little actionable value

Move detailed scripts (Lambda function, cost calculator) to separate reference files and link from the main skill

Remove the 'When to Use This Skill' section as it merely restates the title and description

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary sections like 'Example Prompts' and 'Kiro CLI Integration' that don't add actionable value. The 'When to Use This Skill' section restates the title. Some best practices are generic AWS knowledge Claude already has.	2 / 3
Actionability	Excellent executable code throughout - bash scripts, Python scripts, and AWS CLI commands are all copy-paste ready. The dry-run pattern with commented actual execution lines is practical and safe. Lambda function and lifecycle policy JSON are complete and deployable.	3 / 3
Workflow Clarity	Clear 4-phase workflow (Discovery → Validation → Execution → Verification) with explicit checkpoints. Safety checklist provides validation gates. The dry-run-first pattern is consistently emphasized throughout scripts. Risk mitigation section categorizes actions appropriately.	3 / 3
Progressive Disclosure	Content is well-organized with clear headers, but the document is quite long (~300 lines) and could benefit from splitting detailed scripts into separate files. The 'Additional Resources' section links externally but internal content organization could be improved with references to separate detailed guides.	2 / 3
	Total	10 / 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: 5c5ae21

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.