CtrlK
BlogDocsLog inGet started
Tessl Logo

grok-build

Reference and workflow guidance for the Grok Build CLI (`grok`), including interactive and headless runs, authentication, sessions, worktrees, permissions, sandboxing, MCP servers, plugins, inspection, updates, and automation output. Invoke only when the user explicitly requests the `grok-build` skill, explicitly asks to use Grok Build CLI, or an already-selected workflow requires Grok Build; do not invoke for general coding, generic shell tasks, or other agent CLIs.

76

Quality

95%

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.

The content is well-structured, executable, and concise, with strong validation checkpoints around destructive operations and clean one-level-deep reference disclosure. It exemplifies a focused CLI skill that respects both token budget and Claude's competence.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, opening with a single orienting line and then tight command sections; it avoids explaining what a CLI or sandbox is and every token earns its place.

5 / 5

Actionability

Provides concrete, copy-paste-ready bash commands for login, headless runs, sessions, worktrees, and diagnostics, covering the common cases with exact flags.

5 / 5

Workflow Clarity

Sequences local-evidence inspection before advice, distinguishes permission vs sandbox controls, and includes explicit validation/safety checkpoints (dry-run before worktree deletion, verifying destructive commands) with feedback-loop guidance for risky operations.

5 / 5

Progressive Disclosure

SKILL.md is a concise overview with two clearly signaled, one-level-deep references ([references/cli-reference.md], [references/workflows.md]) that exist in the bundle; bulk detail is split out and navigation is explicit.

5 / 5

Total

20

/

20

Passed

Description

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

The description is comprehensive, specific, and explicit about both capabilities and invocation triggers, with strong guardrails against mis-invocation. Its only minor gap is slightly thinner coverage of casual synonyms a user might say versus the precise product name.

DimensionReasoningScore

Specificity

Enumerates concrete actions and surface area — interactive/headless runs, authentication, sessions, worktrees, permissions, sandboxing, MCP servers, plugins, inspection, updates, automation output — rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' (reference/workflow guidance for the grok CLI) and 'when' ('Invoke only when the user explicitly requests...') with concrete trigger guidance and explicit anti-triggers.

5 / 5

Trigger Term Quality

Includes natural trigger phrases ('use Grok Build CLI', 'grok-build skill', 'workflow requires Grok Build') but is lighter on common synonyms/extensions a user might casually say; coverage is good but not exhaustive.

4 / 5

Distinctiveness Conflict Risk

Scopes tightly to the Grok Build CLI and explicitly excludes general coding, generic shell tasks, and other agent CLIs, giving it a clear niche with minimal conflict risk.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
XiaomiMiMo/MiMo-Code
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.