How do I install the Gemini API skill?

Run npx skillmds@latest add tomevault-io/gemini-api-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gemini API safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gemini API?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gemini API free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gemini API?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gemini API by tomevault-io — Agent Skill

Name: Gemini API
Author: tomevault-io

Gemini API

Provides the official Protobuf specifications and gRPC/REST service definitions for the Gemini API (Google Generative Language API v1beta). Use this skill when you need precise schema definitions for requests/responses (e.g., GenerateContent, Tools, FunctionCalling), multimodal content structures (Content, Part), context caching, model metadata, safety settings, or file uploads.

tomevault-io Updated Sep 17, 2026

File contents

Gemini API Documentation (Protobuf Definitions)

This skill provides the official v1beta Protobuf definitions for the Google Generative Language API (Gemini). These files contain the absolute source of truth for API capabilities, request/response structures, and schema definitions.

When to use these references

When implementing or debugging Gemini API clients (such as in Rust, Go, or other languages), refer to these files for the exact structure of messages, enums, and RPC methods.

Core Services & Schemas

The .proto files are located in references/. Here is a guide on where to look for specific features:

Content Generation & Tools

generative_service.proto: Contains the core GenerateContentRequest and GenerateContentResponse. Look here for tool configurations, system instructions, and generation configurations.
content.proto: Defines the Content, Part, FunctionCall, FunctionResponse, Tool, and ToolConfig structures. Essential for understanding how to construct multimodal payloads and function calling schemas.
safety.proto: Defines HarmCategory, SafetySetting, and SafetyRating enums and messages.

Models & Metadata

model.proto: Defines the Model message, including properties like input_token_limit, output_token_limit, and supported generation methods.
model_service.proto: RPCs for listing and getting models (GetModel, ListModels).

Context Caching

cached_content.proto: Defines the CachedContent resource for caching large prompts.
cache_service.proto: RPCs for managing cached contents (CreateCachedContent, UpdateCachedContent, etc.).

File API (Multimodal Uploads)

file.proto: Defines the File resource representing uploaded media (video, images, documents).
file_service.proto: RPCs for the File API (CreateFile, ListFiles, GetFile, DeleteFile).

Semantic Retrieval (RAG/AQA)

retriever.proto / retriever_service.proto: Definitions for Corpora, Documents, Chunks, and operations like Semantic Search and Attributed Question Answering (AQA).

Fine-tuning

tuned_model.proto: Definitions for tuning jobs and datasets.
permission.proto / permission_service.proto: Access control for tuned models and corpora.

Legacy / PaLM Services

discuss_service.proto / text_service.proto / prediction_service.proto: Older APIs (like GenerateMessage or GenerateText), primarily for PaLM 2 models. Usually not needed for modern Gemini implementations.

How to use

If you need to know the exact field names, types, or enums (e.g., "Does ToolConfig take a string or an enum for function calling mode?"), use grep_search or view the relevant file in the references/ directory.

Example: If implementing function calling, check content.proto for FunctionCall and generative_service.proto for where tools is placed in the GenerateContentRequest.

Source: stephen94125/peon-lib — distributed by TomeVault.

---name: gemini-api-2description: Provides the official Protobuf specifications and gRPC/REST service definitions for the Gemini API (Google Generative Language API v1beta). Use this skill when you need precise schema definitions for requests/responses (e.g., GenerateContent, Tools, FunctionCalling), multimodal content structures (Content, Part), context caching, model metadata, safety settings, or file uploads.---# Gemini API Documentation (Protobuf Definitions)This skill provides the official v1beta Protobuf definitions for the Google Generative Language API (Gemini). These files contain the absolute source of truth for API capabilities, request/response structures, and schema definitions.## When to use these referencesWhen implementing or debugging Gemini API clients (such as in Rust, Go, or other languages), refer to these files for the exact structure of messages, enums, and RPC methods.## Core Services & SchemasThe `.proto` files are located in `references/`. Here is a guide on where to look for specific features:### Content Generation & Tools- **`generative_service.proto`**: Contains the core `GenerateContentRequest` and `GenerateContentResponse`. Look here for tool configurations, system instructions, and generation configurations.- **`content.proto`**: Defines the `Content`, `Part`, `FunctionCall`, `FunctionResponse`, `Tool`, and `ToolConfig` structures. Essential for understanding how to construct multimodal payloads and function calling schemas.- **`safety.proto`**: Defines `HarmCategory`, `SafetySetting`, and `SafetyRating` enums and messages.### Models & Metadata- **`model.proto`**: Defines the `Model` message, including properties like `input_token_limit`, `output_token_limit`, and supported generation methods.- **`model_service.proto`**: RPCs for listing and getting models (`GetModel`, `ListModels`).### Context Caching- **`cached_content.proto`**: Defines the `CachedContent` resource for caching large prompts.- **`cache_service.proto`**: RPCs for managing cached contents (`CreateCachedContent`, `UpdateCachedContent`, etc.).### File API (Multimodal Uploads)- **`file.proto`**: Defines the `File` resource representing uploaded media (video, images, documents).- **`file_service.proto`**: RPCs for the File API (`CreateFile`, `ListFiles`, `GetFile`, `DeleteFile`).### Semantic Retrieval (RAG/AQA)- **`retriever.proto` / `retriever_service.proto`**: Definitions for Corpora, Documents, Chunks, and operations like Semantic Search and Attributed Question Answering (AQA).### Fine-tuning- **`tuned_model.proto`**: Definitions for tuning jobs and datasets.- **`permission.proto` / `permission_service.proto`**: Access control for tuned models and corpora.### Legacy / PaLM Services- **`discuss_service.proto` / `text_service.proto` / `prediction_service.proto`**: Older APIs (like `GenerateMessage` or `GenerateText`), primarily for PaLM 2 models. Usually not needed for modern Gemini implementations.## How to useIf you need to know the exact field names, types, or enums (e.g., "Does `ToolConfig` take a string or an enum for function calling mode?"), use `grep_search` or view the relevant file in the `references/` directory.Example: If implementing function calling, check `content.proto` for `FunctionCall` and `generative_service.proto` for where `tools` is placed in the `GenerateContentRequest`.---> Source: [stephen94125/peon-lib](https://github.com/stephen94125/peon-lib) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions