Skip to content
Development
Skill

/status

Summarize the active Maestro session without mutating state

From plugin
maestro-orchestrate
45359 skills72 agents4 hooks1 MCP
Install
$ npx -y skills add josstei/maestro-orchestrate --skill status --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/status

Context preview

The summary Claude sees to decide when to auto-load this skill.

Summarize the active Maestro session without mutating state

SKILL.md

status.SKILL.md
name: status
description: Summarize the active Maestro session without mutating state

Maestro Status

Call `get_skill_content` with resources: ["architecture"].

Workflow

1. Read the active session using MCP state tools if available; otherwise fall back to scripts or direct file read 2. Report session ID, creation timestamp, workflow mode, and overall status 3. Show phase breakdown: completed phases with timestamps, current active phase, pending phases, and failed phases with error summaries 4. Report file manifest (files created, modified, deleted), token usage by agent, and unresolved errors

Constraints

  • This is read-only; do not mutate state, archive sessions, or continue execution
  • If no active session exists, say so plainly
Ships withmaestro-orchestrate

Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone

Get the whole plugin