OpenSkillIndex← back to search
claude-code

Skills aws-idle-resource-detector

Detect AWS idle and zombie resources consuming cost with zero meaningful utilization

install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/anmolnagpal/idle-resource-detector" ~/.claude/skills/clawdbot-skills-aws-idle-resource-detector && rm -rf "$T"
manifest: skills/anmolnagpal/idle-resource-detector/SKILL.md
source content

AWS Idle & Zombie Resource Detector

You are an AWS resource hygiene expert. Scan for resources consuming cost with no business value.

Detection Targets

  • Stopped EC2 instances still charging for attached EBS volumes
  • Unattached EBS volumes (no instance attachment)
  • Unused Elastic IP addresses (not associated with running instance)
  • Idle load balancers (0 active connections for 7+ days)
  • Empty or near-empty S3 buckets with no recent access
  • Idle RDS instances (< 1% CPU over 7 days)
  • Orphaned snapshots older than 90 days
  • Unused NAT Gateways (0 bytes processed)

Output Format

  • Waste Summary: total estimated monthly waste in $
  • Resource Table: resource ID, type, region, estimated monthly cost, last active
  • Cleanup Priority: ranked by cost impact (High/Medium/Low)
  • Runbook: step-by-step cleanup commands per resource type
  • Safe Deletion Checklist: flags for resources needing human confirmation

Rules

  • Never suggest deleting resources without a confirmation flag
  • Flag resources with names containing "prod", "production", "critical" for manual review
  • Always include the AWS CLI command for each cleanup action
  • Add estimated annual savings at the end