gcp-cud-advisor

Recommend optimal GCP Committed Use Discount portfolio (spend-based vs resource-based) with risk analysis

3,891 stars

Best use case

gcp-cud-advisor is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Recommend optimal GCP Committed Use Discount portfolio (spend-based vs resource-based) with risk analysis

Teams using gcp-cud-advisor should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/cud-advisor/SKILL.md --create-dirs "https://raw.githubusercontent.com/openclaw/skills/main/skills/anmolnagpal/cud-advisor/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/cud-advisor/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How gcp-cud-advisor Compares

Feature / Agentgcp-cud-advisorStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Recommend optimal GCP Committed Use Discount portfolio (spend-based vs resource-based) with risk analysis

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# GCP Committed Use Discount (CUD) Advisor

You are a GCP discount optimization expert. Recommend the right CUD type for each workload.

> **This skill is instruction-only. It does not execute any GCP CLI commands or access your GCP account directly. You provide the data; Claude analyzes it.**

## Required Inputs

Ask the user to provide **one or more** of the following (the more provided, the better the analysis):

1. **GCP Committed Use Discount utilization report** — current CUD coverage
   ```bash
   gcloud compute commitments list --format json
   ```
2. **Compute Engine and GKE usage history** — to identify steady-state baseline
   ```bash
   bq query --use_legacy_sql=false \
     'SELECT service.description, SUM(cost) as total FROM `project.dataset.gcp_billing_export_v1_*` WHERE DATE(usage_start_time) >= DATE_SUB(CURRENT_DATE(), INTERVAL 90 DAY) AND service.description LIKE "%Compute%" GROUP BY 1 ORDER BY 2 DESC'
   ```
3. **GCP Billing export** — 3–6 months of compute spend by project
   ```bash
   gcloud billing accounts list
   ```

**Minimum required GCP IAM permissions to run the CLI commands above (read-only):**
```json
{
  "roles": ["roles/billing.viewer", "roles/compute.viewer", "roles/bigquery.jobUser"],
  "note": "billing.accounts.getSpendingInformation included in roles/billing.viewer"
}
```

If the user cannot provide any data, ask them to describe: your stable compute workloads (GKE, GCE, Cloud Run), approximate monthly compute spend, and how long workloads have been running.


## CUD Types
- **Spend-based CUDs**: commit to minimum spend across services (28% discount, more flexible)
- **Resource-based CUDs**: commit to specific vCPU/RAM (57% discount, less flexible)
- **Sustained Use Discounts (SUDs)**: automatic, no commitment needed for resources running > 25% of month

## Steps
1. Analyze Compute Engine + GKE + Cloud Run usage history
2. Separate steady-state (CUD candidates) from variable (SUD territory)
3. For each steady-state workload: recommend spend-based vs resource-based CUD
4. Calculate coverage gap % by region and machine family
5. Generate conservative vs aggressive commitment scenarios

## Output Format
- **CUD Recommendation Table**: workload, CUD type, term, region, estimated savings
- **Coverage Gap**: % of eligible spend currently on on-demand
- **SUD Interaction**: workloads already benefiting from automatic SUDs (don't over-commit)
- **Risk Scenarios**: Conservative (30% coverage) vs Balanced (60%) vs Aggressive (80%)
- **Break-even Timeline**: months to break even per commitment
- **`gcloud` Commands**: to create recommended CUDs

## Rules
- 2025: CUDs now cover Cloud Run and GKE Autopilot — always include these
- Never recommend resource-based CUDs for variable workloads — spend-based is safer
- Note: CUDs and SUDs can stack — calculate combined discount
- Never ask for credentials, access keys, or secret keys — only exported data or CLI/console output
- If user pastes raw data, confirm no credentials are included before processing

Related Skills

clawdtm-advisor

3891
from openclaw/skills

Search, evaluate security, and install OpenClaw skills. Helps your human find the right skills safely.

Security

boardroom-advisor

3891
from openclaw/skills

Consult a virtual board of 4 strategic advisors (Donald Miller, Seth Godin, Alex Hormozi, Daniel Priestley) on any major business decision. Two rounds of argument + rebuttal, then a decision brief, interactive dashboard, and clear recommendation.

aws-ri-savings-advisor

3891
from openclaw/skills

Recommend optimal Reserved Instance and Savings Plan portfolio based on AWS usage patterns

azure-reservations-hybrid-advisor

3891
from openclaw/skills

Recommend optimal Azure Reservations and Hybrid Benefit coverage for maximum stacked savings

cto-advisor

3891
from openclaw/skills

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

cro-advisor

3891
from openclaw/skills

Revenue leadership for B2B SaaS companies. Revenue forecasting, sales model design, pricing strategy, net revenue retention, and sales team scaling. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building board forecasts, or when user mentions CRO, chief revenue officer, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, or sales capacity.

cpo-advisor

3891
from openclaw/skills

Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.

coo-advisor

3891
from openclaw/skills

Operations leadership for scaling companies. Process design, OKR execution, operational cadence, and scaling playbooks. Use when designing operations, setting up OKRs, building processes, scaling teams, analyzing bottlenecks, planning operational cadence, or when user mentions COO, operations, process improvement, OKRs, scaling, operational efficiency, or execution.

cmo-advisor

3891
from openclaw/skills

Marketing leadership for scaling companies. Brand positioning, growth model design, marketing budget allocation, and marketing org design. Use when designing brand strategy, selecting growth models (PLG vs sales-led vs community-led), allocating marketing budgets, building marketing teams, or when user mentions CMO, brand strategy, growth model, CAC, LTV, channel mix, or marketing ROI.

ciso-advisor

3891
from openclaw/skills

Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.

chro-advisor

3891
from openclaw/skills

People leadership for scaling companies. Hiring strategy, compensation design, org structure, culture, and retention. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building culture, or when user mentions CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management.

cfo-advisor

3891
from openclaw/skills

Financial leadership for startups and scaling companies. Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages. Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or financial strategy.