Agent skill · google
compute-future-reservations
Evaluates future GPU and TPU reservation feasibility and calendar-mode booking options in Google Compute Engine (GCE). Use when planning future AI/ML training runs, checking reservation availability windows, verifying accelerator cluster topologies, or assessing future capacity lead times. Don't use for active on-demand reservations (use compute-on-demand-reservations), immediate Spot capacity queries (use compute-spot-capacity-advice), or Standard Future Reservations (--reservation-mode=DEFAULT).
What it needs
About 8k tokens when loaded.
What this skill does
Compute Engine Future Reservations & Calendar-Mode Feasibility The compute-future-reservations skill assesses future capacity availability and feasibility for high-demand AI/ML hardware (NVIDIA GPUs, H4D VMs, and Google Cloud TPUs). It enables infrastructure engineers to evaluate future reservation windows, match cluster topologies, and manage calendar-mode bookings. [!NOTE] Scope Boundary (Calendar Mode vs. Standard Future Reservations): This skill covers Calendar-Mode Future Reservations (--reservation-mode=CALENDAR, backed by Dynamic Workload Scheduler for up to 90 days on supported families such as a3, a4, h4d, and Cloud TPUs; for newly released machine series, verify Calendar Mode support dynamically via gcloud compute advice calendar-mode or the official Calendar Mode documentation). Do not apply Calendar-Mode flags (--reservation-mode=CALENDAR, --deployment-type=DENSE) to Standard Future Reservations (--reservation-mode=DEFAULT for general-purpose CPU families, a2/g2 GPUs, DRAFT planning workflows, or multi-month/CUD commitments). Usage Attribution MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution. --- Prerequisites, IAM & Billing Before querying calendar-mode advice or submitting future reservation requests, ensure the environment meets these requirements: 1. Project & Region Configuration: Prefer passing --project={projectid} and --region={region} (or --zone={zone}) directly on each command to avoid overwriting global workstation state, or obtain explicit user confirmation before setting defaults (e.g., us-central1): 2. Billing & API Enablement: Ensure the project has an active billing account attached and the Compute Engine API is enabled: 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills google/compute-future-reservations