provider-groklisted

Track and maintain the upstream xAI Grok CLI contract. Use when xAI ships a Grok CLI release, when a `grok` flag/permission-mode/sandbox/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: xAI Grok CLI Process guidance for keeping the gateway's Grok (`grok`) integration aligned with the upstream CLI. This skill does **not** define argv/env behaviour — the single mechanical source of truth is `UPSTREAM_CLI_CONTRACTS.grok` in `src/upstream-contracts.ts`, enforced by `validateUpstreamCliArgs` / `validateUpstreamCliEnv`. Never re-encode flags, permission modes, sandbox, or resume rules here or in TOML. ## Identity | Field | Value | |-------|-------| | CliType | `grok` | | Executable | `grok` | | Distribution | vendor (no pinned npm/PyPI package recorded) | | Changelog | https://docs.x.ai/developers/release-notes.md | | Install docs | https://docs.x.ai/build/overview | | Watch categories | `flags`, `permission-modes`, `session-resume`, `sandbox`, `output-formats` | These values mirror `UPSTREAM_CLI_CONTRACTS.grok.upstreamMetadata` and `docs/upstream/provider-sources.dag.toml` (`[providers.grok]`). The TypeScript metadata is authoritative; the TOML is scanner input only. ## When to use - An xAI Grok CLI release lands and you need to check for contract drift. - A `grok` request fails the upstream contract check before spawn. - `npm run upstream:scan -- --live` reports a change on the x.ai changelog. ## Scan for upstream change ```bash npm run upstream:scan -- --provider grok npm run upstream:scan -- --live --provider grok --fail-on-critical npm run upstream:scan -- --live --provider grok --write-snapshot --write-report ``` **Strongly recommended f