Guides the usage of Gemini API on Google Cloud Vertex AI with the Gen AI SDK. Use when the user asks about using Gemini in an enterprise environment or explicitly mentions Vertex AI. Covers SDK usage (Python, JS/TS, Go, Java, C#), capabilities like Live API, tools, multimedia generation, caching, and batch prediction.
Generates a LiveAPI client service class in the user's chosen programming language. Use when the user wants to build, scaffold, or integrate a client that connects to the Gemini LiveAPI websocket endpoint (Gemini Enterprise or non-Gemini Enterprise), handles session setup/resumption, bearer token refresh, and…
Evaluate and improve GenAI models and agents using the Google GenAI Evaluation SDK. Creates eval datasets (from session traces or synthetic generation), selects and configures metrics (RubricMetric, LLMMetric, CodeExecutionMetric), executes evals via client.evals.evaluate(), and analyzes results to suggest concrete…
Primary Router for Vertex AI skills. Use this skill when the user wants to work with Google Cloud Vertex AI (e.g., deploying models, running inference, or tuning models). This skill routes to vertex-deploy, vertex-inference, or vertex-tuning.
Skill "vertex-deploy" from GoogleCloudPlatform/vertex-ai-samples, covering vertex ai model garden deploy skill, 1. prerequisites, 2. discovering deployable models, 3. deploying a model and example: deploying gemma 3.
Skill "vertex-inference" from GoogleCloudPlatform/vertex-ai-samples, covering vertex ai genai inference skill, 1. authentication (critical), 2. gemini models, choosing the right sdk and installation.
Skill "open-model" from GoogleCloudPlatform/vertex-ai-samples, covering vertex ai open model tuning, workflow decision tree, phase 0: environment & iam setup {#phase-0}, 0.1 authentication & project context and 0.2 possible locations.
Guides the developer workflow for contributing to Race Condition. Use when setting up pre-commit hooks, running tests before a PR, understanding code style requirements, or preparing a contribution.
Guides deployment of Race Condition to a GCP project. Use when deploying to the cloud, setting up infrastructure with Terraform, or troubleshooting a deployment. This is for cloud deployment -- for local development, use the getting-started skill instead.
Explains the Race Condition architecture, the design decisions behind it, and where to read code first. Use when the developer asks how something works, wants a tour, or wants to understand the system before changing it.
Guides setup of the Race Condition project from clone to running simulation. Use when the developer wants to get the project running locally, install dependencies, configure GCP credentials, or troubleshoot startup issues.
You are helping a developer work with Race Condition, an open-source multi-agent marathon simulation built with Google ADK and Gemini. It was demonstrated at the Google Cloud Next '26 Developer Keynote.
Claude Code instructions for GoogleCloudPlatform/race-condition, covering race condition -- ai assistant instructions, quick orientation, project conventions and detailed task skills.
Use when the marathon plan needs non-spatial event parameters defined: theme, hydration-point logistics, crowd zones, start times, or expected participant counts. Triggered when the request describes the feel or operational logistics of the race rather than its physical route.
Use when the marathon plan needs a 26.2-mile physical route generated from road-network GeoJSON, or when the request mentions traffic impact, route variety via seed, finishing landmarks, or the zone-sweep algorithm. Triggered by route-planning or traffic-analysis language.
Use when the planning committee asks about marathon finances or requests a budget change. Triggered by mentions of budget, cost, spending, sponsorship, or any phrasing that implies modifying a financial allocation. Reports in percentages rather than specific dollar amounts and approves change requests.
Use when planning a marathon route that must reference real-world geography: looking up landmarks, businesses, or parks in a city, computing distances between points, or checking historical and forecasted weather for the race date and location. Triggered when the request mentions a real city, venue, or weather…
Use when the planning committee asks to change, increase, decrease, or modify a budget allocation in a security-restricted context. Triggered by any budget-modification phrasing. Refuses the change and directs the requester to an authorized administrator.