This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.
session-management from josstei/maestro-orchestrate is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
Manages orchestration session state, tracking, and resumption.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Session Management Skill
Activate this skill for all session state operations during Maestro orchestration. This skill defines the protocols for creating, updating, resuming, and archiving orchestration sessions.
## State Access Protocol
When MCP state tools are available, prefer them for state operations:
- **Preferred**: MCP tools (`initialize_workspace`, `create_session`, `update_session`, `transition_phase`, `get_session_status`, `archive_session`) — structured I/O, atomic operations.
- **Fallback**: `write_file`/`replace` directly on state files — when MCP tools are not in the available tool list.
- **Legacy**: `node <runtime-script-root>/read-active-session.js` (used by command shell blocks to inject state before the first turn) / `read-state.js <relative-path>` — 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`.
## Hook-Level Session State
…
The line at the top of this page pins the label git:20261019.2f1c8b3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_hdk7ov6wthmwrnfl
GET https://markdownregistry.com/api/v1/resolve?ref=josstei/maestro-orchestrate/session-management
GET https://markdownregistry.com/api/v1/blob/d1685c764b685ccd9187e8c105f64772ef47d1d0aa800f7095263725aadddb54
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
josstei/maestro-orchestrate · antigravity/skills/a11y-audit/SKILL.md · Run a Maestro-style accessibility audit for WCAG compliance, ARIA usage, keyboard navigation, and screen reader…
josstei/maestro-orchestrate · antigravity/skills/compliance-check/SKILL.md · Run a Maestro-style regulatory compliance review for GDPR/CCPA, cookie consent, data handling, and licensing
josstei/maestro-orchestrate · antigravity/skills/execute/SKILL.md · Execute an approved Maestro implementation plan using the shared session-state contract
josstei/maestro-orchestrate · antigravity/skills/orchestrate/SKILL.md · Run the full Maestro workflow for complex engineering tasks that need a mandatory design dialogue, approved…
josstei/maestro-orchestrate · antigravity/skills/perf-check/SKILL.md · Run a Maestro-style performance assessment for hotspots, regressions, and optimization planning
athola/claude-night-market · plugins/sanctum/skills/session-management/SKILL.md · Manages Claude Code sessions with naming, checkpointing, and resume strategies. Use when organizing long-running work…
