Agent skill · ma08
zellij-cross-session-orchestration
Use repo-managed zellij helpers from ~/pro/botfiles to inspect, message, and launch parallel coding-agent task sessions.
What it needs
About 7k tokens when loaded.
What this skill does
Zellij Cross-Session Orchestration Use this skill when the user wants to work with their zellij-based coding-agent workflows from ~/pro/botfiles, especially for detached task launches or cross-session coordination. Trigger conditions Load this skill when the user asks to: start a side task in another zellij session inspect another live task/session send a message into another live zellij-backed agent session use repo-managed work- / zellij orchestration conventions from ~/pro/botfiles Source of truth Prefer the repo-managed helpers and docs in ~/pro/botfiles: README.md docs/cross-session-orchestration-contract.md codex/skills/start-zellij-session-for-task/SKILL.md codex/skills/cross-session-context/SKILL.md codex/skills/cross-session-message/SKILL.md Core commands 1) Launch a detached side-task session Use when the user wants a second coding-agent run without taking over the current terminal. Optional target override: Raw Codex fallback for hosts without the App Server notification wrappers: Supported targets from the botfiles docs: here (default) ml arya agent Behavior to preserve: resolves tracker/slug context with shared task-status tooling creates a detached zellij session named from the resolved task slug renames the initial tab to [TRACKER-ID] when available launches Codex through codex-app-notify-session into a real spawned pane in the detached session (not only via options --default-shell) so attach/dump-screen can verify visible Codex UI and requestuserinput prompts can notify via the App Server proxy clears inherited CODEX metadata before starting child Codex seeds the child session with $start-new-task <original input> uses codex-app-notify-session --dangerously-bypass-approvals-and-sandbox by default; use --no-codex-app-notify only as an explicit raw-Codex fallback fails early for remote targets if the project root is not present there supports --dry-run for inspection-only requests on current Linux/Zellij behavior, prefer a two-step launch pattern for d …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills ma08/zellij-cross-session-orchestration