CtrlK
BlogDocsLog inGet started
Tessl Logo

cmux-settings

View and edit cmux settings in ~/.config/cmux/cmux.json. Use when the user wants to change cmux preferences (appearance, sidebar, notifications, automation, browser, shortcuts), set a value by JSON path, validate the file, open it in an editor, or look up which keys cmux recognizes. Triggers on '/cmux-settings', 'change cmux setting', 'set <something> in cmux', 'cmux config', 'cmux.json', or 'rebind a cmux shortcut'.

77

Quality

96%

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

93%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 highly actionable and token-efficient with clean structure and well-signaled references. The only gap is that the validation feedback loop is implied rather than an explicit step in the workflow.

Suggestions

Add an explicit feedback step to the Workflow, e.g. after 'cmux-settings validate': 'If unknown keys are flagged, remove or correct them and re-run validate before reporting success.'

Show one validate-failure example inline (unknown key → unset → re-validate) so the recovery path is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it states facts ('JSONC', 'file watcher applies changes on save, no restart') without explaining JSON or config concepts, and every section earns its tokens.

5 / 5

Actionability

Provides a full command table plus copy-paste-ready examples like 'cmux-settings set sidebarAppearance.matchTerminalBackground true' and 'cmux-settings set shortcuts.bindings.newTab ["ctrl+b","c"]' covering common cases.

5 / 5

Workflow Clarity

The four-step workflow includes an explicit 'Read back and cmux-settings validate' checkpoint, but the validate→fix→re-validate feedback loop for failed validation is only implied in the Rules section rather than spelled out in the sequence.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with one-level-deep, clearly linked references (references/all-keys.md, references/shortcut-actions.md) and a real bundled helper script, all verified to exist in the bundle.

5 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: concrete actions, comprehensive natural trigger phrases, both 'what' and 'when' explicitly stated, and a distinct cmux-specific niche in third-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'View and edit', 'set a value by JSON path', 'validate the file', 'open it in an editor', 'look up which keys cmux recognizes' — with comprehensive coverage of the domain.

5 / 5

Completeness

Clearly answers 'what' (view/edit cmux settings in cmux.json plus enumerated actions) and 'when' (explicit 'Use when' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Explicit 'Triggers on' clause covers natural phrases and synonyms users would say: '/cmux-settings', 'change cmux setting', 'set <something> in cmux', 'cmux config', 'cmux.json', 'rebind a cmux shortcut'.

5 / 5

Distinctiveness Conflict Risk

Targets a clear cmux-specific niche with distinctive triggers ('cmux.json', '/cmux-settings'), making overlap with unrelated skills minimal.

5 / 5

Total

20

/

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
basicmachines-co/basic-memory
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.