concurrency-report
Report concurrency and parallelism for a session — how many agents ran in parallel, concurrency-lane utilization, peak parallel width, and serialization bottlenecks (sequential chains that could have run as parallel lanes) — using the Agent Monitor workflow intelligence API. Use when checking whether a multi-agent session used parallelism efficiently.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill concurrency-report --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.
# Concurrency Report Report on parallel execution for one Claude Code session: lanes, peak width, utilization, and where work serialized. ## Input The user provides: **$ARGUMENTS** A session ID. If empty, fetch `GET /api/sessions?limit=1` and report on the most recent session, stating which one. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/workflows/{sessionId}` | The `concurrency` dataset (overlapping agent execution lanes with start/end timing) and the `complexity` dataset (numeric score from depth, breadth, and tool diversity) | ## Report Sections ### 1. Parallelism Summary From `concurrency`: number of distinct lanes, peak parallel width (max agents running simultaneously), and total agents. Pair with the `complexity` score to judge whether the parallelism matched the work's size. `Lanes: N · Peak parallel: M · Agents: K · Complexity: S` ### 2. Lane Timeline A per-lane list of the agents that occupied each lane in order: `Lane 1: explore (0–12s) → code-review (12–48s)` `Lane 2: debugger (5–30s)` Show overlapping windows so simultaneity is visible. ### 3. Utilization | Lane | Busy time | Idle time | Utilization % | |------|-----------|-----------|---
- Input
- Data Sources
- Report Sections
- 1. Parallelism Summary
- 2. Lane Timeline
- 3. Utilization
- 4. Serialization Bottlenecks
- Output
What does the concurrency-report skill do?
Report concurrency and parallelism for a session — how many agents ran in parallel, concurrency-lane utilization, peak parallel width, and serialization bottlenecks (sequential chains that could have run as parallel lanes) — using the Agent Monitor workflow intelligence API. Use when checking whether a multi-agent session used parallelism efficiently.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill concurrency-report --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.