agentleFS
jpantsjohajpantsjoha/googlecloud-plugin/skills/vertex-ai/SKILL.md

vertex-ai

Skill4 starsChanged 4 months agoMITView on GitHub

Build and deploy ML models and generative AI workloads — models, prompts, tuning and endpoints — on Vertex AI. Covers Model Garden, the Gemini API, custom training, endpoint deployment, and IAM. Warns before deploying endpoints (billable). Integrates with Vertex AI MCP server. Use when the user mentions: Gemini on GCP, vertex endpoint, generative AI GCP, vertex training, PaLM, vertex AI pipeline. Use this for models, training and endpoints; use agent-architect instead for anything agentic — Agent Builder, ADK, Agent Runtime, A2A, AP2 and multi-agent topologies all belong there, not here.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use roles/aiplatform.user for inference.

    line 64

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Vertex AI

Unified ML platform for training, deploying, and serving models — including Gemini, generative AI, and custom models.

Naming currency: the platform was renamed to the Gemini Enterprise Agent Platform (GEAP) at Next '26 (2026-04-22). The rebrand is branding-only — vertex-ai persists in gcloud groups, SDK imports, API hostnames, Terraform resources, and doc URLs, so this skill keeps them. For agentic system design (ADK, Agent Runtime, multi-agent, MCP/A2A/AP2, agent evaluation), route to agent-architect; this skill covers platform/model mechanics.

Key Products

ProductUse
Gemini API on VertexProduction-grade Gemini access with data governance
Model GardenBrowse and deploy 150+ models (Gemini, Llama, etc.)
Custom TrainingTrain on managed infrastructure (GPUs/TPUs)
Vertex AI EndpointsServe predictions from deployed models
Agent BuilderBuild conversational agents on Vertex
Vertex AI PipelinesOrchestrate ML workflows (Kubeflow Pipelines)

Core Patterns

Call Gemini via Vertex (Python)

import vertexai
from vertexai.generative_models import GenerativeModel

vertexai.init(project="PROJECT_ID", location="us-central1")
model = GenerativeModel("gemini-2.0-flash-001")
response = model.generate_content("Explain Cloud Run in one sentence.")
print(response.text)

Deploy an endpoint (billable — confirm first)

# Billable: endpoints charge per node-hour when deployed
gcloud ai endpoints create \
  --display-name=ENDPOINT_NAME \
  --region=REGION \
  --project=PROJECT_ID

Grant Vertex AI access (least-privilege)

gcloud projects add-iam-policy-binding PROJECT_ID \
  --member="serviceAccount:SA@PROJECT.iam.gserviceaccount.com" \
  --role="roles/aiplatform.user"

Safety Rules

  • Endpoints incur cost even when idle — undeploy when not needed
  • Use roles/aiplatform.user for inference; roles/aiplatform.admin only for platform admins
  • Cost warning: GPUs and TPUs are expensive — confirm instance type and count before training

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.