Agent skill · software engineering · sickn33
grok-build
Delegate well-specified implementation tasks to xAI's Grok Build CLI running headlessly while the orchestrating agent plans, writes task specs, reviews every diff, and owns the result.
Why this skill is useful
Adds executable scripts for task delegation to Grok Build CLI that automate the implementation process and ensure proper task management.
What it needs
Requires grok installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Grok Build Orchestration When to Use Use when delegating a well-specified implementation task to xAI's Grok Build CLI running headlessly Use when executing a Markdown implementation plan task-by-task with a diff review after each task Use when the user says "use grok", "grok build", "have grok implement", or "send to grok" The coding assistant is the orchestrator: it plans, writes self-contained task specs, dispatches them to Grok Build headlessly, reviews every diff, and owns the final result. Grok is the fast, cheap executor. Full CLI details and verified behaviors: references/cli.md. Safety Gate Before every dispatch, show the user the exact task specification that will be sent to xAI, the target worktree, and the permission mode. Obtain explicit approval to disclose that text and to let Grok edit the scoped worktree. Never include secrets, proprietary source, customer data, or credentials in a task specification. Do not run grok update, --always-approve, or a destructive recovery command without separate, explicit approval. When to delegate vs keep with the orchestrator Delegate to Grok Keep with the orchestrator --- --- Plan tasks with clear acceptance criteria Ambiguous requirements, architecture decisions Boilerplate, scaffolding, CRUD Deep cross-file debugging Mechanical refactors Security-sensitive code Test writing from clear specs Anything touching production infrastructure UI components from mockups/specs Tasks where writing the spec ≈ doing the work When in doubt, keep it with the orchestrator. Session preflight (once, before the first dispatch) 1. grok update --check --json — if updateAvailable is true, tell the user. Run grok update only after explicit approval, then confirm with grok --version. 2. grok models — if it errors or reports logged out, STOP and ask the user to run grok login. Per-task loop (sequential — the default) 1. Spec. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/grok-build