Pin the current cmux workspace to the done lane with `cmux workspace status set done` once a session goal is reached and verified. Use at the end of a work session running inside a cmux terminal, right before the final response; skip when work is blocked, handed off, awaiting user input, or when nothing was changed.
97%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
cmux shows a status lane per workspace in its left sidebar. The lane is normally inferred from live signals (agent needs input > agent running > open PR > all PRs merged or closed > dirty git tree > todo), so a finished session whose tree is still dirty keeps reading as working. Pinning done is what makes the sidebar reflect a reached goal.
Invoke once, immediately before the final response of a session in which all of these hold:
Do not invoke when:
The command targets the caller's workspace through CMUX_WORKSPACE_ID. Outside a cmux terminal that variable is unset and cmux falls back to whichever workspace is focused, which is the wrong one. Check first and do nothing when it is empty:
[ -n "$CMUX_WORKSPACE_ID" ] || exit 0
cmux workspace status set doneExpected output:
done
inferred: <lane>
override: done (auto-clears when inferred moves off <lane>)cmux on PATH), ignore it. Do not retry, do not target another workspace, and do not mention it in the final response unless the user asked about workspace status.set accepts todo, working, needs-attention, review, done, plus auto and none to clear a pin. Only done belongs in this flow; clear a premature pin by hand with cmux workspace status set auto.cmux workspace status with no arguments prints the effective lane, the inferred lane, and the current override — use it to confirm a pin landed.phatblat/dotfiles
4d65cab
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.