error-propagation
Trace error propagation through a multi-agent session by agent depth — where failures originated, the depth at which they appeared, and how they cascaded up to parent agents — using the Agent Monitor workflow intelligence API and the session event stream. Use when a multi-agent run failed and you need to find the origin and blast radius of the failure.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill error-propagation --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.
# Error Propagation Trace where a multi-agent session's failures started and how far they spread. ## Input The user provides: **$ARGUMENTS** A session ID. If empty, fetch `GET /api/sessions?limit=1`, but prefer the most recent session whose `status` is `error` or `abandoned`; state which one you picked. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/workflows/{sessionId}` | The `errorPropagation` dataset: failures grouped by agent depth, with originating depth and cascade paths to parents | | `GET /api/events?session_id={sessionId}` | The event stream — corroborate with `APIError`, `SubagentStop`, and failing `PostToolUse` events (`event_type`, `tool_name`, `summary`, `timestamp`) | ## Report Sections ### 1. Failure Summary From `errorPropagation`: total errors, the depth where the first error originated, and how many distinct agents were affected. `Origin depth: d · Errors: N · Agents affected: M` ### 2. Errors by Depth | Depth | Errors originated | Errors inherited from children | Net failing agents | |-------|-------------------|--------------------------------|--------------------| Show whether failures concentrate deep in the tree (leaf subagents) or
- Input
- Data Sources
- Report Sections
- 1. Failure Summary
- 2. Errors by Depth
- 3. Cascade Paths
- 4. Error Taxonomy
- 5. Containment Assessment
- Output
What does the error-propagation skill do?
Trace error propagation through a multi-agent session by agent depth — where failures originated, the depth at which they appeared, and how they cascaded up to parent agents — using the Agent Monitor workflow intelligence API and the session event stream. Use when a multi-agent run failed and you need to find the origin and blast radius of the failure.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill error-propagation --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.