SkillAgentSearch skills...

grok-build

Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every diff, and owns the result

Install / Use

npx skills add sanjay3290/ai-skills --skill grok-build

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Supported Platforms

Universal

Our assessment of grok-build

grok-build scores 83/100 on our quality scale, 938th of 1,148 Content & Media skills we index.

Its SKILL.md is 5.4 KB long, well organised into 15 sections with 1 code example: a solid amount of guidance for an agent.

It has 426 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so grok-build is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: Instructs the agent to invoke `grok` with `--always-approve`, which disables edit approval prompts for a delegated AI and weakens safeguards.

AI review: risky

  • Instructs the agent to invoke `grok` with `--always-approve`, which disables edit approval prompts for a delegated AI and weakens safeguards.
  • Tells the agent to run `grok update` and `grok login` on the user's machine, trusting the external CLI.
  • The file is a SKILL.md, so these commands are instructions the agent will follow, not merely human documentation.

AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

grok-build compared with similar skills

All 4 of these similar skills score higher than grok-build; compare them before choosing.

SkillScoreStarsUpdatedFormat
grok-build (this skill)by sanjay3290834262mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
algorithmic-artby anthropics100177.9k57d agoSKILL.md
pptxby anthropics100177.9k57d agoSKILL.md
prospectingby coreyhaines3110060.1k7d agoSKILL.md

Frequently asked questions

How do I install grok-build?
Run npx skills add sanjay3290/ai-skills --skill grok-build. The install tabs above show the steps for each supported agent.
Which AI agents does grok-build work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is grok-build safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review judged it risky: Instructs the agent to invoke grok with --always-approve, which disables edit approval prompts for a delegated AI and weakens safeguards. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is grok-build still maintained?
The repository was last updated about 2 months ago, so grok-build is actively maintained.

name: grok-build description: "Orchestrate coding work by delegating well-specified implementation tasks to xAI's Grok Build CLI (grok) running headlessly, while the coding assistant plans, writes the task specs, reviews every diff, and owns the result. Use when user says: 'use grok', 'grok build', 'delegate to grok', 'have grok implement', 'have grok execute', 'have grok build', 'send to grok', 'execute this plan with grok'. Executes a Markdown implementation plan task-by-task, or ad-hoc tasks with an inline spec." license: Apache-2.0 metadata: author: sanjay3290 version: "1.0"

Grok Build Orchestration

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.

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, run grok update and 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. Write a self-contained task file (template below) to a temp directory OUTSIDE the target repo — the harness scratchpad if one is available, else the OS temp dir. Never write it inside the target repo. Grok has zero conversation context: no one-liner prompts, ever.

    • POSIX: mkdir -p "${TMPDIR:-/tmp}/grok-specs", then write task.md there.
    • Windows (PowerShell): New-Item -ItemType Directory -Force "$env:TEMP\grok-specs", then write task.md there.
  2. Clean state. No uncommitted source changes — commit or stash first, so the post-run diff is exactly Grok's work. Ignore build artifacts (__pycache__, dist/, etc.); if they show in git status, they're usually just un-gitignored, not your concern. Never dispatch on a dirty source tree.

  3. Dispatch.

    POSIX:

    grok --prompt-file <task-file> \
      --output-format json \
      --always-approve \
      --max-turns 30 \
      --cwd <repo>
    

    Windows (PowerShell) — backtick line-continuation:

    grok --prompt-file <task-file> `
      --output-format json `
      --always-approve `
      --max-turns 30 `
      --cwd <repo>
    

    Parse the JSON output and save sessionId. (--always-approve is required for headless runs — --permission-mode acceptEdits silently cancels edits with no interactive approver. See references/cli.md.) For a high-stakes task, add --check so Grok self-verifies before you review; skip it otherwise (it ~doubles latency).

  4. Review gate — non-negotiable.

    • Read the diff yourself (git diff -- <files from the spec> to skip artifact noise): does it do the task, only the task, and match repo conventions?
    • Run the acceptance commands from the spec.
    • Pass → commit with a clear message following the repo's convention → next task.
    • Fail → fix-up: grok --resume <sessionId> -p "<specific feedback>" --always-approve --output-format json. Max 2 fix-up rounds. Still failing → revert Grok's changes (git checkout -- .; git clean -fd for new files), do the task yourself, and tell the user Grok couldn't complete it.

Task spec template

# Task: <one-line title>

## Context
- Repo: <path> — <one line on what the project is>
- Conventions: <test runner, formatter, a good example file to imitate>

## Files
- Modify: <path>
- Create: <path>

## Task
<precise description of the change>

## Constraints
- Do not modify any files other than those listed above.
- <other constraints>

## Acceptance criteria
- `<exact command>` <expected result>

Executing a Markdown implementation plan

  • One plan task per dispatch, in order.
  • Check off the plan's task checkboxes (- [ ] → - [x]) as each task lands and passes the review gate.
  • If the plan explicitly marks tasks as independent, see Parallel dispatch below; otherwise stay sequential.

Parallel dispatch (opt-in exception, not the default)

Only when a plan explicitly marks tasks independent: dispatch each with --worktree=<task-slug>, run concurrently, then review and merge one worktree at a time through the same review gate. Merge conflicts usually eat the savings — prefer sequential.

Failure handling

| Failure | Action | |---|---| | stopReason: "Cancelled", empty text, no diff | Missing --always-approve — retry with it | | CLI error / timeout | Retry once; then do the task yourself and note the fallback | | Auth expired | Stop; ask the user to run grok login | | 2 fix-up rounds exhausted | Revert Grok's diff; the orchestrator finishes the task | | Dirty tree at dispatch | Refuse; commit/stash first |

Models

Default grok-4.5. Add -m grok-composer-2.5-fast only for trivial mechanical tasks.

Related Skills

View on GitHub
GitHub Stars426
CategoryContent
Updated2mo ago
Forks45

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions