aws-cost-cleanup

Automated cleanup of unused AWS resources to reduce costs

1.02x

Quality

56%

Does it follow best practices?

Impact

88%

1.02x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/aws-cost-cleanup/SKILL.md

The canonical home for this skill is aws-cost-cleanup in boisenoise/skills-collections

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 action-rich with executable AWS CLI/Python examples and a well-sequenced, validation-aware cleanup workflow. Its main weaknesses are length/redundancy and a monolithic inline structure that would benefit from splitting scripts into bundle files.

Suggestions

Move the standalone scripts (cleanup-unused-ebs.sh, cleanup-old-snapshots.sh, release-unused-eips.sh, calculate-savings.py, the Lambda) into a scripts/ directory and reference them from SKILL.md to improve progressive disclosure.

De-duplicate the volume-scan logic shared between calculate-savings.py and the Lambda handler, and reconcile the Lambda's direct-delete behavior with the documented dry-run-first workflow.

Trim overlapping sections (e.g. 'Best Practices' vs 'Safety Checklist' vs 'Risk Mitigation') to reduce token cost.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows and leads with code, but at ~300 lines it carries redundancy (the Lambda function duplicates the savings-calculator logic and several sections overlap), fitting 'mostly efficient but could be tightened' rather than 4.	3 / 5
Actionability	Multiple concrete, mostly-executable bash/python/AWS-CLI snippets and a lifecycle-policy JSON give copy-paste-ready guidance, with only minor placeholders like 'my-bucket' keeping it from a 5.	4 / 5
Workflow Clarity	A destructive/batch skill with a 4-phase workflow (Discovery, Validation, Execution, Verification), dry-run-first execution, and a safety checklist provides clear sequencing with most checkpoints present; minor gaps (the Lambda example deletes without dry-run) keep it below 5.	4 / 5
Progressive Disclosure	There are no bundle files and all content is inlined with section headers; since the skill exceeds 50 lines and inlines full scripts that belong in a scripts/ directory, it fits 'some structure but content that should be separate is inline' rather than 4.	3 / 5
	Total	14 / 20 Passed

Description

48%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 clearly states what the skill does but is light on concrete actions and entirely lacks an explicit 'when to use' trigger clause, capping completeness at 3. It is fairly distinctive within the AWS niche.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when reducing AWS costs by removing unattached EBS volumes, old snapshots, unused Elastic IPs, and stopped instances.'

Replace the generic verb 'cleanup' with 2-3 specific actions (delete, release, archive) to lift specificity.

Include common synonyms and resource types (delete/remove, EBS/EIP/snapshots, .json lifecycle) for broader trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Automated cleanup of unused AWS resources' names the domain but the action 'cleanup' is generic, with no concrete actions (e.g. delete volumes, release EIPs) listed, matching the 'names the domain but actions are minimal or generic' anchor rather than 3 which requires named concrete actions.	2 / 5
Completeness	There is a clear 'what' (automated cleanup of unused AWS resources to reduce costs) but no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'cleanup', 'unused AWS resources', and 'reduce costs' are reasonably natural terms a user might say, but common synonyms (delete/remove/waste) and specific resource types are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The 'unused AWS resources' + 'cost' framing carves a mostly-distinct niche with only minor overlap risk against general AWS management skills, fitting the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	12 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/aws-cost-cleanup/SKILL.md
Commit: debb2ec

Reviewed: 1 day 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.