aws-cost-cleanup

Automated cleanup of unused AWS resources to reduce costs

Quality

32%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Discovery

22%

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 too vague and lacks both specific actions and explicit trigger guidance. While it identifies the domain (AWS cost reduction via cleanup), it fails to enumerate concrete capabilities or provide a 'Use when...' clause, making it difficult for Claude to reliably select this skill over others.

Suggestions

List specific concrete actions and resource types, e.g., 'Identifies and removes unused EC2 instances, unattached EBS volumes, stale snapshots, idle Elastic IPs, and empty S3 buckets to reduce AWS costs.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about reducing AWS costs, finding unused cloud resources, cleaning up idle infrastructure, or optimizing AWS spending.'

Include common keyword variations users might say, such as 'cloud waste', 'cost optimization', 'idle resources', 'orphaned resources', or specific AWS service names.

Dimension	Reasoning	Score
Specificity	The description says 'cleanup of unused AWS resources' which is vague — it doesn't specify what kinds of resources (EC2 instances, EBS volumes, S3 buckets, etc.) or what concrete actions are performed (terminate, delete, snapshot, tag, report).	1 / 3
Completeness	It loosely describes 'what' (cleanup unused AWS resources) but has no explicit 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 2 per the rubric, and the 'what' is also weak, so it scores 1.	1 / 3
Trigger Term Quality	It includes 'AWS', 'unused', 'cleanup', and 'costs' which are somewhat natural terms a user might say, but it's missing specific resource types (e.g., EC2, EBS, S3, Lambda, snapshots) and common variations like 'cost optimization', 'idle resources', 'cloud waste'.	2 / 3
Distinctiveness Conflict Risk	The AWS cost/cleanup focus provides some distinctiveness, but 'unused AWS resources' is broad enough to potentially overlap with AWS infrastructure management, cost analysis, or cloud optimization skills.	2 / 3
	Total	6 / 12 Passed

Implementation

42%

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 cleanup scripts and a solid safety checklist, but it is far too verbose and monolithic. It tries to cover too many topics (EBS, snapshots, EIPs, S3 lifecycle, Lambda automation, multi-account, CloudWatch alarms, Kiro CLI) in a single file without progressive disclosure. Significant trimming and restructuring into separate files would dramatically improve its effectiveness.

Suggestions

Split the skill into a concise SKILL.md overview with references to separate files (e.g., SCRIPTS.md for cleanup scripts, LAMBDA.md for automation, COST-CALCULATOR.md for the Python savings tool).

Remove sections Claude doesn't need: 'When to Use This Skill', 'Example Prompts', 'Kiro CLI Integration', 'Additional Resources', and the generic 'Limitations' boilerplate.

Make the Cleanup Workflow section more concrete by linking each phase to specific scripts/commands (e.g., 'Run calculate-savings.py' instead of 'Generate cost impact report').

Consolidate 'Best Practices' and 'Risk Mitigation' into the Safety Checklist to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The skill is excessively verbose at ~250+ lines. It includes unnecessary sections like 'Example Prompts', 'Kiro CLI Integration', 'Additional Resources', 'When to Use This Skill', and 'Limitations' boilerplate that add little value. The 'Best Practices' and 'Risk Mitigation' sections overlap significantly. Much of this content (AWS CLI syntax, boto3 usage, general cleanup concepts) is knowledge Claude already possesses.	1 / 3
Actionability	The skill provides fully executable bash scripts and Python code that are copy-paste ready. The AWS CLI commands are specific with proper flags, queries, and filters. The Lambda function, lifecycle policy JSON, and cost calculator are all concrete and complete.	3 / 3
Workflow Clarity	The 'Cleanup Workflow' section lists four phases with reasonable sequencing, and the safety checklist is good. However, the workflow steps are described abstractly ('Run all describe commands', 'Verify resources are truly unused') rather than linking to specific scripts or commands. The feedback loop between dry-run and execution is implicit rather than explicit with validation checkpoints. For destructive batch operations like this, the lack of explicit validation commands within the workflow caps this at 2.	2 / 3
Progressive Disclosure	The entire skill is a monolithic wall of text with no references to supporting files. Content like the Lambda function, cost calculator, S3 lifecycle policy, and multi-account scripts could easily be split into separate referenced files. There are no bundle files, yet the content is far too long to be inline — it would benefit greatly from a hub-and-spoke structure.	1 / 3
	Total	7 / 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: 8ac11ab

Reviewed: 4 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.