aws-cost-cleanup

Automated cleanup of unused AWS resources to reduce costs

Quality

62%

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

Quality

Content

63%Weight 40%Scale 1-5

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

The content is highly actionable with executable scripts and a well-sequenced, validation-aware workflow, but it is a long monolithic file with redundant safety sections and no progressive disclosure into bundle files.

Suggestions

Move the full scripts (EBS, snapshots, EIP, Lambda, cost calculator) into a scripts/ directory and reference them from SKILL.md to improve progressive disclosure and reduce inline length.

Consolidate the overlapping Safety Checklist, Best Practices, and Risk Mitigation sections into one to remove redundancy and tighten conciseness.

Make the workflow's error-recovery loop explicit (e.g. 'If dry-run review flags dependencies, exclude the resource and re-run') to reach the top workflow-clarity anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code with no concept-explaining fluff, but it carries redundancy: 'When to Use This Skill' restates the description and the Safety Checklist, Best Practices, and Risk Mitigation sections overlap.	3 / 5
Actionability	It provides full, copy-paste bash and python scripts covering the common cleanup targets, but placeholders like 'my-bucket' and commented-out execution lines are minor gaps keeping it from a 5.	4 / 5
Workflow Clarity	A clear 4-phase Discovery, Validation, dry-run Execution, and Verification sequence with a safety checklist satisfies the destructive-operation validation requirement, but the error-recovery feedback loop is implied rather than explicit.	4 / 5
Progressive Disclosure	Section headers are clear, but ~300 lines of full scripts are inlined in a single file with no bundle references; content that belongs in separate scripts/ files is inline, matching anchor 3.	3 / 5
	Total	14 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 concise and names a clear, distinct niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness, and its single action verb ('cleanup') keeps specificity modest.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when cleaning up unused AWS resources, reducing AWS spend, or eliminating wasted EBS volumes, snapshots, and Elastic IPs.'

Broaden trigger terms with natural synonyms users say ('waste', 'spend', 'idle resources', 'orphaned') to improve trigger matching.

List 2-3 concrete actions (e.g. 'identify, dry-run, and remove unused EBS volumes, snapshots, and Elastic IPs') to lift specificity above a single generic verb.

Dimension	Reasoning	Score
Specificity	Names the domain ('unused AWS resources') and a couple of actions ('cleanup', 'reduce costs') but is not comprehensive, matching anchor 3; it is more than the bare anchor-2 example yet lacks the multiple concrete actions needed for a 4.	3 / 5
Completeness	It has a clear 'what' (cleanup of unused AWS resources to reduce costs) but no 'Use when...' trigger clause, so completeness is capped at 3 per the judging guideline.	3 / 5
Trigger Term Quality	Includes natural phrases a user would say ('AWS', 'cleanup', 'unused resources', 'reduce costs') with good coverage, though a few synonyms like 'waste', 'spend', or 'idle' are missing.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (AWS cost/resource cleanup) with minimal conflict risk, though there is minor overlap potential with general AWS management or tagging skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Path: skills/antigravity-aws-cost-cleanup/SKILL.md
Commit: 19c310e

Reviewed: about 18 hours 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.