hoangsonww/fleet-runs
> 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.
npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor --skill fleet-runs
Summarize Workflow-tool (Workflow()) fleet runs and drill into one run's agents.
The user provides: $ARGUMENTS
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.
| Endpoint | Returns |
|----------|---------|
| GET /api/workflows/runs | List 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/run | Live run state across the fleet (current/active runs) |
| GET /api/run/{id} | Live state for one run, to reconcile against the journal |
| Run ID | Status | Agents | Started | Duration |
|--------|--------|--------|---------|----------|
Sort most recent first. Add a one-line status mix below (e.g. 8 runs: 5 completed, 2 running, 1 error).
latest is given)From GET /api/workflows/runs/{runId}, reconciled with GET /api/run/{id}:
| Agent | Type | Status | Duration | Notes |
|-------|------|--------|----------|-------|
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).
3m 04s).npm start from the repo root.Take hoangsonww/fleet-runs from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.