CtrlK
BlogDocsLog inGet started
Tessl Logo

grok

Delegate coding to xAI Grok Build CLI (features, PRs).

51

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/autonomous-ai-agents/grok/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with executable commands and a clean flags reference, but it is slightly repetitive, lacks validation feedback loops in its batch workflows, and keeps everything inline with no progressive disclosure to separate files.

Suggestions

Add an explicit verify-before-push checkpoint to the parallel-worktree and autonomous-build workflows (e.g. run tests / `gh pr checks` before opening PRs).

Dedupe the --no-auto-update / --always-approve / pty+tmux guidance so it lives once (flags table + rules) rather than recurring across sections.

Offload the detailed PR-review patterns and full flags reference into a references/ file referenced one level deep from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly operational with no padded conceptual explanation, but key advice (e.g. --no-auto-update, --always-approve, pty+tmux) repeats across the flags table, deep dive, pitfalls, and rules sections and could be tightened.

2 / 3

Actionability

Numerous copy-paste-ready `terminal(command="grok ...")` blocks, a complete flags table, config.toml, and concrete pitfall fixes provide fully executable guidance.

3 / 3

Workflow Clarity

Sequences like the Read-Only Audit pattern have explicit validation checkpoints, but batch/destructive flows (parallel worktree fixes, autonomous --always-approve builds) jump straight to push/PR with no validate→fix→retry loop, capping the score at 2.

2 / 3

Progressive Disclosure

Sections are well-organized, but with no bundle files the ~290-line SKILL.md keeps flags reference, PR-review, and worktree patterns inline rather than offloaded to one-level-deep references.

2 / 3

Total

9

/

12

Passed

Description

50%

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 identifies the tool and domain but is thin on concrete actions, natural trigger terms, and explicit use-when guidance, and it conflicts with near-identical sibling skills. It sits at the middle anchor across all dimensions.

Suggestions

Add a "Use when..." clause naming natural triggers (e.g. "Use when delegating coding, refactoring, bug fixes, or PR reviews to xAI Grok").

Expand concrete actions beyond "Delegate coding" to list refactoring, issue fixing, and code review so specificity reaches the score-3 anchor.

Differentiate from sibling skills (codex, claude-code) with a distinctiveness cue, e.g. noting Grok's subscription auth or no-git-repo operation.

DimensionReasoningScore

Specificity

Names the tool and domain plus two artifact types ("features, PRs"), but only one real verb ("Delegate coding") — not the multiple concrete actions of a score-3 anchor.

2 / 3

Completeness

It states what the skill does but has no "Use when..." clause; the when is only weakly implied by "(features, PRs)", capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

"coding" and "PRs" are natural terms, but the description leans on the product name and omits common variations users would say (refactor, fix issues, review code).

2 / 3

Distinctiveness Conflict Risk

Naming "xAI Grok Build CLI" gives a niche, but "Delegate coding" overlaps with the explicitly-mentioned sibling skills codex and claude-code, leaving real conflict risk.

2 / 3

Total

8

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.