Content
81%Weight 40%Scale 1-5Reviews 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.
| Dimension | Reasoning | Score |
|---|---|---|
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 |