aws-cost-cleanup

Automated cleanup of unused AWS resources to reduce costs

Quality

32%

Does it follow best practices?

Impact

Pending

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 brief and vague, lacking specific actions, resource types, and explicit trigger guidance. While it identifies the domain (AWS cost reduction), it 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

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about reducing AWS costs, cleaning up unused resources, or identifying idle EC2 instances, EBS volumes, or snapshots.'

List specific concrete actions and resource types, e.g., 'Identifies and removes unused EC2 instances, unattached EBS volumes, old snapshots, idle Elastic IPs, and orphaned security groups.'

Include natural trigger terms users would say, such as 'AWS bill', 'cost optimization', 'unused instances', 'cloud waste', 'idle resources'.

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, snapshots, etc.) or what concrete actions are performed (terminate, delete, deregister, etc.).	1 / 3
Completeness	It provides a weak 'what' (automated cleanup of unused AWS resources) but completely lacks a 'when' clause — there is no explicit trigger guidance for when Claude should select this skill.	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, S3, EBS, snapshots, Lambda) and action variations (e.g., 'delete', 'terminate', 'cost optimization').	2 / 3
Distinctiveness Conflict Risk	The AWS cost reduction focus provides some distinctiveness, but 'cleanup of unused resources' could overlap with general AWS management skills, infrastructure-as-code skills, or cost 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 excels at providing concrete, executable code examples for AWS resource cleanup, but suffers significantly from bloat and poor organization. It tries to cover too many topics in a single file (cleanup scripts, Lambda automation, cost calculation, monitoring, multi-account management) without progressive disclosure. The safety workflow is present but could be more tightly integrated into the actual scripts rather than being a separate section.

Suggestions

Reduce the file to core cleanup patterns (EBS, snapshots, EIPs) and move Lambda automation, S3 lifecycle, monitoring, and Organizations integration into separate referenced files.

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

Integrate validation directly into scripts (e.g., add a --dry-run flag or confirmation prompt) rather than relying on commented-out lines, and add explicit 'stop if X' checkpoints.

Trim best practices and risk mitigation to a compact checklist rather than prose explanations of things Claude already understands.

Dimension	Reasoning	Score
Conciseness	The skill is excessively verbose at ~250+ lines. It includes sections Claude doesn't need (example prompts, Kiro CLI integration, additional resources links, explanations of what each resource type is). The 'When to Use This Skill' section restates the title. Best practices and risk mitigation sections contain generic advice Claude already knows.	1 / 3
Actionability	The skill provides fully executable bash scripts and Python code that are copy-paste ready. 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 has a clear 4-phase sequence (Discovery → Validation → Execution → Verification) and the safety checklist is good. However, the validation checkpoints within the scripts themselves are weak—the dry-run approach is just commenting/uncommenting lines rather than having explicit validation gates. For destructive batch operations like deleting volumes and snapshots, the feedback loops are implicit rather than explicit.	2 / 3
Progressive Disclosure	This is a monolithic wall of content with everything inline—cleanup scripts, Lambda code, cost calculator, lifecycle policies, monitoring setup, org-wide scanning, and Kiro CLI integration all in one file. Much of this content (Lambda function, S3 lifecycle, CloudWatch alarms, Organizations integration) should be split into separate referenced files.	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: 431bfad

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