Rebuild atmux cockpit sessions and per-team cage tmux topology.
npx skills add https://github.com/geoyws/atmux --skill cockpit-rebuild
Please help me install this Agent Skill. Skill: cockpit-rebuild Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/cockpit-rebuild Command: npx skills add https://github.com/geoyws/atmux --skill cockpit-rebuild
It solves drift and broken tmux/cage topology by recreating the canonical atmux cockpit session and all per-team cages in a deterministic, idempotent way.
atmux_cockpit session layout (including viewer windows) so operator attachments work reliably after reboot or accidental changes.team.json, registry rosters, and cockpit overlays; optionally cycles cages to recover from wedged or missing state.SHELL/PATH/TERM so tmux invocations don’t fail in minimal cron environments.Run cockpit-rebuild to restore the full cockpit-plus-cages topology: atmux cockpit rebuild.
High-intent search queries and answers about installing and using this skill.
Restoring a broken tmux session layout after a reboot requires deterministically rebuilding the canonical atmux cockpit topology. This idempotent reconciliation process recreates cockpit windows and per-team cages, eliminating drift and ensuring reliable operator attachments.
Normalizing per-team cage sockets and registry rosters requires applying idempotent state reconciliation to the atmux cockpit. This safely normalizes team.json configurations and registry overlays, optionally cycling cages to recover from wedged or missing state.
Fixing tmux invocations failing inside a minimal cron environment requires scrubbing orphan and stale cron entries. The rebuild process repairs the cron environment by prepending safe SHELL, PATH, and TERM variables so tmux commands execute reliably during scheduled recovery.
Yes, operational recovery supports optional cycle control when rebuilding team cages. You can use --no-cycle to prevent recreation or --force-cycle to force cage cycling, ensuring idempotent state reconciliation regardless of the severity of the wedged topology.
Yes, you can reconcile SQLite/WAL state alongside tmux operational recovery. The idempotent reconciliation process normalizes registry rosters and team.json configurations while rebuilding hierarchical level-resolved cage prefixes across the entire atmux cockpit topology.
Kord96Inspects Git worktree-backed Claude sessions and reports sync state and drift from main.
gizixValidate Tkinter form inputs with keystroke, focus-out, and submit checks.
ScientiaCapitalLoad and save PROJECT_CONTEXT.md files across Claude sessions.
johnnymo87Recreate missing tmux socket directories and signal the server to restore connections.