| Skill | Added | Review |
|---|---|---|
cmux-connector __solutions/cmux-connector/SKILL.md Connect to already-running cmux panes on the remote Mac (built by cmux-fanout) and inject caller-supplied work into them from Windows — one runspace per pane, fire-and-forget or run-and-wait, broadcast or per-pane commands, ShellManaged/CallerManaged/RawInteractive profiles. Use AFTER cmux-fanout has built a grid, when you want to run/administer commands across those existing panes concurrently or steer agent REPLs in them. Requires PowerShell 7.1+, key-auth SSH to the Mac, and a pane map written by cmux-fanout. NOT for building panes (use cmux-fanout), local Windows grids (use psmux-connector), or in-process parallelism (use the Task tool). | 76 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: a4e208e | |
cmux-fanout __solutions/cmux-fanout/SKILL.md 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. | 73 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: a4e208e |