Skip to content
TrustedSkillsbeta
Back to all skills

Aws Cost Cleanup

Checked
aaaaqwq·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 aaaaqwq/agi-super-team --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

aaaaqwq

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 aaaaqwq/claude-code-skills at 331ecd3c1d.

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

Commit
331ecd3c1d
Manifest
skills/aws-cost-cleanup/SKILL.md
Scanned
1 file, 292 lines
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

This skill helps identify and remove unused or underutilized AWS resources to reduce cloud spending. It can analyze cost data, pinpoint idle instances, old snapshots, and other potential waste, then generate cleanup plans or execute automated removal actions. The goal is to optimize your AWS environment for both performance and cost efficiency.

When to use it

  • Unexpectedly high AWS bills: Use the skill to investigate spikes in spending and identify the root causes.
  • Project completion/termination: Automatically clean up resources associated with a finished project to avoid ongoing costs.
  • Regular cost optimization reviews: Schedule periodic scans to proactively identify and eliminate unnecessary expenses.
  • Dev/Test environment cleanup: Ensure development and testing environments are properly cleaned after use, preventing resource accumulation.

Key capabilities

  • Cost data analysis
  • Identification of idle resources (instances, snapshots)
  • Cleanup plan generation
  • Automated resource removal

Example prompts

  • "Find all unused EBS volumes in the us-east-1 region."
  • "Generate a cleanup plan for EC2 instances that haven't been accessed in 30 days."
  • "Delete any snapshots older than 7 days in my account."

Tips & gotchas

  • Requires appropriate AWS credentials with sufficient permissions to access and modify resources.
  • Review generated cleanup plans carefully before execution to avoid accidental data loss.