Agent skill · Workflow & Productivity

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.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill grok-build --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 7 KB
Bundled scripts: none
Declared author: sanjay3290
Path: skills/grok-build/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 ac

What's inside
Steps it walks through
  1. When to Use
  2. Safety Gate
  3. When to delegate vs keep with the orchestrator
  4. Session preflight (once, before the first dispatch)
  5. Per-task loop (sequential — the default)
  6. Task spec template
  7. Executing a Markdown implementation plan
  8. Parallel dispatch (opt-in exception, not the default)
  9. Failure handling
  10. Limitations
  11. Models
Ships with 1 file
  • references/cli.md
Commands it runs
grok --prompt-file <task-file> \
More from agentic-awesome-skills
All skills →
About this skill
What does the grok-build skill do?

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.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill grok-build --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going