[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DPBXME47B8PMGHDJS75WZ":3,"skill-same:01M79DPBXME47B8PMGHDJS75WZ":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79DPBXME47B8PMGHDJS75WZ","gemini-agents-api",null,"Manages custom Agent resources on Gemini Enterprise Agent Platform. Use when the user wants to programmatically create, configure, list, update, or delete stateful, server-managed Agent resources (including mounting files, skills, and tools) before executing conversations.","hamzabellouch\u002Fagent-skills","hamzabellouch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237856042?v=4","01M79BRYW7XAMK3YDWQEMTWGWS","Hamza Bellouch","01M79BRYWXQV3JK2TGVTX8GN2A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FAI_Engineering_and_Platforms\u002FAgents_and_LLM_Platforms\u002Fgemini-agents-api\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gemini-agents-api\nmetadata:\n  category: AiAndMachineLearning\ndescription: Manages custom Agent resources on Gemini Enterprise Agent Platform. Use when the user wants to programmatically create, configure, list, update, or delete stateful, server-managed Agent resources (including mounting files, skills, and tools) before executing conversations.\n---\n\n# Gemini Enterprise Agent Platform - Managed Agents API Skill\n\nThis skill provides complete instructions, REST request endpoints, and JSON payload structures to programmatically manage **custom Agent resources** on the Gemini Enterprise Agent Platform (Agent Platform).\n\nThe **Managed Agents API** forms the **Control Plane** of the platform. It allows developers to provision, retrieve, update, and delete tailored, stateful agent containers equipped with system instructions, sandboxed files, custom skill registries, and local\u002Fremote tools.\n---\n\n## 1. Authentication & Setup\n\nAll REST requests to the Control Plane must include a Bearer token derived from Application Default Credentials (ADC), and target the production global endpoint.\n\n### 1. Setup Environment Variables\n\nBefore running requests, set up the required project variables and access token:\n\n```bash\nexport PROJECT_ID=\"your-project-id\"\nexport LOCATION=\"global\"\nexport ACCESS_TOKEN=$(gcloud auth print-access-token)\n```\n\n> [!IMPORTANT]\n> **API Location Support**:\n> The `LOCATION` environment variable must be set to a regional location where the Gemini Enterprise Agent Platform's **Managed Agents API** is actively supported (e.g., `global`, or other available regional endpoints).\n\n\n### 2. Endpoint URL\n\nThe production Agents Control Plane endpoint is:\n\n```http\nhttps:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F{PROJECT_ID}\u002Flocations\u002F{LOCATION}\u002Fagents\n```\n\n---\n\n## 2. Programmatic Agent Management (Control Plane CRUD)\n\n### 1. Create Agent (Long-Running Operation)\n\nTo create a new agent resource, issue a `POST` request with the custom configuration. You can mount remote files, folders, or skills directly from **Google Cloud Storage** buckets into the agent container's workspace. Creating an agent is a Long-Running Operation (LRO) that spawns an asynchronous job.\n\n*   **Method**: `POST`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents`\n\n#### Request Payload\n\n```bash\ncurl -X POST \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson; charset=utf-8\" \\\n  -d '{\n    \"id\": \"my-custom-agent\",\n    \"base_agent\": \"antigravity-preview-05-2026\",\n    \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n    \"system_instruction\": \"You are a helpful, domain-expert assistant.\",\n    \"tools\": [\n      {\"type\": \"code_execution\"},\n      {\"type\": \"filesystem\"},\n      {\"type\": \"google_search\"},\n      {\"type\": \"url_context\"}\n    ],\n    \"base_environment\": {\n      \"type\": \"remote\",\n      \"sources\": [\n        {\n          \"type\": \"gcs\",\n          \"source\": \"gs:\u002F\u002Fyour-agent-bucket-name\u002Fskills\",\n          \"target\": \"\u002F.agent\u002Fskills\"\n        }\n      ],\n      \"network\": {\n        \"allowlist\": [\n          { \"domain\": \"*\" }\n        ]\n      }\n    }\n  }'\n```\n\n#### LRO Operations Response\n\nSince agent provisioning takes a few moments, the endpoint immediately returns an operation tracking object:\n\n```json\n{\n  \"name\": \"projects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\",\n  \"metadata\": {\n    \"@type\": \"type.googleapis.com\u002Fgoogle.cloud.aiplatform.v1beta1.CreateAgentOperationMetadata\",\n    \"genericMetadata\": {\n      \"createTime\": \"2026-05-14T19:00:00.123456Z\",\n      \"updateTime\": \"2026-05-14T19:00:01.654321Z\"\n    }\n  }\n}\n```\n\n#### [Advanced] Mount Skill Registry Resources\n\nTo mount skills directly from the Skill Registry service instead of Cloud Storage, replace the Cloud Storage source item in the payload:\n\n```json\n\"sources\": [\n  {\n    \"type\": \"skill_registry\",\n    \"source\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fskills\u002Fmy-math-skill\u002Frevisions\u002F123456789012\",\n    \"target\": \"\u002F.agent\u002Fskills\"\n  }\n]\n```\n\n#### [Advanced] Configuring Model Context Protocol (MCP) Servers\n\nTo configure Third-Party MCP servers for an agent, add the server metadata directly under the `\"tools\"` parameter array inside the creation request. The platform securely routes tool execution requests to the external MCP server.\n\n> [!IMPORTANT]\n> **MCP Security Explanation**: When describing MCP tool configurations, you must explain that the platform securely routes tool requests to the specified MCP server and guarantees header confidentiality by only sending custom headers\u002Ftokens to that URL.\n\n```json\n\"tools\": [\n  {\n    \"type\": \"mcp\",\n    \"name\": \"my-mcp-server\",\n    \"url\": \"https:\u002F\u002Fmcp.yourcompany.com\u002Fapi\",\n    \"headers\": {\n      \"Authorization\": \"Bearer YOUR_MCP_AUTH_TOKEN\"\n    }\n  }\n]\n```\n\n*   **name**: A descriptive name for the MCP server.\n*   **url**: The endpoint URL of the external MCP server.\n*   **headers**: (Optional) Custom key-value pairs containing authentication tokens (e.g. API keys, bearer tokens) required to call the server. The platform guarantees that these headers are only sent to the specified MCP server URL.\n\n> [!TIP]\n> **Overriding MCP at Interaction Time (Data Plane)**:\n> You can dynamically override or supply MCP tools directly when creating a conversation interaction (Data Plane) by passing `\"type\": \"mcp_server\"` inside the `\"tools\"` payload of `interactions.create`. Refer to the Interactions API documentation for details.\n\n---\n\n### 2. Polling the LRO Status\n\nTo track the status of agent creation and obtain the final ready resource, poll the operation URL returned in the `name` field of the creation response.\n\n*   **Method**: `GET`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002F{OPERATION_NAME}`\n\n```bash\ncurl -X GET \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\"\n```\n\n#### In-Progress Response\n\n```json\n{\n  \"name\": \"projects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\",\n  \"metadata\": { ... }\n}\n```\n\n#### Finished Success Response\n\nOnce the container is ready, `\"done\": true` is set, and the completed `Agent` resource description resides inside `\"response\"`:\n\n```json\n{\n  \"name\": \"projects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\",\n  \"done\": true,\n  \"response\": {\n    \"@type\": \"type.googleapis.com\u002Fgoogle.cloud.aiplatform.v1beta1.Agent\",\n    \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n    \"base_agent\": \"antigravity-preview-05-2026\",\n    \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n    \"system_instruction\": \"You are a helpful, domain-expert assistant.\"\n  }\n}\n```\n\n---\n\n### 3. Get Agent\n\nRetrieve the configuration metadata, tools, and environment setup of an existing custom agent.\n\n*   **Method**: `GET`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\u002F{AGENT_ID}`\n\n```bash\ncurl -X GET \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\"\n```\n\n#### Response Example\nReturns the complete configured state of the custom Agent resource:\n\n```json\n{\n  \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n  \"base_agent\": \"antigravity-preview-05-2026\",\n  \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n  \"system_instruction\": \"You are a helpful, domain-expert assistant.\",\n  \"tools\": [\n    {\"type\": \"code_execution\"},\n    {\"type\": \"filesystem\"},\n    {\"type\": \"google_search\"},\n    {\"type\": \"url_context\"}\n  ],\n  \"base_environment\": {\n    \"type\": \"remote\",\n    \"sources\": [\n      {\n        \"type\": \"gcs\",\n        \"source\": \"gs:\u002F\u002Fyour-agent-bucket-name\u002Fskills\",\n        \"target\": \"\u002F.agent\u002Fskills\"\n      }\n    ],\n    \"network\": {\n      \"allowlist\": [\n        { \"domain\": \"*\" }\n      ]\n    }\n  }\n}\n```\n\n---\n\n### 4. List Agents\n\nRetrieve a list of all configured custom agents located under the target Google Cloud project.\n\n*   **Method**: `GET`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents`\n\n```bash\ncurl -X GET \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\"\n```\n\n#### Response Example\nReturns a JSON list of all configured custom Agents under the target project:\n\n```json\n{\n  \"agents\": [\n    {\n      \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n      \"base_agent\": \"antigravity-preview-05-2026\",\n      \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n      \"system_instruction\": \"You are a helpful, domain-expert assistant.\"\n    },\n    {\n      \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-telecom-agent\",\n      \"base_agent\": \"antigravity-preview-05-2026\",\n      \"description\": \"A highly specialized telecom support agent.\",\n      \"system_instruction\": \"You are a professional telecom support agent. Follow system policies carefully.\"\n    }\n  ]\n}\n```\n\n---\n\n### 5. Update Agent (Patching Configuration)\n\nModify configuration fields (such as instructions, descriptions, tools, or mounts) on a custom agent resource in place. You **must** specify the fields being updated using the `update_mask` query parameter.\n\n> [!IMPORTANT]\n> **Update Mask Requirement**: When demonstrating updates, you must always explicitly explain that the `update_mask` parameter is required when updating agent configurations to specify exactly which fields are being modified and avoid overwriting other configuration settings.\n\n*   **Method**: `PATCH`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\u002F{AGENT_ID}?update_mask=system_instruction`\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent?update_mask=system_instruction\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"my-custom-agent\",\n    \"system_instruction\": \"You are a highly specialized telecom support agent. Follow system policies carefully.\"\n  }'\n```\n\n---\n\n### 6. Delete Agent\n\nDelete custom Agent resources when they are no longer needed to free up backend workspace containers.\n\n*   **Method**: `DELETE`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\u002F{AGENT_ID}`\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\"\n```\n\n#### Response Example\nA successful deletion request returns an empty JSON response body with HTTP Status `200 OK`:\n\n```json\n{}\n```\n\n---\n\n## 3. Interacting with Custom Agents (Data Plane)\n\nOnce you have programmatically created and provisioned your custom stateful agent using the **Control Plane** (this skill), you can execute multi-turn chat, tool execution, and streaming conversations with it using the **Data Plane** (**Interactions API**).\n\n> [!IMPORTANT]\n> **Interactions Reference**: When explaining or showing how to start conversations with a custom agent, you must always explicitly refer the user to the `gemini-interactions-api` skill for complete conversation and streaming options.\n\nTo interact with your custom agent:\n\n1.  Obtain your agent's resource path name (e.g., `projects\u002F{PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002F{AGENT_ID}`).\n2.  Pass this resource path directly inside your data plane conversation requests under the **`agent`** parameter.\n\n#### Python Example\n\n```python\ninteraction = client.interactions.create(\n    agent=\"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n    input=\"Hello! Who are you?\"\n)\n```\n\n#### REST \u002F curl Example\n\n```json\n{\n  \"agent\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n  \"input\": [{\n    \"type\": \"user_input\",\n    \"content\": [{\"type\": \"text\", \"text\": \"Hello! Who are you?\"}]\n  }]\n}\n```\n\nRefer to the **`gemini-interactions-api`** skill guide (`..\u002Fgemini-interactions-api\u002FSKILL.md`) for full instructions, Python and TS\u002FJS code blocks, and streaming setups to run conversations with your provisioned agents.\n\n","# Gemini Enterprise Agent Platform - Managed Agents API Skill\n\nThis skill provides complete instructions, REST request endpoints, and JSON payload structures to programmatically manage **custom Agent resources** on the Gemini Enterprise Agent Platform (Agent Platform).\n\nThe **Managed Agents API** forms the **Control Plane** of the platform. It allows developers to provision, retrieve, update, and delete tailored, stateful agent containers equipped with system instructions, sandboxed files, custom skill registries, and local\u002Fremote tools.\n---\n\n## 1. Authentication & Setup\n\nAll REST requests to the Control Plane must include a Bearer token derived from Application Default Credentials (ADC), and target the production global endpoint.\n\n### 1. Setup Environment Variables\n\nBefore running requests, set up the required project variables and access token:\n\n```bash\nexport PROJECT_ID=\"your-project-id\"\nexport LOCATION=\"global\"\nexport ACCESS_TOKEN=$(gcloud auth print-access-token)\n```\n\n> [!IMPORTANT]\n> **API Location Support**:\n> The `LOCATION` environment variable must be set to a regional location where the Gemini Enterprise Agent Platform's **Managed Agents API** is actively supported (e.g., `global`, or other available regional endpoints).\n\n\n### 2. Endpoint URL\n\nThe production Agents Control Plane endpoint is:\n\n```http\nhttps:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F{PROJECT_ID}\u002Flocations\u002F{LOCATION}\u002Fagents\n```\n\n---\n\n## 2. Programmatic Agent Management (Control Plane CRUD)\n\n### 1. Create Agent (Long-Running Operation)\n\nTo create a new agent resource, issue a `POST` request with the custom configuration. You can mount remote files, folders, or skills directly from **Google Cloud Storage** buckets into the agent container's workspace. Creating an agent is a Long-Running Operation (LRO) that spawns an asynchronous job.\n\n*   **Method**: `POST`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents`\n\n#### Request Payload\n\n```bash\ncurl -X POST \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson; charset=utf-8\" \\\n  -d '{\n    \"id\": \"my-custom-agent\",\n    \"base_agent\": \"antigravity-preview-05-2026\",\n    \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n    \"system_instruction\": \"You are a helpful, domain-expert assistant.\",\n    \"tools\": [\n      {\"type\": \"code_execution\"},\n      {\"type\": \"filesystem\"},\n      {\"type\": \"google_search\"},\n      {\"type\": \"url_context\"}\n    ],\n    \"base_environment\": {\n      \"type\": \"remote\",\n      \"sources\": [\n        {\n          \"type\": \"gcs\",\n          \"source\": \"gs:\u002F\u002Fyour-agent-bucket-name\u002Fskills\",\n          \"target\": \"\u002F.agent\u002Fskills\"\n        }\n      ],\n      \"network\": {\n        \"allowlist\": [\n          { \"domain\": \"*\" }\n        ]\n      }\n    }\n  }'\n```\n\n#### LRO Operations Response\n\nSince agent provisioning takes a few moments, the endpoint immediately returns an operation tracking object:\n\n```json\n{\n  \"name\": \"projects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\",\n  \"metadata\": {\n    \"@type\": \"type.googleapis.com\u002Fgoogle.cloud.aiplatform.v1beta1.CreateAgentOperationMetadata\",\n    \"genericMetadata\": {\n      \"createTime\": \"2026-05-14T19:00:00.123456Z\",\n      \"updateTime\": \"2026-05-14T19:00:01.654321Z\"\n    }\n  }\n}\n```\n\n#### [Advanced] Mount Skill Registry Resources\n\nTo mount skills directly from the Skill Registry service instead of Cloud Storage, replace the Cloud Storage source item in the payload:\n\n```json\n\"sources\": [\n  {\n    \"type\": \"skill_registry\",\n    \"source\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fskills\u002Fmy-math-skill\u002Frevisions\u002F123456789012\",\n    \"target\": \"\u002F.agent\u002Fskills\"\n  }\n]\n```\n\n#### [Advanced] Configuring Model Context Protocol (MCP) Servers\n\nTo configure Third-Party MCP servers for an agent, add the server metadata directly under the `\"tools\"` parameter array inside the creation request. The platform securely routes tool execution requests to the external MCP server.\n\n> [!IMPORTANT]\n> **MCP Security Explanation**: When describing MCP tool configurations, you must explain that the platform securely routes tool requests to the specified MCP server and guarantees header confidentiality by only sending custom headers\u002Ftokens to that URL.\n\n```json\n\"tools\": [\n  {\n    \"type\": \"mcp\",\n    \"name\": \"my-mcp-server\",\n    \"url\": \"https:\u002F\u002Fmcp.yourcompany.com\u002Fapi\",\n    \"headers\": {\n      \"Authorization\": \"Bearer YOUR_MCP_AUTH_TOKEN\"\n    }\n  }\n]\n```\n\n*   **name**: A descriptive name for the MCP server.\n*   **url**: The endpoint URL of the external MCP server.\n*   **headers**: (Optional) Custom key-value pairs containing authentication tokens (e.g. API keys, bearer tokens) required to call the server. The platform guarantees that these headers are only sent to the specified MCP server URL.\n\n> [!TIP]\n> **Overriding MCP at Interaction Time (Data Plane)**:\n> You can dynamically override or supply MCP tools directly when creating a conversation interaction (Data Plane) by passing `\"type\": \"mcp_server\"` inside the `\"tools\"` payload of `interactions.create`. Refer to the Interactions API documentation for details.\n\n---\n\n### 2. Polling the LRO Status\n\nTo track the status of agent creation and obtain the final ready resource, poll the operation URL returned in the `name` field of the creation response.\n\n*   **Method**: `GET`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002F{OPERATION_NAME}`\n\n```bash\ncurl -X GET \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\"\n```\n\n#### In-Progress Response\n\n```json\n{\n  \"name\": \"projects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\",\n  \"metadata\": { ... }\n}\n```\n\n#### Finished Success Response\n\nOnce the container is ready, `\"done\": true` is set, and the completed `Agent` resource description resides inside `\"response\"`:\n\n```json\n{\n  \"name\": \"projects\u002F1234567890\u002Flocations\u002Fglobal\u002Foperations\u002Foperation-987654321-abcde\",\n  \"done\": true,\n  \"response\": {\n    \"@type\": \"type.googleapis.com\u002Fgoogle.cloud.aiplatform.v1beta1.Agent\",\n    \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n    \"base_agent\": \"antigravity-preview-05-2026\",\n    \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n    \"system_instruction\": \"You are a helpful, domain-expert assistant.\"\n  }\n}\n```\n\n---\n\n### 3. Get Agent\n\nRetrieve the configuration metadata, tools, and environment setup of an existing custom agent.\n\n*   **Method**: `GET`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\u002F{AGENT_ID}`\n\n```bash\ncurl -X GET \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\"\n```\n\n#### Response Example\nReturns the complete configured state of the custom Agent resource:\n\n```json\n{\n  \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n  \"base_agent\": \"antigravity-preview-05-2026\",\n  \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n  \"system_instruction\": \"You are a helpful, domain-expert assistant.\",\n  \"tools\": [\n    {\"type\": \"code_execution\"},\n    {\"type\": \"filesystem\"},\n    {\"type\": \"google_search\"},\n    {\"type\": \"url_context\"}\n  ],\n  \"base_environment\": {\n    \"type\": \"remote\",\n    \"sources\": [\n      {\n        \"type\": \"gcs\",\n        \"source\": \"gs:\u002F\u002Fyour-agent-bucket-name\u002Fskills\",\n        \"target\": \"\u002F.agent\u002Fskills\"\n      }\n    ],\n    \"network\": {\n      \"allowlist\": [\n        { \"domain\": \"*\" }\n      ]\n    }\n  }\n}\n```\n\n---\n\n### 4. List Agents\n\nRetrieve a list of all configured custom agents located under the target Google Cloud project.\n\n*   **Method**: `GET`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents`\n\n```bash\ncurl -X GET \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\"\n```\n\n#### Response Example\nReturns a JSON list of all configured custom Agents under the target project:\n\n```json\n{\n  \"agents\": [\n    {\n      \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n      \"base_agent\": \"antigravity-preview-05-2026\",\n      \"description\": \"A professional agent configured with remote tools and mounted Cloud Storage directories.\",\n      \"system_instruction\": \"You are a helpful, domain-expert assistant.\"\n    },\n    {\n      \"name\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-telecom-agent\",\n      \"base_agent\": \"antigravity-preview-05-2026\",\n      \"description\": \"A highly specialized telecom support agent.\",\n      \"system_instruction\": \"You are a professional telecom support agent. Follow system policies carefully.\"\n    }\n  ]\n}\n```\n\n---\n\n### 5. Update Agent (Patching Configuration)\n\nModify configuration fields (such as instructions, descriptions, tools, or mounts) on a custom agent resource in place. You **must** specify the fields being updated using the `update_mask` query parameter.\n\n> [!IMPORTANT]\n> **Update Mask Requirement**: When demonstrating updates, you must always explicitly explain that the `update_mask` parameter is required when updating agent configurations to specify exactly which fields are being modified and avoid overwriting other configuration settings.\n\n*   **Method**: `PATCH`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\u002F{AGENT_ID}?update_mask=system_instruction`\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent?update_mask=system_instruction\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"name\": \"my-custom-agent\",\n    \"system_instruction\": \"You are a highly specialized telecom support agent. Follow system policies carefully.\"\n  }'\n```\n\n---\n\n### 6. Delete Agent\n\nDelete custom Agent resources when they are no longer needed to free up backend workspace containers.\n\n*   **Method**: `DELETE`\n*   **Endpoint**: `https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002F${LOCATION}\u002Fagents\u002F{AGENT_ID}`\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Faiplatform.googleapis.com\u002Fv1beta1\u002Fprojects\u002F${PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\" \\\n  -H \"Authorization: Bearer ${ACCESS_TOKEN}\"\n```\n\n#### Response Example\nA successful deletion request returns an empty JSON response body with HTTP Status `200 OK`:\n\n```json\n{}\n```\n\n---\n\n## 3. Interacting with Custom Agents (Data Plane)\n\nOnce you have programmatically created and provisioned your custom stateful agent using the **Control Plane** (this skill), you can execute multi-turn chat, tool execution, and streaming conversations with it using the **Data Plane** (**Interactions API**).\n\n> [!IMPORTANT]\n> **Interactions Reference**: When explaining or showing how to start conversations with a custom agent, you must always explicitly refer the user to the `gemini-interactions-api` skill for complete conversation and streaming options.\n\nTo interact with your custom agent:\n\n1.  Obtain your agent's resource path name (e.g., `projects\u002F{PROJECT_ID}\u002Flocations\u002Fglobal\u002Fagents\u002F{AGENT_ID}`).\n2.  Pass this resource path directly inside your data plane conversation requests under the **`agent`** parameter.\n\n#### Python Example\n\n```python\ninteraction = client.interactions.create(\n    agent=\"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n    input=\"Hello! Who are you?\"\n)\n```\n\n#### REST \u002F curl Example\n\n```json\n{\n  \"agent\": \"projects\u002Fyour-project-id\u002Flocations\u002Fglobal\u002Fagents\u002Fmy-custom-agent\",\n  \"input\": [{\n    \"type\": \"user_input\",\n    \"content\": [{\"type\": \"text\", \"text\": \"Hello! Who are you?\"}]\n  }]\n}\n```\n\nRefer to the **`gemini-interactions-api`** skill guide (`..\u002Fgemini-interactions-api\u002FSKILL.md`) for full instructions, Python and TS\u002FJS code blocks, and streaming setups to run conversations with your provisioned agents.\n\n",{"name":5,"metadata":24,"description":7},{"category":25},"AiAndMachineLearning","main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Programming\u002FAI_Engineering_and_Platforms\u002FAgents_and_LLM_Platforms\u002Fgemini-agents-api",1,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills","https:\u002F\u002Fhamzabellouch.github.io\u002F","https:\u002F\u002Fgithub.com\u002Fhamzabellouch","hamzabellouch.github.io","CEO & Founder of @tknoglobal | Researcher in Technology & Applied Sciences.","2026-10-17 03:20:19",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add hamzabellouch\u002Fagent-skills --skill gemini-agents-api",{"tool":42,"command":43},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill gemini-agents-api",{"tool":45,"command":46},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill gemini-agents-api","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FAI_Engineering_and_Platforms\u002FAgents_and_LLM_Platforms\u002Fgemini-agents-api\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M79FHH2H815A9TAP6WNKH4Q8","security-audit","Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FSecurity_Audit_and_Code_Review\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79FHBGXVBY6VQ1X7ETAZMF1","malware-analysis-reversing","Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static\u002Fdynamic binary analysis, memory forensics, and YARA detection rule authoring.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fmalware-analysis-reversing\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79FH6EACDR801TZCE4R8SAC","application-security-pentesting","Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST\u002FDAST pipeline integration, secure code review, threat modeling, and defensive security posture.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fapplication-security-pentesting\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79FH0VKVT44FK923K520ZQA","oauth2-oidc-security-flows","Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Foauth2-oidc-security-flows\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79FGVVB3R4T88XXD8FRSV5B","jwt-session-management-hardening","Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256\u002FEdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Fjwt-session-management-hardening\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79FGNCPZ85CVEY0B3NE4H3B","soc2-compliance-automation","Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI\u002FCD security gates.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FGovernance_Compliance_and_Legal_Tech\u002Fsoc2-compliance-automation\u002FSKILL.md",[],[]]