cmux

End-user control of cmux topology and routing (windows, workspaces, panes/surfaces, focus, moves, reorder, identify, trigger flash). Use when automation needs deterministic placement and navigation in a multi-pane cmux layout.

Quality

93%

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

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.

A concise, highly actionable command reference with excellent progressive disclosure into real bundle files. The main gap is the absence of explicit validation/verification guidance for the mutating topology commands.

Suggestions

Add a brief note on verifying mutating operations (e.g., re-run `cmux list-pane-surfaces` or check `--json` output) after move-surface/reorder-surface to confirm the intended layout.

For workspace-action and config edits, mention a quick check step (e.g., `cmux identify --json` or listing the workspace) to confirm the change took effect.

Consider a one-line ordering hint for common multi-command flows (new-split → move-surface → focus) so the catalog doubles as a sequenced recipe.

Dimension	Reasoning	Score
Conciseness	Lean, command-dense body with no over-explanation of concepts Claude already knows; every section (fast start, handle model, settings) earns its place.	5 / 5
Actionability	Provides copy-paste-ready `cmux ...` commands covering the common cases (identify, list, new-split, move-surface, reorder-surface, workspace-action, trigger-flash) plus concrete config paths.	5 / 5
Workflow Clarity	Presented as a usable command catalog with clear sections, but it is a flat reference rather than a sequenced multi-step workflow; batch/mutating commands like move-surface and reorder-surface lack explicit verification steps.	4 / 5
Progressive Disclosure	Clear overview body with a well-signaled, one-level-deep references table; all four referenced files exist (handles-and-identify.md, panes-surfaces.md, trigger-flash-and-health.md, windows-workspaces.md) and cross-skill links are clearly labeled.	5 / 5
	Total	19 / 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, specific description that clearly conveys both capability and trigger conditions with a distinct niche. Trigger-term naturalness could be slightly broader with simpler synonyms alongside the technical phrasing.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — 'windows, workspaces, panes/surfaces, focus, moves, reorder, identify, trigger flash' — giving comprehensive coverage of the topology/routing action space.	5 / 5
Completeness	Explicitly states both what it does ('control of cmux topology and routing') and when to use it ('Use when automation needs deterministic placement and navigation in a multi-pane cmux layout').	5 / 5
Trigger Term Quality	Includes natural trigger phrases like 'deterministic placement and navigation in a multi-pane cmux layout', but the language is somewhat technical and lacks common synonyms or simpler variations users might say.	4 / 5
Distinctiveness Conflict Risk	The 'cmux' niche with specific topology/routing triggers is clearly distinct from other skills and unlikely to fire for the wrong one.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 4 suspicious	Warning

	Total	15 / 16 Passed

Repository: basicmachines-co/basic-memory
Path: .agents/skills/cmux/SKILL.md
Commit: 194afe1

Reviewed: 7 days 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.