← Back to Skills Marketplace
anmolnagpal

Idle Resource Detector

by Anmol Nagpal · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
299
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install idle-resource-detector
Description
Detect AWS idle and zombie resources consuming cost with zero meaningful utilization
README (SKILL.md)

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 (\x3C 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
Usage Guidance
This skill's instructions clearly rely on the AWS CLI and live AWS credentials, but the package metadata doesn't declare those requirements — that's a warning sign. Before installing or running it: (1) Verify where the agent will obtain AWS credentials (environment, ~/.aws, instance profile) and avoid giving high-privilege keys; prefer a read-only or least-privilege role. (2) Require an explicit confirmation flag and human review before any delete command is executed; test the skill in a non-production account first. (3) Ask the publisher to update metadata to list required binaries (aws), required env vars or config paths, and to document the exact IAM permissions needed (read-only vs. deletion). (4) If you cannot confirm the confirmation enforcement or credential handling, do not run this against production accounts or keys. Absence of code/scan findings is expected for an instruction-only skill and does not imply safety.
Capability Analysis
Type: OpenClaw Skill Name: idle-resource-detector Version: 1.0.0 The skill bundle defines an AWS idle resource detector. The `_meta.json` contains standard metadata. The `SKILL.md` instructs the AI agent to identify idle AWS resources and generate AWS CLI cleanup commands. While the agent is enabled to use `bash` and generate commands, this is consistent with its stated purpose of providing cleanup actions. The instructions also include safety rules like requiring confirmation flags for deletion and flagging critical resources. There is no evidence of malicious intent, data exfiltration, unauthorized execution, or prompt injection designed to subvert the agent for harmful purposes within the skill bundle itself.
Capability Assessment
Purpose & Capability
The skill's stated purpose is to scan AWS resources and produce AWS CLI cleanup commands, but the registry metadata declares no required binaries (aws CLI), no environment variables, and no config paths. To perform its task it legitimately needs AWS CLI access and AWS credentials/role — these are missing from the declared requirements.
Instruction Scope
SKILL.md explicitly requires inclusion of AWS CLI commands and step-by-step cleanup actions and lists many resource types to inspect. That implies the agent will read AWS account state (via CLI/API) and may present deletion commands. The document does state 'Never suggest deleting resources without a confirmation flag' and to flag prod/critical names, but it gives broad discretion to run discovery and produce potentially destructive commands without specifying how credentials are obtained or how the confirmation flow is enforced.
Install Mechanism
Instruction-only skill with no install spec poses low installation risk (no archives or external code downloads).
Credentials
No environment variables or primary credential are declared, yet the skill needs AWS credentials (AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY or instance/profile credentials) and the aws CLI binary. This mismatch could lead the agent to use existing host credentials (e.g., ~/.aws, environment, or instance profile) without explicit user awareness. Required privileges (read-only vs. delete) are not specified.
Persistence & Privilege
always:false and no claims of modifying other skills or system-wide settings. The skill does not request permanent presence or elevated platform privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install idle-resource-detector
  3. After installation, invoke the skill by name or use /idle-resource-detector
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of AWS Idle & Zombie Resource Detector. - Detects various idle AWS resources, including stopped EC2s with attached EBS, unattached EBS volumes, unused Elastic IPs, idle load balancers, nearly empty S3 buckets, idle RDS, old orphaned snapshots, and unused NAT Gateways. - Provides a clear waste summary and estimated monthly waste. - Outputs a detailed resource table (ID, type, region, cost, last active). - Ranks resources by cleanup priority (High/Medium/Low) based on cost impact. - Supplies step-by-step runbooks and AWS CLI cleanup commands. - Flags critical resources and enforces confirmation requirements for safe deletions. - Calculates and displays estimated annual savings for identified idle resources.
Metadata
Slug idle-resource-detector
Version 1.0.0
License
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Idle Resource Detector?

Detect AWS idle and zombie resources consuming cost with zero meaningful utilization. It is an AI Agent Skill for Claude Code / OpenClaw, with 299 downloads so far.

How do I install Idle Resource Detector?

Run "/install idle-resource-detector" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Idle Resource Detector free?

Yes, Idle Resource Detector is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Idle Resource Detector support?

Idle Resource Detector is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Idle Resource Detector?

It is built and maintained by Anmol Nagpal (@anmolnagpal); the current version is v1.0.0.

💬 Comments