Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →josstei/session-management
Manages orchestration session state, tracking, and resumption
Passed 16 of 20 test cases with the skill, and 6 of 20 without it.
and 14 more in the full report
11 fixed7 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are resuming an interrupted express workflow session where workflow_mode is express and the single phase is marked in_progress. What is the correct next step?
| Checked | Without skill | With skill |
|---|---|---|
| Re-delegates to the agent listed in the agents array with the same scope | Missed | Passed |
The instructions your model reads when the skill loads.
Activate this skill for all session state operations during Maestro orchestration. This skill defines the protocols for creating, updating, resuming, and archiving orchestration sessions.
When MCP state tools are available, prefer them for state operations:
initialize_workspace, create_session, update_session, transition_phase, get_session_status, archive_session) — structured I/O, atomic operations.write_file/replace directly on state files — when MCP tools are not in the available tool list.write-state.js, read-state.js) — remain available but are not the recommended path.Detection: check whether MCP state tools appear in your available tools. If they do, use them. If they do not, use write_file/replace.
Maestro hooks maintain a separate, transient state directory under ${MAESTRO_HOOKS_DIR:-<os.tmpdir()>/maestro-hooks-<uid>}/<session-id>/ that is distinct from orchestration state in <MAESTRO_STATE_DIR>:
| Concern | Orchestration State | Hook State |
|---|---|---|
| Location | <MAESTRO_STATE_DIR>/state/ | ${MAESTRO_HOOKS_DIR:-<os.tmpdir()>/maestro-hooks-<uid>}/<session-id>/ |
| Lifecycle | Created at execution setup, archived in Phase 4 | Directory created by the session-start hook when an active session exists; active-agent file written by the pre-delegation hook and cleared by the post-delegation hook; stale directories pruned by both session-start and pre-delegation hooks |
| Contents | Session metadata, phase tracking, token usage, file manifests | Active agent tracking file (active-agent) |
| Persistence | Survives session restarts (supports /maestro:resume) | Ephemeral — lost on session end or system reboot |
| Managed by | Orchestrator via session-management skill | The runtime's pre-delegation and post-delegation hooks |
The pre-delegation hook prunes stale hook state directories older than 2 hours to prevent accumulation from abnormal session terminations.
The orchestrator does not read or write hook-level state directly. It interacts only with <MAESTRO_STATE_DIR> paths. The two state systems are independent and serve different concerns.
For Standard workflow, create a new session at execution setup after the design document and implementation plan are approved and the execution mode gate has resolved. For Express workflow, create a session after the structured brief is approved (see Express Workflow section in the orchestrator template).
YYYY-MM-DD-<topic-slug>
Where:
YYYY-MM-DD is the orchestration start date<topic-slug> is a lowercase, hyphenated summary matching the design document topictest cases passed, vs 6 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.