aws-cost-cleanup

Automated cleanup of unused AWS resources to reduce costs

Quality

38%

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/antigravity-awesome-skills-claude/skills/aws-cost-cleanup/SKILL.md

Quality

Content

55%Scale 1-3

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

The skill provides excellent actionable content with executable scripts and a well-structured cleanup workflow with proper safety checkpoints. However, it is significantly bloated with redundant sections (Best Practices repeating Safety Checklist, Example Prompts, Kiro CLI Integration, boilerplate Limitations), unnecessary explanations, and would benefit greatly from splitting into multiple files with a concise overview in SKILL.md.

Suggestions

Reduce the SKILL.md to a concise overview (~50-80 lines) covering the cleanup targets, workflow phases, and safety checklist, then move scripts into separate bundle files (e.g., scripts/cleanup-ebs.sh, scripts/calculate-savings.py, scripts/cleanup-lambda.py)

Remove the 'Example Prompts', 'Kiro CLI Integration', 'When to Use This Skill', and 'Additional Resources' sections entirely as they add no actionable value for Claude

Consolidate 'Best Practices', 'Risk Mitigation', and 'Safety Checklist' into a single concise safety section to eliminate redundancy

Add clear navigation references to bundle files (e.g., '**EBS cleanup script**: See [scripts/cleanup-ebs.sh](scripts/cleanup-ebs.sh)') for progressive disclosure

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 no actionable value. The 'Best Practices' and 'Risk Mitigation' sections largely repeat the Safety Checklist. Claude already knows AWS CLI and boto3 patterns.	1 / 3
Actionability	The skill provides fully executable bash scripts and Python code that are copy-paste ready. The cleanup scripts, Lambda function, S3 lifecycle policy, cost calculator, and CloudWatch alarm commands are all concrete and specific with real AWS CLI commands and boto3 code.	3 / 3
Workflow Clarity	The Cleanup Workflow section provides a clear 4-phase sequence (Discovery → Validation → Execution → Verification) with explicit validation checkpoints. The Safety Checklist reinforces this with dry-run-first approach, dependency checking, and rollback planning. The scripts themselves default to dry-run mode with commented-out destructive commands.	3 / 3
Progressive Disclosure	The content is a monolithic wall of text with no bundle files to reference. Multiple sections (Cost Impact Calculator, Lambda function, S3 lifecycle, Organizations integration, Monitoring) could be split into separate files. There are no internal cross-references or navigation aids despite the document's length.	1 / 3
	Total	8 / 12 Passed

Description

22%Scale 1-3

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. It identifies the domain (AWS resource cleanup) but fails to enumerate concrete capabilities or provide a 'Use when...' clause, making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

List specific concrete actions and resource types, e.g., 'Identifies and removes unused EC2 instances, unattached EBS volumes, 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 bills, finding idle or unused cloud resources, or cleaning up their AWS account.'

Include common keyword variations users might say, such as 'cloud waste', 'cost optimization', 'idle instances', '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 types of resources (EC2 instances, EBS volumes, S3 buckets, etc.) or what concrete actions are performed (terminate, delete, tag, report).	1 / 3
Completeness	It loosely describes 'what' (cleanup unused AWS resources) but there is no explicit 'when' clause or trigger guidance. The rubric states a missing 'Use when...' clause should cap completeness at 2, and the 'what' itself is also weak, so this scores a 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, Lambda, S3) and common variations like 'cloud waste', 'idle resources', or 'cost optimization'.	2 / 3
Distinctiveness Conflict Risk	The AWS cost/cleanup domain is somewhat specific and wouldn't conflict with most skills, but 'unused AWS resources' is broad enough that it could overlap with AWS monitoring, AWS infrastructure management, or general cost optimization skills.	2 / 3
	Total	6 / 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: popey/claude-code-skills
Path: plugins/antigravity-awesome-skills-claude/skills/aws-cost-cleanup/SKILL.md
Commit: a5a6601

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