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.
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill fleet-runs --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 | 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 | ## Report Sections ### 1. Runs Overview (when listing) | 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`). ### 2. Run Detail (when a run ID / `latest` is given) From `GET /api/workflows/runs/{runId}
- Input
- Data Sources
- Report Sections
- 1. Runs Overview (when listing)
- 2. Run Detail (when a run ID / latest is given)
- 3. Status & Health
- Output
What does the fleet-runs skill do?
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.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill fleet-runs --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.