CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cmux-fanout

Fan out agent workspaces on a remote Mac's cmux from Windows — create a cmux workspace with N split panes by running one `ssh <host> cmux <verb>` per operation, launch agent REPLs (claude, codex, any CLI) in each pane, wait for readiness, and return a pane map for downstream skills. Use when the user wants to build an agent grid on the Mac's cmux, "fan out N agents on the mac", spin up remote cmux workspaces/panes, or inspect (status) and tear down grids built this way. Requires PowerShell 7.1+, key-auth SSH to the Mac, cmux running there, and the one-time socket-gate step (see setup.md). NOT for injecting into or reading existing panes conversationally (future cmux-connector), local Windows pane grids (use psmux-fanout), or driving cmux's embedded browser.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 dense, well-organized operational skill: concrete PowerShell commands, an explicit pane-map contract, and outstanding failure-mode documentation with per-error fixes. The main gaps are placeholder paths in the quickstart/teardown commands and references to bundle files (setup.md, scripts, tests, lib) that cannot be verified against the bundle as provided.

Suggestions

Replace the '$env:USERPROFILE\...\cmux-fanout' placeholder with an explicit way to resolve the skill directory (e.g., a comment stating the skill root is the directory containing SKILL.md) so every quickstart line is copy-paste ready.

Trim the transport paragraph's comparative justification ('nothing is batched or pipelined the way a persistent RPC channel would be') to a single statement of the rule — one ssh call per operation, dependent splits run sequentially.

Include the bundle files (setup.md, doctor.ps1, fanout.ps1, status.ps1, teardown.ps1, lib\\CmuxRpc.psm1, tests\\smoke\\) with the skill, or note in SKILL.md where they live, so the referenced paths are verifiable rather than dangling in the shipped bundle.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (no SSH/tmux primer), but the transport paragraph's justification ('nothing is batched or pipelined the way a persistent RPC channel would be') and the inline enumeration of all twelve verbs are slightly more explanatory than strictly needed. Efficient with minor trimmable instances — anchor 4, not the every-token-earns-its-place anchor (5), and well above noticeably-verbose (2) or mostly-efficient-with-real-excess (3).

4 / 5

Actionability

Quickstart gives concrete executable commands ('& "$fan\fanout.ps1" -Panes 4 -Command claude', '-Commands @(\'claude\',\'codex\',\'claude\',\'opencode\')') and a concrete pane-map JSON contract, but '$env:USERPROFILE\...\cmux-fanout' and the teardown '-MapFile "<project>\...cmux-fanout-<name>.json"' contain placeholders that keep it from being fully copy-paste ready. Mostly executable with minor gaps — anchor 4, not the fully-executable anchor (5).

4 / 5

Workflow Clarity

Clear sequence with explicit validation: 'doctor.ps1 — preflight, run this first', first-run smoke test ('tests\\smoke\\03-discovery.ps1'), status check after transport failures ('check status.ps1 before retrying'), and a five-entry error taxonomy (CMUX_GATE/TRANSPORT/OP/SHAPE, panes-never-ready) each paired with a fix — genuine feedback loops for error recovery, matching anchor 5 rather than most-checkpoints-present (4).

5 / 5

Progressive Disclosure

Good structure with clearly signaled, one-level-deep references ('full steps in setup.md', 'setup.md, section 2', doctor/fanout/status/teardown scripts, smoke test, lib\\CmuxRpc.psm1) and setup detail appropriately deferred. However, none of the referenced bundle files are present in the provided bundle to verify they exist, and the ~74-line body sits above the simple-skill threshold — good structure with minor organization gaps, anchor 4 rather than fully-verified clear navigation (5).

4 / 5

Total

17

/

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 lifecycle actions, a quoted natural trigger phrase with synonyms, explicit what/when guidance, and proactive negative boundaries that disambiguate sibling skills. Third-person voice is used throughout with no fluff or over-claims.

DimensionReasoningScore

Specificity

Quotes 'create a cmux workspace with N split panes', 'launch agent REPLs (claude, codex, any CLI) in each pane', 'wait for readiness', 'return a pane map', plus status and teardown — multiple concrete actions covering the full create/monitor/teardown lifecycle, matching the comprehensive-coverage anchor rather than the several-actions-with-gaps anchor (4).

5 / 5

Completeness

Explicitly answers both what ('create a cmux workspace with N split panes… return a pane map for downstream skills') and when ('Use when the user wants to build an agent grid…') with concrete trigger phrases, and adds requirements and NOT-for boundaries — clearly the both-answered-with-triggers anchor, not the 'when could be more specific' anchor (4).

5 / 5

Trigger Term Quality

Includes the literal natural user phrase '"fan out N agents on the mac"' plus synonyms 'build an agent grid', 'spin up remote cmux workspaces/panes', and 'inspect (status) and tear down', giving comprehensive natural-term coverage rather than just good coverage with a few missing (4).

5 / 5

Distinctiveness Conflict Risk

A clear niche (remote Mac cmux driven from Windows via SSH) with explicit disambiguation — 'NOT for injecting into or reading existing panes conversationally (future cmux-connector), local Windows pane grids (use psmux-fanout), or driving cmux's embedded browser' — minimal conflict risk, exceeding the minor-overlap anchor (4).

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

KennethJefferson/cmux_test

Path

__solutions/cmux-fanout/SKILL.md

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.