cost-optimization-cloud
Cost Optimization Cloud
Overview
Use this skill to produce actionable cloud cost reductions that preserve service quality and operational safety.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Inputs To Gather
- Cost breakdown by service/account/environment/tag.
- Utilization telemetry (CPU, memory, I/O, request profile, idle windows).
- Reliability and performance guardrails (SLO, latency, availability).
- Contractual/compliance constraints and migration limits.
Deliverables
- Prioritized optimization backlog with savings estimate and confidence.
- Risk-assessed rollout sequence.
- Verification plan for savings and regression detection.
- Reversal plan for harmful optimizations.
Optimization Decision Buckets
waste removal: idle resources, overprovisioned instances, orphaned storage.efficiency: rightsizing, autoscaling policy tuning, query/request optimization.pricing: reservations/savings plans, spot usage where safe.architecture: storage tiering, cache strategy, async/off-peak processing.
Quick Example
- Observation: cluster CPU < 15% for 14 days, memory < 25%.
- Action: downsize node class + adjust autoscaling floor.
- Guardrail: p95 latency and error rate must remain within pre-change bounds.
- Rollback: revert size within one deployment window if guardrail breaches.
Quality Standard
- Every recommendation includes expected savings, confidence, and risk.
- Recommendations explicitly state SLO/compliance impact.
- Rollout uses low-blast-radius sequence.
- Post-change metrics and rollback triggers are pre-defined.
Workflow
- Identify top cost drivers with workload attribution.
- Generate candidate actions by decision bucket.
- Quantify savings, risk, and implementation effort.
- Sequence actions by ROI and operational safety.
- Execute incrementally with guardrail monitoring.
- Validate realized savings and capture lessons.
Failure Conditions
- Stop when savings action violates SLO/compliance constraints.
- Stop when cost attribution confidence is too low for safe action.
- Escalate when forecast variance remains unexplained after top-driver analysis.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9