← ClaudeAtlas

eks-cost-intelligencelisted

Run a live EKS cluster cost efficiency assessment — analyze spending across 6 dimensions (compute efficiency, Spot/Graviton adoption, networking, storage, observability, idle resources), calculate a weighted 0-100 Cost Score, and generate a prioritized report with dollar-quantified findings and ready-to-apply remediation snippets. Use this skill when someone asks "how much am I wasting on EKS?", "run a cost audit on my cluster", "what's my biggest cost driver?", "analyze my cluster's cost efficiency", or needs dollar-denominated findings for a FinOps review — even if they don't say "cost intelligence" or "score". Combines live Cost Explorer data, CloudWatch utilization metrics, and Kubernetes resource analysis. Falls back to AWS CLI and kubectl when the EKS MCP server is unavailable. Distinct from eks-best-practices (static advisory guidance), eks-operation-review (operational health), and eks-recon (cluster discovery).
aws-samples/sample-apex-skills · ★ 37 · DevOps & Infrastructure · score 73
Install: claude install-skill aws-samples/sample-apex-skills
# EKS Cost Intelligence ## Overview This skill performs a live cost efficiency assessment of your EKS cluster. It connects via AWS CLI and kubectl, analyzes cost signals across 6 dimensions, calculates a weighted Cost Score (0–100), and produces a detailed report with dollar-quantified findings, prioritized recommendations, and pre-filled remediation snippets. This skill is focused on **live cost assessment** — answering the question: "Where is this cluster wasting money, and how much can I save?" ## When to Use **Activate when the user:** - Asks "how much am I wasting?" or "what's my biggest cost driver?" - Requests a cost audit, cost review, or spending assessment on a live cluster - Needs dollar-denominated findings to justify optimization work to leadership - Wants cost attribution by namespace, team, or workload - Is preparing a FinOps review or cost reduction initiative - Asks which workloads are over-provisioned relative to actual usage - Wants to know their cluster's cost efficiency score **Do NOT activate when the user:** - Asks general cost optimization best practices → use `eks-best-practices` (static advisory) - Asks "how should I design my cluster for cost efficiency?" → use `eks-best-practices` - Requests an operational review or health check → use `eks-operation-review` - Wants cluster discovery or reconnaissance → use `eks-recon` - Asks about upgrade readiness → use `eks-upgrade-check` - Asks to set up the EKS MCP server → use `eks-mcp-server` ### Sibli