waste-detection

Identify cloud waste in infrastructure-as-code configurations via static analysis.

8|4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/adrien-barret/claude-kit --skill waste-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: waste-detection
Source: https://github.com/adrien-barret/claude-kit/tree/main/project-template/.claude/skills/finops/waste-detection
Command: npx skills add https://github.com/adrien-barret/claude-kit --skill waste-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify waste in cloud infrastructure definitions and configurations by static analysis, enabling cost optimization without needing runtime usage data.

Core Features & Use Cases

  • Static waste detection: flags idle environments, unattached storage, orphaned snapshots, unused Elastic IPs, and over-provisioned dev/staging resources based on IaC patterns.
  • Structured reporting: provides a severity, waste type, confidence, and remediation guidance to help prioritize fixes.
  • Use Case: scan a Terraform or CloudFormation repo to surface resources that are likely waste and generate a remediation plan for the ops team.

Quick Start

Run the waste-detection analysis against your IaC repository to produce a waste report. Example: waste-detection /path/to/infra

Frequently Asked Questions about waste-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect cloud waste in Terraform or CloudFormation repositories without runtime data?

Static analysis of infrastructure-as-code configurations identifies potential cloud waste by flagging idle instances, unattached volumes, orphaned snapshots, and unused Elastic IPs in Terraform or CloudFormation definitions without requiring runtime usage data.

What types of cloud waste can static IaC analysis find in non-prod environments?

Static IaC analysis finds idle instances, unattached storage volumes, orphaned snapshots, unused Elastic IPs, and over-provisioned resources across development, staging, and production environments defined in your infrastructure code.

Can I scan my infrastructure-as-code to estimate monthly cloud cost waste?

Scanning infrastructure-as-code generates a structured report including waste type, severity, confidence, estimated monthly cost, and remediation guidance for each flagged resource to help prioritize cloud cost optimization efforts.

What's the best way to validate potential cloud waste flagged by static IaC analysis?

The best way to validate flagged cloud waste is to cross-reference the static analysis findings with runtime usage data from CloudWatch or Prometheus to confirm the resources are truly idle before taking remediation action.

Does IaC static waste detection work for over-provisioned resources in staging and development scenarios?

Static waste detection works for over-provisioned resources across staging and development scenarios by analyzing IaC patterns to flag potential waste, while recommending validation with CloudWatch or Prometheus data.

How do I generate a remediation plan for unattached volumes and orphaned snapshots in my IaC repository?

Running a static waste-detection analysis against your IaC repository produces a structured remediation plan that includes severity, confidence, estimated monthly cost, and specific guidance for unattached volumes and orphaned snapshots.