SkillAgentSearch skills...

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

Install / Use

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill concurrency-report

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Automation

Supported Platforms

Claude Code
Zed

Our assessment of concurrency-report

concurrency-report scores 81/100 on our quality scale, 2394th of 2,768 Automation skills we index.

Its SKILL.md is 2.5 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so concurrency-report is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

concurrency-report compared with similar skills

All 4 of these similar skills score higher than concurrency-report; compare them before choosing.

SkillScoreStarsUpdatedFormat
concurrency-report (this skill)by hoangsonww811.0k56d agoSKILL.md
Agent-Reachby Panniantong100113.0k10d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
headroomby headroomlabs-ai10080.1ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.1k9d agoCLAUDE.md

Frequently asked questions

How do I install concurrency-report?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill concurrency-report. The install tabs above show the steps for each supported agent.
Which AI agents does concurrency-report work with?
It is written for Claude Code and Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is concurrency-report safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is concurrency-report still maintained?
The repository was last updated about 2 months ago, so concurrency-report is actively maintained.

name: concurrency-report description: > 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.

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 % | |------|-----------|-----------|---------------| Plus an overall utilization figure (busy lane-time / total lane-time).

4. Serialization Bottlenecks

Identify sequential chains where one agent waited on the previous despite no apparent dependency — candidates to run as parallel lanes. State the chain and the wall-clock time it cost. Only flag chains the concurrency timing data actually shows as sequential.

Output

  • Markdown tables for utilization; a fenced list for the lane timeline.
  • Durations in human units (e.g. 48s, 2m 10s); percentages to whole numbers.
  • Use ▲/▼ when comparing utilization against an even-distribution baseline.
  • Cite only timing returned by the API; never invent lane overlaps or durations.
  • If the session ran a single agent (no concurrency), say so plainly rather than inventing lanes.
  • If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryAutomation
Updated1mo ago
Forks238

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions