菜单
Use for xAI/Grok API capabilities through the lfg xai_grok MCP — text generation, web search, X/Twitter search, image/video generation, and TTS. Load when the user wants Grok-connected xAI tools beyond built-in host tools, or when search_tool should target xai_* MCP tools.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.
MUST USE for planning before coding: 5+ steps, ambiguous scope, multiple modules, architecture decisions, a vague 'just make it good / figure out what to build' brief, or any request to plan, interview, or break work down. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode, just make it good, figure out what to build.
Execute a Prometheus work plan in GrokBuild with `/goal` state, Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and explicit continuation. Use after planning when the user says start work, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.
Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.
Persistent code-mode kernels (JS/Python) for incremental computation — omp/senpi eval analog on GrokBuild via lfg MCP. Use when multi-step code execution, data exploration, or stateful REPL beats one-shot bash.
| name | xai |
| description | Use for xAI/Grok API capabilities through the lfg xai_grok MCP — text generation, web search, X/Twitter search, image/video generation, and TTS. Load when the user wants Grok-connected xAI tools beyond built-in host tools, or when search_tool should target xai_* MCP tools. |
One skill for all lfg xai_grok MCP tools (~/.grok/plugins/lfg/mcp-runtimes/xai-grok-mcp). Use this skill instead of guessing tool names.
lfg setup --run so the plugin ships xai_grok and lfg mirrors it into ~/.grok/config.toml as [mcp_servers.xai_grok] (required for the Grok /mcps UI). Reload MCP with r in /mcps or start a new session.~/.grok/xai-grok-mcp-auth.json via lfg xai auth set-api-key, lfg xai auth set-oauth, or the MCP tools xai_auth_set_api_key / xai_auth_set_oauth; then XAI_API_KEY; then read-only Grok host ~/.grok/auth.json (host file is never written by xai_grok MCP). Never log tokens or keys./mcps OAuth authenticate (i) for xai_grok: Grok only runs that host-managed OAuth flow for HTTP/SSE MCP servers, while xai_grok is local stdio. Use xai_auth_* tools instead.search_tool with a specific query, e.g. "xai web search", "xai x search", "xai image generate".use_tool using the exact schema from step 1 (server is typically xai_grok; tool names use underscores: xai_web_search, not hyphens).| User intent | MCP tool | search_tool hint |
|---|---|---|
| Draft, rewrite, summarize, reason (no live web) | xai_generate_text | xai generate text |
| Current web info + citations | xai_web_search | xai web search |
| X/Twitter posts, handles, real-time social | xai_x_search | xai x search |
| Still images (Grok Imagine) | xai_image_generate | xai image generate |
| Video (text/image/reference) | xai_video_generate | xai video generate |
| Speech / TTS | xai_tts | xai tts |
Details and example payloads: references/tools.md.
xai_generate_text for closed-book generation; use xai_web_search or xai_x_search when recency or sources matter..grok-xai-artifacts when the schema supports artifact_dir.xai_grok is disconnected, say so explicitly; use host-native web_search / x_search only if the user still wants a fallback.Use credentials exposed by the Grok host or MCP server only. Never print, quote, summarize, or store OAuth tokens, refresh tokens, bearer tokens, or API keys.