CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestration skill body: concise, fully actionable with cross-platform commands, and a clearly sequenced workflow with explicit validation and fallback loops. Detail is appropriately offloaded to a single one-level-deep reference file.

DimensionReasoningScore

Conciseness

Lean body with no padding of concepts Claude already knows; every section (preflight, per-task loop, failure table, models) earns its place, and non-obvious Grok-specific facts like '--always-approve is required for headless runs' justify their inclusion.

5 / 5

Actionability

Fully executable guidance with copy-paste-ready commands for both POSIX and Windows (grok --prompt-file ... --output-format json --always-approve --max-turns 30 --cwd <repo>, grok --resume, git checkout -- .) and a concrete task spec template.

5 / 5

Workflow Clarity

Clearly sequenced per-task loop with an explicit, non-negotiable review gate, validation checkpoints (read the diff, run acceptance commands), a bounded fix-up feedback loop (max 2 rounds), and a revert fallback — satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

SKILL.md serves as a tight overview that signals one-level-deep references to the confirmed references/cli.md ('Full CLI details and verified behaviors: references/cli.md'), keeping detail out of the main body while remaining easy to navigate.

5 / 5

Total

20

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description written in third person that clearly states both what the skill does and when to invoke it, with concrete user-facing trigger phrases. It is concise, comprehensive, and distinct from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete orchestrator actions ('plans, writes the task specs, reviews every diff, and owns the result', 'Executes a Markdown implementation plan task-by-task') with comprehensive coverage of the delegation workflow.

5 / 5

Completeness

Explicitly answers both 'what' (orchestrates coding work by delegating to Grok Build headlessly, planning, reviewing, owning results) and 'when' (an explicit 'Use when user says:' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases users would actually say ('use grok', 'grok build', 'delegate to grok', 'have grok implement', 'send to grok', 'execute this plan with grok') including synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche (delegating to xAI's Grok Build CLI) with Grok-specific trigger phrases that are unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
sanjay3290/ai-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.