CtrlK
BlogDocsLog inGet started
Tessl Logo

xai-models

xAI Grok model selection and capabilities guide. Use when choosing the right Grok model for your task, comparing model features, or optimizing costs.

64

Quality

80%

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 ./.claude/skills/xai-models/SKILL.md

The canonical home for this skill is xai-models in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable reference with concrete model IDs, pricing, executable code, and a clear selection decision tree, but it is a monolithic single-file guide that duplicates pricing/context data across tables and repeats identical API-call boilerplate per model. Splitting detailed profiles and matrices into reference files and deduplicating the repeated code blocks would improve both conciseness and structure.

Suggestions

Consolidate the three overlapping tables (Model Quick Reference, Detailed Profiles, and Context Window Comparison) — pricing and context window values appear in all three; a single canonical table plus short profiles would cut significant tokens.

Show the client setup ('OpenAI(api_key=os.getenv("XAI_API_KEY"), base_url="https://api.x.ai/v1")') once at the top and reduce the per-model examples to just the model ID and a one-line comment, eliminating six near-identical 'client.chat.completions.create' boilerplate blocks.

Move the Detailed Model Profiles, Capabilities Matrix, and Cost Optimization sections into a references/ file (e.g., MODELS.md), keeping SKILL.md as the quick-reference table plus decision tree with clearly signaled one-level-deep pointers.

DimensionReasoningScore

Conciseness

Pricing and context data are restated across three tables (Quick Reference, Detailed Profiles, and Context Window Comparison), and the near-identical 'client.chat.completions.create' boilerplate is repeated verbatim for each model. It is mostly efficient with no concept over-explanation (above anchor 2), but the duplication means it could be noticeably tightened, matching anchor 3.

3 / 5

Actionability

Fully executable, copy-paste-ready code throughout: complete client setup ('OpenAI(api_key=..., base_url="https://api.x.ai/v1")'), vision base64 encoding, batch prompts, and multi-model pipeline configs, plus concrete model IDs, prices, and a decision tree. This matches anchor 5's requirement of executable examples covering the common cases.

5 / 5

Workflow Clarity

The Model Selection Decision Tree gives a clear, unambiguous selection sequence covering all five models, and the Recommended Configurations section maps use cases to pipelines. It sits at anchor 4 rather than 5 because verification steps are minor gaps (e.g., checking model availability via 'client.models.list()' appears only at the end rather than as an explicit checkpoint), and above anchor 3 because the sequence is coherent with no risky operations requiring validation caps.

4 / 5

Progressive Disclosure

The body is a well-headered but monolithic ~250-line reference: detailed model profiles, the capabilities matrix, and cost-optimization strategies are all inline rather than split into one-level-deep reference files. This matches anchor 3 ('some structure but... content that should be separate is inline'); it is not anchor 4 because no bundle files exist and nothing is split out, and not anchor 2 because section organization is genuinely good.

3 / 5

Total

15

/

20

Passed

Description

82%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 description with an explicit and specific 'Use when...' trigger clause covering three natural use cases and a clearly-scoped niche (xAI Grok models). The only weakness is that the 'what' portion ('model selection and capabilities guide') leans slightly abstract instead of enumerating concrete actions.

DimensionReasoningScore

Specificity

The description names the domain ('xAI Grok model selection and capabilities guide') and a few relevant actions ('choosing the right Grok model', 'comparing model features', 'optimizing costs'), but 'selection and capabilities guide' is abstract rather than a concrete action verb list, matching anchor 3. It falls short of anchor 4 because the actions are user-needs framing rather than several specific concrete capabilities.

3 / 5

Completeness

It explicitly answers both what ('xAI Grok model selection and capabilities guide') and when ('Use when choosing the right Grok model... comparing model features, or optimizing costs') with concrete trigger phrases. This matches anchor 5 exactly; the 'when' clause is explicit and specific, so it exceeds anchor 4.

5 / 5

Trigger Term Quality

'Use when choosing the right Grok model for your task, comparing model features, or optimizing costs' contains natural phrases users would say, giving good keyword coverage. It is not anchor 5 because common variations like 'pricing', 'which Grok model should I use', or 'model comparison' are missing.

4 / 5

Distinctiveness Conflict Risk

'xAI Grok' is a clear niche with distinct triggers (model selection, feature comparison, cost optimization) and minimal conflict risk — related skills like auth, agent tools, or sentiment analysis would not match these triggers. Anchor 5 is the best fit.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.