Auto-invoked
Agent Orchestration
/resume-session
List in-flight Ouroboros sessions and show the commands needed to re-attach after MCP disconnect
Claude Code
$ npx -y skills add Q00/ouroboros --skill resume-session --agent claude-code
Codex
$ npx skills add Q00/ouroboros --skill resume-session -a codex -y
Cursor
$ npx skills add Q00/ouroboros --skill resume-session -a cursor -y
Gemini CLI
$ npx skills add Q00/ouroboros --skill resume-session -a gemini-cli -y
GitHub Copilot
$ npx skills add Q00/ouroboros --skill resume-session -a github-copilot -y
OpenCode
$ npx skills add Q00/ouroboros --skill resume-session -a opencode -y
Windsurf
$ npx skills add Q00/ouroboros --skill resume-session -a windsurf -y
SKILL.md
resume-session.SKILL.mdname: resume-session
description: "List in-flight Ouroboros sessions and show the commands needed to re-attach after MCP disconnect"
/ouroboros:resume-session
Recover in-flight Ouroboros sessions after an unexpected MCP server disconnect. The name avoids shadowing Claude Code's built-in `/resume`.
ooo resume-session [--all]
/ouroboros:resume-session
Instructions
1. Run with the active runtime's `run_shell` capability:
ouroboros resume --list
It reads the configured EventStore directly and read-only (no MCP server needed, nothing created or written) and lists `running` or `paused` sessions: the 20 most recent, or all with `--all`. `--list` prints the table and exits without the interactive prompt, which aborts when no terminal is attached. Exit code 2 means the EventStore exists but could not be read.
2. If sessions are listed, show the table and ask which session to work with (active runtime's `ask_user` capability). Each row carries the `session_id`, `exec_id`, and Seed id used below.
3. Give the matching re-attach path:
- Inspect persisted events (read-only, no MCP server):
ouroboros status execution <exec_id> --events
- Inspect interactively (read-only monitor; pick the session in the TUI):
ouroboros tui monitor
- Resume execution (needs the original Seed file; `--resume` takes the `session_id`):
ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>
Afterwards: `ooo evaluate` once the execution completes, or `ooo cancel <session_id>` if it is stuck.
If it reports "No in-flight sessions found", the execution completed, failed, or was cancelled, or the EventStore was never created; `ouroboros tui monitor` browses past sessions.
RFC #1392 State Breadcrumb Footer
End the final response with exactly one line `◆ <current state> → next: <recommended action>`. Derive the state from live session state via `ouroboros_session_status` when available, otherwise from this skill's actual outcome. Never use a linear `Step N of M` footer; when the next step is a real choice, list 2-3 options.
Read more
name: resume-session description: "List in-flight Ouroboros sessions and show the commands needed to re-attach after MCP disconnect"
/ouroboros:resume-session
Recover in-flight Ouroboros sessions after an unexpected MCP server disconnect. The name avoids shadowing Claude Code's built-in `/resume`.
ooo resume-session [--all] /ouroboros:resume-session
Instructions
1. Run with the active runtime's `run_shell` capability:
ouroboros resume --list
It reads the configured EventStore directly and read-only (no MCP server needed, nothing created or written) and lists `running` or `paused` sessions: the 20 most recent, or all with `--all`. `--list` prints the table and exits without the interactive prompt, which aborts when no terminal is attached. Exit code 2 means the EventStore exists but could not be read.
2. If sessions are listed, show the table and ask which session to work with (active runtime's `ask_user` capability). Each row carries the `session_id`, `exec_id`, and Seed id used below.
3. Give the matching re-attach path:
- Inspect persisted events (read-only, no MCP server):
ouroboros status execution <exec_id> --events
- Inspect interactively (read-only monitor; pick the session in the TUI):
ouroboros tui monitor
- Resume execution (needs the original Seed file; `--resume` takes the `session_id`):
ouroboros run workflow --orchestrator --resume <session_id> <seed.yaml>
Afterwards: `ooo evaluate` once the execution completes, or `ooo cancel <session_id>` if it is stuck.
If it reports "No in-flight sessions found", the execution completed, failed, or was cancelled, or the EventStore was never created; `ouroboros tui monitor` browses past sessions.
RFC #1392 State Breadcrumb Footer
End the final response with exactly one line `◆ <current state> → next: <recommended action>`. Derive the state from live session state via `ouroboros_session_status` when available, otherwise from this skill's actual outcome. Never use a linear `Step N of M` footer; when the next step is a real choice, list 2-3 options.
Ships withouroboros
Agent OS: the agent gets smarter on its own. We just hold the line: Interview-gated, staged evaluation, budgeted evolution loop. MCP server, 14 runtimes: Claude Code, Codex CLI, Gemini CLI, OpenCode, Copilot, Kiro and more.
6.4k26 skills22 agents1 MCP
Stars on GitHub
Momentum
- stars in total
- 6.4k
Other skills on ouroboros.
More skills from other plugins.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
@paperclipaiInstall Skilladr-create
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
@ruvnetInstall SkillQuestions about resume-session.
- Which coding agents can use resume-session?
- resume-session installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.