Check an execution session's status and, on request, measure drift from the Seed goal.
/ouroboros:ouroboros-status [session_id]
Ouroboros tools may be deferred, and a schema loaded on one turn can unload by the next. Immediately before each ouroboros_* call, load it with the active runtime's tool-discovery capability: "+ouroboros session status" for ouroboros_session_status and ouroboros_measure_drift. A call whose schema is not loaded fails with "Invalid tool parameters". If the tool is already callable, discovery is a no-op and an empty result is expected. Use the fallback only when the tool is genuinely absent.
session_id, else the most recent one in the conversation, else ask the user.ouroboros_session_status MCP tool:```
Tool: ouroborossessionstatus
Arguments:
session_id:
```
ouroboros_measure_drift:```
Tool: ouroborosmeasuredrift
Arguments:
session_id:
current_output:
seed_content:
constraint_violations: [] (any known violations)
current_concepts: [] (concepts in current output)
```
EXCEEDED), warn and suggest ooo interview to re-clarify or ooo evolve to course-correct; otherwise suggest continuing with ooo run or ooo evaluate.Tell the user session tracking needs the Ouroboros MCP server (ooo setup), and that without it they can compare the implementation against the Seed by hand.
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.