provider-geminilisted

Track and maintain the upstream Google Gemini CLI contract. Use when Google ships a Gemini CLI release, when a `gemini` flag/approval-mode/output-format/resume behaviour changes, or when an upstream scan flags drift. Process guidance only — `src/upstream-contracts.ts` is the mechanical source of truth.
verivus-oss/llm-cli-gateway · ★ 8 · AI & Automation · score 78

Install: claude install-skill verivus-oss/llm-cli-gateway

# Provider: Google Gemini CLI Process guidance for keeping the gateway's Gemini (`gemini`) integration aligned with the upstream CLI. This skill does **not** define argv/env behaviour — the single mechanical source of truth is `UPSTREAM_CLI_CONTRACTS.gemini` in `src/upstream-contracts.ts`, enforced by `validateUpstreamCliArgs` / `validateUpstreamCliEnv`. Never re-encode flags, approval modes, output formats, or resume rules here or in TOML. ## Identity | Field | Value | |-------|-------| | CliType | `gemini` | | Executable | `gemini` | | Package | `@google/gemini-cli` (npm) | | Repo | https://github.com/google-gemini/gemini-cli | | Changelogs | https://geminicli.com/docs/changelogs/ · https://github.com/google-gemini/gemini-cli/releases | | Watch categories | `flags`, `approval-modes`, `output-formats`, `session-resume` | These values mirror `UPSTREAM_CLI_CONTRACTS.gemini.upstreamMetadata` and `docs/upstream/provider-sources.dag.toml` (`[providers.gemini]`). The TypeScript metadata is authoritative; the TOML is scanner input only. ## When to use - A Google Gemini CLI release lands and you need to check for contract drift. - A `gemini` request fails the upstream contract check before spawn. - `npm run upstream:scan -- --live` reports a change on either Gemini source. ## Scan for upstream change ```bash npm run upstream:scan -- --provider gemini npm run upstream:scan -- --live --provider gemini --fail-on-critical npm run upstream:scan -- --live --provider gemini --write