How do I install the Gemini Gemini API Dev skill?

Run npx skillmds@latest add tomevault-io/gemini-gemini-api-dev 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 Gemini API Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gemini Gemini API Dev?

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 Gemini API Dev free to use?

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

Who published Gemini Gemini API Dev?

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

Gemini Gemini API Dev by tomevault-io

Name: Gemini Gemini API Dev
Author: tomevault-io

Gemini Gemini API Dev

Build Gemini API integrations with verified source evidence, environment separation, request/response validation, safety settings, and testable examples. Use when expanding, reviewing, or operating Gemini CLI skills, rules, prompt kits, provider lanes, or generated-code handoffs in the TechTide skill library. Use when this capability is needed.

tomevault-io 4d0475b 2 files · 2.9 KB Updated Sep 17, 2026

File contents

Gemini API Development

Build Gemini API integrations with verified source evidence, environment separation, request/response validation, safety settings, and testable examples.

Verified Surface

Provider lane: gemini
Native surface: Gemini CLI SKILL.md packages
Harness export: gemini
Import mode: direct-import-normalized
Source evidence: load references/source-evidence.md before promoting third-party material.

Workflow

Confirm the target Gemini API capability, model family, auth method, and runtime.
Keep API keys in environment variables and document only variable names.
Validate request payloads, response parsing, retries, timeouts, and error handling.
Add small examples or tests that can run without exposing production data.
Review safety, logging, and rate-limit behavior before deployment.

Output Contract

Return:

provider lane and native surface
source evidence used
promotion decision or operating recommendation
security and privacy notes
verification still required

Guardrails

Keep third-party source bodies out of public artifacts unless direct import has clean license, attribution, and manual review.
Do not use star counts, popularity, screenshots, or social posts as the sole evidence for promotion.
Do not install or execute unreviewed external scripts as part of source research.
Quarantine missing licenses, unclear ownership, vague prompt packs, duplicate skill packs, and unsupported native-surface claims.
Preserve Alex Cinovoj / TechTide ownership for TechTide-authored synthesis while citing third-party sources as references.

Source: TechTideOhio/techtide-harness-kit — distributed by TomeVault.

---name: gemini-gemini-api-devdescription: Build Gemini API integrations with verified source evidence, environment separation, request/response validation, safety settings, and testable examples. Use when expanding, reviewing, or operating Gemini CLI skills, rules, prompt kits, provider lanes, or generated-code handoffs in the TechTide skill library. Use when this capability is needed.---# Gemini API DevelopmentBuild Gemini API integrations with verified source evidence, environment separation, request/response validation, safety settings, and testable examples.## Verified Surface- Provider lane: gemini- Native surface: Gemini CLI SKILL.md packages- Harness export: gemini- Import mode: direct-import-normalized- Source evidence: load `references/source-evidence.md` before promoting third-party material.## Workflow1. Confirm the target Gemini API capability, model family, auth method, and runtime.2. Keep API keys in environment variables and document only variable names.3. Validate request payloads, response parsing, retries, timeouts, and error handling.4. Add small examples or tests that can run without exposing production data.5. Review safety, logging, and rate-limit behavior before deployment.## Output ContractReturn:- provider lane and native surface- source evidence used- promotion decision or operating recommendation- security and privacy notes- verification still required## Guardrails- Keep third-party source bodies out of public artifacts unless direct import has clean license, attribution, and manual review.- Do not use star counts, popularity, screenshots, or social posts as the sole evidence for promotion.- Do not install or execute unreviewed external scripts as part of source research.- Quarantine missing licenses, unclear ownership, vague prompt packs, duplicate skill packs, and unsupported native-surface claims.- Preserve Alex Cinovoj / TechTide ownership for TechTide-authored synthesis while citing third-party sources as references.---> Source: [TechTideOhio/techtide-harness-kit](https://github.com/TechTideOhio/techtide-harness-kit) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions