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/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 highly actionable with executable code and a safety-aware phased workflow, but it is somewhat verbose with redundancy and inlines material that could be split into reference files. Validation is present so the destructive-operation cap does not bind.

Suggestions

Extract the full scripts into a scripts/ bundle and reference them from SKILL.md to reduce inlined redundancy and improve progressive disclosure.

Deduplicate the repeated describe-volumes available-filter logic and remove the tangential Kiro CLI section to tighten conciseness.

Add an explicit validate->fix->retry feedback loop in the Cleanup Workflow (e.g., 'If verification finds still-attached dependencies, re-check and re-run') to reach the top workflow anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly code and concrete lists without conceptual padding, but it repeats the same describe-volumes available-filter pattern across multiple blocks and includes tangential sections (Kiro CLI integration), so it is 'mostly efficient but could be tightened'.	3 / 5
Actionability	It provides concrete, mostly copy-paste-ready bash, boto3, lifecycle JSON, CloudWatch, and Lambda code covering common cases, with only minor gaps like the hardcoded 'my-bucket' and the Organizations loop that enumerates without deleting, matching 'mostly executable guidance; minor gaps'.	4 / 5
Workflow Clarity	A four-phase Cleanup Workflow (Discovery, Validation, Execution, Verification) plus a Safety Checklist gives a clear sequence with validation present, so the destructive-skill cap does not apply; it stops short of explicit validate->fix->retry feedback loops, matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist and the entire skill is one inlined file where multiple full scripts (bash, python, lifecycle policy, Lambda) that could be separate reference files are all embedded, matching 'some structure but content that should be separate is inline'.	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 is clear about its domain and goal but generic in its actions and lacks an explicit trigger clause, which caps completeness. It is reasonably distinct from other skills but would benefit from concrete action verbs and a 'Use when...' trigger.

Suggestions

List concrete actions (e.g., 'delete unattached EBS volumes, release unused Elastic IPs, expire old snapshots') instead of the generic 'cleanup'.

Add an explicit 'Use when...' clause, e.g., 'Use when reducing AWS spend or removing idle resources like unattached volumes and unused Elastic IPs.'

Include natural synonyms users say (spend, waste, billing, idle resources) to improve trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("unused AWS resources") and a single generic action ("Automated cleanup") plus the goal ("to reduce costs"), but lists no concrete actions like deleting EBS volumes or releasing Elastic IPs, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It gives a clear 'what' ("Automated cleanup of unused AWS resources to reduce costs") but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric cap completeness is held at 3 even though the 'when' is weakly implied.	3 / 5
Trigger Term Quality	It includes some natural keywords a user might say ("AWS", "cleanup", "unused resources", "costs") but misses common synonyms and variations like "waste", "spend", "billing", or specific service names, matching 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	"Cleanup of unused AWS resources to reduce costs" carves out a mostly distinct cost-optimization niche with minor overlap risk against other AWS infrastructure skills, matching 'mostly distinct; minor overlap risk with closely related skills'.	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/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.