provider-mistrallisted

Track and maintain the upstream Mistral Vibe CLI contract. Use when Mistral ships a Vibe release, when a `vibe` flag/agent-mode/output-format/session-logging/env-model 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: Mistral Vibe CLI Process guidance for keeping the gateway's Mistral (`vibe`) integration aligned with the upstream CLI. This skill does **not** define argv/env behaviour — the single mechanical source of truth is `UPSTREAM_CLI_CONTRACTS.mistral` in `src/upstream-contracts.ts`, enforced by `validateUpstreamCliArgs` / `validateUpstreamCliEnv`. Never re-encode flags, agent modes, output formats, the env-model rule, or resume rules here or in TOML. ## Identity | Field | Value | |-------|-------| | CliType | `mistral` | | Executable | `vibe` | | Package | `mistral-vibe` (pypi; also uv / brew) | | Repo | https://github.com/mistralai/mistral-vibe | | Changelog | https://github.com/mistralai/mistral-vibe/releases | | Watch categories | `flags`, `agent-modes`, `session-logging`, `output-formats`, `env-model` | These values mirror `UPSTREAM_CLI_CONTRACTS.mistral.upstreamMetadata` and `docs/upstream/provider-sources.dag.toml` (`[providers.mistral]`). The TypeScript metadata is authoritative; the TOML is scanner input only. ## When to use - A Mistral Vibe release lands and you need to check for contract drift. - A `mistral` request fails the upstream contract check before spawn. - `npm run upstream:scan -- --live` reports a change on the Vibe releases page. ## Scan for upstream change ```bash npm run upstream:scan -- --provider mistral npm run upstream:scan -- --live --provider mistral --fail-on-critical npm run upstream:scan -- --live --provider mistral --write-snaps