crush-config

Use when the user needs help configuring Crush — writing crushrc (the Bash config format) or crush.json, setting up providers, models, LSPs, MCP servers, hooks, skills, permissions, or changing Crush behavior.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%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 comprehensive, executable configuration reference that stays lean and assumes competence while providing copy-paste-ready commands and a clear load/priority model. Its main limitation is that everything lives in one ~370-line file with no progressive split into bundled references.

Suggestions

Move the Hooks runtime details (stdin/env/exit-code/decision-aggregation) and the Legacy JSON format + crushrc↔crush.json mapping tables into separate reference files under ./references/, keeping SKILL.md as a concise overview with one-level-deep links.

Tighten the occasional prose asides (e.g. 'Because it is real Bash you get includes, secrets, conditionals, and variables for free') into terser statements to reclaim tokens.

Add a short 'configuring Crush' quick-start workflow at the top (create crushrc → add provider → set model → reload) so first-time users get a sequenced entry point before the command reference.

Dimension	Reasoning	Score
Conciseness	Dense, reference-style content that assumes Claude's competence (no explanations of Bash, JSON, or MCP) with lean command signatures and flag tables; a few prose asides like 'Because it is real Bash you get...for free' could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready examples throughout — e.g. 'provider add deepseek --type openai-compat --base-url ... --api-key "${DEEPSEEK_API_KEY:?...}"' and 'mcp add github --type http --url ... --header Authorization "Bearer $GH_PAT"' — covering the common cases concretely.	5 / 5
Workflow Clarity	Load order, config priority, and merge/conflict behavior are sequenced clearly, and each config task is an unambiguous single builtin call with examples; no explicit validate→fix→retry loop is present, but none is required for non-destructive config editing.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and internal anchor navigation ('[Legacy JSON format](#legacy-json-format)', '[Hooks runtime](#hooks-runtime)'); no bundle files exist so all content is inline, and sizable subsections like the full flag reference and hooks runtime could conceivably be split out, leaving minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

92%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, third-person description that pairs an explicit 'Use when' trigger with a comprehensive enumeration of the config surfaces it covers. It is concrete, distinct, and free of vague fluff.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete configuration surfaces — 'writing crushrc (the Bash config format) or crush.json, setting up providers, models, LSPs, MCP servers, hooks, skills, permissions, or changing Crush behavior' — giving comprehensive coverage of concrete actions.	5 / 5
Completeness	Explicitly answers both: the 'what' (writing crushrc/crush.json, setting up the listed entities) and the 'when' via the opening 'Use when the user needs help configuring Crush' trigger clause.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('configuring Crush', 'setting up providers, models, LSPs, MCP servers, hooks, skills, permissions', 'crushrc', 'crush.json') with verb synonyms, though a few common user phrasings like 'add an MCP server' or 'setup' are not present.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to Crush-specific configuration with named artifacts (crushrc, crush.json) and Crush entities, giving it a clear niche with minimal overlap risk against generic skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: charmbracelet/crush
Path: internal/skills/builtin/crush-config/SKILL.md
Commit: 8f63ee5

Reviewed: about 6 hours ago

Table of Contents

Discovery Implementation Validation

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.