Menu
Skill for interacting with the Grok Build CLI and using it as a subagent.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | grok-cli |
| description | Skill for interacting with the Grok Build CLI and using it as a subagent. |
When you need to use the Grok Build CLI as a subagent or execute any grok commands, you MUST follow this instruction:
Always use the --always-approve flag when invoking the grok command.
grok --always-approve <command> [options]
This ensures that the Grok Build CLI can run autonomously without getting blocked waiting for user input.
Turn a PGS research finding into a three-layer technical note bundle: (1) Grade-10 plain prose, (2) embedded SVG infographic with concise figures, (3) PhD-level rigorous technical treatment; plus a PNG export of the SVG. Output lives under research/<chapter>/30-30-30-technical-note/. Use when the user asks for a "30/30/30 technical note", "30-30-30 tech note", "/30-30-30-technical-note", or wants the standard finding bundle format for a research chapter.
Reduce reasoning friction and produce the most direct, high-fidelity answer or artifact possible. Use when the user invokes /actualize, says "actualize", "cut the fluff", "direct path only", "no redirection", or wants silent pre-output self-inspection to eliminate evasion, scope creep, habitual caution, process narration, or abstraction layers that dilute task fidelity.
Use when the user asks Codex to coordinate with Grok or another local peer agent through Agent Bus MCP, mentions agent-bus, bus topics, readiness handshakes, shared MCP coordination, peer handoffs, or asks to send/read messages through the bus.
Sticky Grok→Gemini collaboration via direct local Antigravity CLI (`agy`) subprocess calls only. Use when the user invokes /agy-cli-collab, $agy-cli-collab, says "antigravity collab", or asks Grok to consult Gemini through the agy CLI. Never use MCP agy_* tools when this skill is active. Multi-turn sessions resume with --conversation (pinned UUID) or --continue fallback.
Write, review, optimize, benchmark, or reason about assembly code for speed, efficiency, SIMD/vectorization, CPU hot paths, low-level kernels, instruction selection, register pressure, cache behavior, branch behavior, or compiler output. Use when the user asks for assembly, "write the kernel in asm", "review this assembly", "optimize this hot path", "explain the instruction schedule", "reduce latency in this loop", or provides surrounding C/ code + benchmark target and wants invariant-first low-level work.
Visual-first exploratory reasoning and hypothesis development for novel ideas, unconventional framings, and early-stage research. Use when the user wants to brainstorm, says "brainstorm", asks to enter brainstorm mode, wants non-obvious insights, wants to escape conventional framing, or wants quick computational probes and visual explanations such as scripts, plots, graphs, charts, infographics, diagrams, slides, parameter sweeps, tables, or toy models to test an idea before converging on a formal plan. Strong emphasis on turning ideas into seeable artifacts early.