Skip to content

hoangsonww/Claude-Code-Agent-Monitor / plugins/ccam-workflows/skills/fleet-runs

fleet-runs

Verified

Summarize Workflow-tool fleet runs from the Agent Monitor — these fleets emit no hooks and are ingested from on-disk run journals. List recent runs with status and agents-per-run, then drill into a single run's per-agent detail. Reconciles against the live run-state endpoints. Use when reviewing Workflow() fleets rather than hook-instrumented interactive sessions.

Fleet Runs

Summarize Workflow-tool (Workflow()) fleet runs and drill into one run's agents.

Input

The user provides: $ARGUMENTS

  • Empty → list the most recent fleet runs.
  • A run ID → drill into that single run.
  • latest → drill into the most recent run.

These fleets emit no hooks; the dashboard ingests them from on-disk Workflow-tool run journals, so this data is independent of the hook event stream.

Data Sources

EndpointReturns
GET /api/workflows/runsList of ingested fleet run journals: run id, status, agent count, timing
GET /api/workflows/runs/{runId}One run in detail: per-agent status, timing, type, and outputs
GET /api/runLive run state across the fleet (current/active runs)
GET /api/run/{id}Live state for one run, to reconcile against the journal

Report Sections

1. Runs Overview (when listing)

Run IDStatusAgentsStartedDuration
Sort most recent first. Add a one-line status mix below (e.g. 8 runs: 5 completed, 2 running, 1 error).

2. Run Detail (when a run ID / latest is given)

From GET /api/workflows/runs/{runId}, reconciled with GET /api/run/{id}:

  • Header: run id, status, total agents, wall-clock duration.
  • Per-agent table:
    AgentTypeStatusDurationNotes
  • Call out the longest-running agent and any agent with an error/failed status.

3. Status & Health

Completion rate (completed / total agents), any stalled or errored agents, and whether the journal and the live run-state endpoint agree (flag drift if they do not).

Output

  • Markdown tables; status mix as a single summary line.
  • Durations in human units (e.g. 3m 04s).
  • Make explicit that these runs come from run journals (no hooks), so hook-derived metrics do not apply.
  • Cite only runs and agents returned by the API; never invent runs.
  • If there are no fleet runs, say so plainly.
  • If the dashboard is unreachable, tell the user to start it with npm start from the repo root.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall