AI Agents Marketplace
Showing 4 of 4 results
agent-platform-deploy
# Agent Platform Model Garden Deploy Skill This skill provides instructions for deploying Open Models from Agent Platform Model Garden to endpoints, and subsequently undeploying them to clean up resources. ## 1P Tuned Model Copy & Deployment If you need to copy a **1P (First-Party) Tuned Model** from a source project to a destination region or project and deploy it to a newly created endpoint, refer to the [1P Tuned Model Copy & Deployment Guide](references/copy_deploy_guide.md). ## Safety & Confirmation Ti
agent-platform-tuning
# Agent Platform Model Tuning ## Overview This skill provides procedural knowledge for fine-tuning Large Language Models (both Open Models and Gemini Models) using Agent Platform's tuning service. It covers the entire lifecycle from environment setup and data preparation to job configuration, monitoring, and deployment. ## Workflow Decision Tree 1. **Project & Region Verification Check**: Has the user provided the Google Cloud project and region? - **No** → **STOP tool execution immediately**. Do NOT run ve
agent-platform-migrate-from-ai-studio
# Migrating from Gemini API in AI Studio to Agent Platform Use this skill when you need to transition an application from the developer-centric Google AI Studio ecosystem (`generativelanguage.googleapis.com`) to the enterprise-grade Google Cloud Agent Platform (`aiplatform.googleapis.com`). -------------------------------------------------------------------------------- ## When to Invoke This Skill * You want to migrate an application from Google AI Studio to Agent Platform (formerly Vertex AI). * You have
code-testing-agent
# Code Testing Generation Skill An AI-powered skill that generates comprehensive, workable unit tests for any programming language using a coordinated multi-agent pipeline. ## Non-negotiable execution contract Classify scope **before editing**: - **Broad** (a project/package-wide suite, or multiple production files/modules): create `research.md` and `plan.md` in a resolved non-stageable `<TESTAGENT_DIR>` before implementation, then `status.md` there after the final test-quality review. When `code-testing-ge