cmux

MUST be read ANY time you interact with cmux in ANY way — listing/inspecting/creating/closing cmux workspaces, panes, or surfaces; reading or capturing pane/screen output; sending input or keys to a pane/surface; delegating to, polling, or checking on other agents running in cmux panes/surfaces; building or rearranging terminal layout; cmux browser automation; sending notifications/flashes/status/progress to the sidebar; editing cmux settings; or integrating an agent with cmux hooks. If your command starts with `cmux ` or touches a cmux workspace/pane/surface/agent, read this FIRST. Triggers on "cmux", "in this workspace", "this pane", "the other agent", "delegate to", "check on the agent", "send to the pane". macOS only (14.0+).

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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 unusually action-dense reference: executable command blocks, explicit ordering rules, and verification steps for fragile operations, with no tutorial padding. Its main weakness is progressive disclosure — it is a long monolithic file that signals a reference file (references/socket-api.md) that is not present in the bundle.

Suggestions

Create the referenced references/socket-api.md (or remove the dangling reference) so the one-level-deep pointer resolves.

Split the browser automation and markdown-viewer sections into separate reference files to shorten the main SKILL.md overview, keeping only quick-start snippets inline.

Move the keyboard-shortcuts and full CLI-help appendix to a reference file so the core body focuses on automation recipes.

Dimension	Reasoning	Score
Conciseness	The body is command-dense and assumes Claude's competence throughout (no tutorials explaining CLI/Unix sockets), with every warning earning its place; it avoids the concept-explanation padding that the score-1 and score-2 anchors penalize.	3 / 3
Actionability	Provides fully executable, copy-paste-ready command blocks with concrete flags and examples (e.g. 'cmux new-pane --workspace "$CMUX_WORKSPACE_ID" --type terminal --direction right --focus false' and 'cmux browser "$S" click e2 --snapshot-after'), matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Multi-step fragile workflows are explicitly sequenced with verification checkpoints — 'open → wait → snapshot → act → re-snapshot', numbered markdown-reuse steps ending in 'confirm stray pane is gone', and 'ORDER MATTERS: close-previous BEFORE open-new' — satisfying the 'explicit validation steps; feedback loops' anchor.	3 / 3
Progressive Disclosure	Sections are clearly headed and the one reference (references/socket-api.md) is signaled one-level-deep, but the ~225-line body keeps substantial API/browser/markdown detail inline and the referenced socket-api.md file does not exist in the bundle, fitting the 'some structure, could be better organized, content that should be separate is inline' anchor rather than a clean score-3 split.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 a strong, third-person trigger block that exhaustively enumerates concrete capabilities alongside explicit natural-language triggers and a clear activation condition. It is dense but every clause is a distinct capability or trigger rather than filler.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions verbatim — 'listing/inspecting/creating/closing cmux workspaces, panes, or surfaces; reading or capturing pane/screen output; sending input or keys' — matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2.	3 / 3
Completeness	Clearly answers both what (the long action list) and when ('If your command starts with `cmux ` or touches a cmux workspace/pane/surface/agent, read this FIRST' plus explicit triggers), satisfying the 'both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	Explicitly enumerates natural user phrases ('Triggers on "cmux", "in this workspace", "this pane", "the other agent", "delegate to", "check on the agent", "send to the pane"'), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The 'cmux' niche and its workspace/pane/surface/socket triggers are highly specific and unlikely to fire for an unrelated skill, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	12 / 12 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: mishatojk/davidskills
Commit: 66860fb

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.