provider-grok

Solid

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/subcommand behaviour changes, or when an upstream scan flags drift. Process guidance only; `src/upstream-contracts.ts` is the mechanical source of truth.

AI & Automation 16 stars 0 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

100

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# 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 t...

Details

Author: verivus-oss
Repository: verivus-oss/llm-cli-gateway
Created: 5 months ago
Last Updated: 2 days ago
Language: TypeScript
License: MIT

Integrates with

Model Context Protocol · AI

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

provider-codex

Track and maintain the upstream OpenAI Codex CLI contract. Use when OpenAI ships a Codex release, when a `codex exec` flag/sandbox/approval/resume/subcommand behaviour changes, or when an upstream scan flags drift. Process guidance only; `src/upstream-contracts.ts` is the mechanical source of truth.

16 Updated 2 days ago

verivus-oss

AI & Automation Solid

provider-gemini

Track and maintain the gateway's Gemini-compatible Google Antigravity CLI contract. Use when Google ships an Antigravity CLI release, when an `agy` flag/permission/session/subcommand behaviour changes, or when an upstream scan flags drift. Process guidance only; `src/upstream-contracts.ts` is the mechanical source of truth.

16 Updated 2 days ago

verivus-oss

AI & Automation Solid

provider-cursor

Track and maintain the upstream Cursor Agent CLI contract. Use when Cursor ships a CLI release, when a `cursor-agent` flag, execution mode, session command, ACP entrypoint, or subcommand changes, or when an upstream scan flags drift. Process guidance only: `src/upstream-contracts.ts` is the mechanical source of truth.

16 Updated 2 days ago

verivus-oss