gemini-api — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited gemini-api (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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 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.
The .proto files are located in references/. Here is a guide on where to look for specific features:
GenerateContentRequest and GenerateContentResponse. Look here for tool configurations, system instructions, and generation configurations.Content, Part, FunctionCall, FunctionResponse, Tool, and ToolConfig structures. Essential for understanding how to construct multimodal payloads and function calling schemas.HarmCategory, SafetySetting, and SafetyRating enums and messages.Model message, including properties like input_token_limit, output_token_limit, and supported generation methods.GetModel, ListModels).CachedContent resource for caching large prompts.CreateCachedContent, UpdateCachedContent, etc.).File resource representing uploaded media (video, images, documents).CreateFile, ListFiles, GetFile, DeleteFile).GenerateMessage or GenerateText), primarily for PaLM 2 models. Usually not needed for modern Gemini implementations.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.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.