Claude Code Cloud Usage Skill for Reviewing Idle Capacity
Compare billing categories with workload timing to identify which resources merit a closer utilization review.
中文Install in Claude Code
The offline exercise uses a synthetic billing summary and utilization table. Live data collection in the upstream skill requires an authenticated cloud CLI with read-only billing and monitoring access.
- Get the complete `plugins/devops/cloud-cost-optimizer/skills/optimizing-cloud-costs` directory from the pinned GitHub checkout.
- Copy it under the target project's `.claude/skills/`. Confirm `.claude/skills/optimizing-cloud-costs/SKILL.md`, open Claude Code at the project root, and call `/optimizing-cloud-costs`.
Example task
Two test instances average four percent CPU. One has a scheduled daily peak and the other remains nearly flat. Explain which needs review first and what context is missing.What to check
The report separates periodic usage from sustained low utilization and names the observation window and dependencies to verify.
Original SKILL.md on GitHub · Updated
Frequently asked question
Is a low average enough to call a resource idle?
Review the peaks, workload schedule and service role before drawing that conclusion.