CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

grok-media

xAI Grok image and video generation guide covering authentication, endpoints, prompt structure, image editing, reference-image video, and async polling.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/grok-media/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is an efficient, well-structured, provider-specific API guide with concrete endpoints, fields, statuses, pricing, and fit guidance. Its main gaps are the lack of an example request/response pair, an unstated request_id source in the polling workflow, and slight duplication of the edit-prompt guidance.

Suggestions

Add one minimal example request and response per API (e.g., a JSON body for 'POST /images/generations' and the shape of the 'POST /videos/generations' response) to make the guidance copy-paste ready.

State where the polling 'request_id' comes from (the submit response) and suggest a poll interval or retry policy for the 'failed'/'expired' states to close the workflow validation gap.

Merge the duplicated edit-prompt guidance in 'Image prompting' and 'Grok-Specific Prompt Guidance → Images' into a single section.

DimensionReasoningScore

Conciseness

The body is bullet-style and restricted to provider-specific facts (endpoints, field names, statuses, pricing) with no explanation of concepts Claude already knows. Minor trimming is possible — the edit-prompt guidance appears twice ('describe only the intended change and preserve everything else implicitly' vs 'keep the rest of the image stable by omission') — which fits anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than anchor 5.

4 / 5

Actionability

Concrete guidance throughout: exact endpoints ('POST /images/generations', 'GET /videos/{request_id}'), env var 'XAI_API_KEY', exact request field names, placeholder syntax '<IMAGE_1>', '<IMAGE_2>', and explicit terminal statuses. Minor gaps keep it below anchor 5: there is no example request/response body and the source of the polling 'request_id' is never stated, so it is not fully copy-paste ready.

4 / 5

Workflow Clarity

The video workflow has a clear submit-then-poll sequence with explicit validation checkpoints ('status == "done"', 'failed', 'expired' handled explicitly) plus a Failure Handling section for error propagation. Minor gaps (no poll interval, retry guidance, or feedback loop for error recovery) place it at anchor 4 rather than anchor 5's 'explicit validation steps; feedback loops for error recovery'.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the ~120-line body is well-organized with clear sections (Models, Image API, Video API, Pricing, Good Fits, Weak Fits, Failure Handling). Because it exceeds 50 lines, the simple-skill exception for a 5 does not apply, and some content (pricing detail, prompt guidance) could live in reference files; this fits anchor 4 ('good structure; most content is appropriately placed; minor organization gaps') rather than anchor 3, since nothing is buried or misplaced.

4 / 5

Total

16

/

20

Passed

Description

70%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 specific, provider-scoped, and clearly distinguishable from other media-generation skills, with good natural keyword coverage. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the 'when to use' question unanswered and caps completeness.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when generating or editing images and videos with xAI Grok models, or when the user mentions Grok, xAI media generation, or reference-image video') to answer the 'when' half of completeness.

Include natural trigger variations users actually say, such as 'text-to-video', 'image-to-video', and 'reference images', to broaden trigger term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'image and video generation', 'image editing', 'reference-image video', 'async polling', 'authentication', 'endpoints' — with only minor coverage gaps (video modes like text-to-video/image-to-video are not named as actions). It lists multiple specific items rather than only 1-2, matching the anchor 4 example, but is not comprehensive enough for anchor 5.

4 / 5

Completeness

The 'what' is clear ('xAI Grok image and video generation guide covering authentication, endpoints, prompt structure, image editing, reference-image video, and async polling') but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, matching anchor 3 ('clear what but when is missing or only weakly implied').

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'image generation', 'video generation', 'image editing', 'reference-image video', plus provider names 'xAI' and 'Grok'. A few natural variations are missing ('text-to-video', 'image-to-video', 'reference images', file-format mentions), which fits anchor 4's 'good keyword coverage; a few natural terms missing' rather than anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

'xAI Grok' names a specific provider niche with distinct triggers, and the capability list (reference-image video, async polling) is unlikely to overlap with generic image/video skills or other providers' skills. This matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk') rather than anchor 4, which requires some overlap risk with closely related skills.

5 / 5

Total

16

/

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

calesthio/OpenMontage

Path

.agents/skills/grok-media/SKILL.md

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.