Skip to content
TrustedSkillsbeta
Back to all skills

Aws Cost Cleanup

Checked
sickn33·vlatest·cloud·MIT

Provides AWS guidance and assistance for deploying and managing cloud infrastructure.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sickn33/agentic-awesome-skills --skill aws-cost-cleanup -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

sickn33

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned sickn33/antigravity-awesome-skills at 5a4cdd9df8.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
5a4cdd9df8
Manifest
skills/aws-cost-cleanup/SKILL.md
Scanned
1 file, 298 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The aws-cost-cleanup skill helps identify and remove unused or underutilized AWS resources to reduce cloud spending. It can analyze resource utilization data, pinpoint idle instances, old snapshots, and other cost drivers, then automate the deletion of these resources based on defined policies. This allows for proactive management of AWS costs and prevents unnecessary expenses.

When to use it

  • Monthly Cost Review: Use this skill at the end of each month to identify potential areas for cost optimization before billing cycles close.
  • Project Completion: After a project is finished, leverage the skill to automatically clean up associated resources that are no longer needed.
  • Dev/Test Environment Management: Regularly use it to ensure development and testing environments aren't accumulating unused resources and incurring unnecessary charges.
  • Identifying Idle Resources: Run this skill periodically to proactively identify EC2 instances or EBS volumes with low utilization metrics.

Key capabilities

  • Resource Utilization Analysis
  • Automated Resource Deletion
  • Policy-Based Cleanup
  • Identification of Idle Instances
  • Old Snapshot Removal

Example prompts

  • "Find and delete all unused EBS snapshots older than 30 days."
  • "Analyze EC2 instance utilization over the last week and recommend cost optimization actions."
  • "Remove any EC2 instances that have been idle for more than a day."

Tips & gotchas

This skill requires appropriate AWS IAM permissions to access resource data and perform deletion operations. Always review proposed cleanup actions before execution, especially in production environments, to avoid accidental data loss.