Stats
Actions
Tags
From grok
Diagnose the Grok plugin — CLI presence, auth, resolved config, and Node version
How this command is triggered — by the user, by Claude, or both
Slash command
/grok:setup [--json]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Run: Present the report to the user. If it reports that grok is **not installed**, the fix is the curl bootstrap (do NOT suggest `npm install` — grok is installed via curl): If grok is installed but **not authenticated**, tell the user to set `XAI_API_KEY` or sign in with SuperGrok / X Premium+ (grok stores auth at `~/.grok/auth.json`). Never print the key value.
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/grok.mjs" setup $ARGUMENTS
Present the report to the user.
If it reports that grok is not installed, the fix is the curl bootstrap (do NOT suggest npm install — grok is installed via curl):
curl -fsSL https://x.ai/cli/install.sh | bash
If grok is installed but not authenticated, tell the user to set XAI_API_KEY or sign in with SuperGrok / X Premium+ (grok stores auth at ~/.grok/auth.json). Never print the key value.
/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupWalks an enterprise admin through configuring the Claude Office add-in to call their own cloud (Vertex, Bedrock, Foundry, or gateway), producing a customized manifest.xml for M365 deployment.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupInteractive setup wizard that detects installed AI providers, configures authentication, and optimizes token usage. Auto-runs on first install and surfaces a status dashboard on manual invocation.
npx claudepluginhub trevoraspencer/grok-plugin-cc --plugin grok