SkillAgentSearch skills...

event-trace

Trace the full event chain for one Claude Code session into an ordered timeline of every event type with tool_name and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?session_id= and /api/sessions/:id from the Agent Monitor dashboard

Install / Use

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Operations

Supported Platforms

Claude Code

Our assessment of event-trace

event-trace scores 81/100 on our quality scale, 661st of 763 Operations skills we index.

Its SKILL.md is 3.0 KB long, well organised into 10 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 event-trace 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-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

event-trace compared with similar skills

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

SkillScoreStarsUpdatedFormat
event-trace (this skill)by hoangsonww811.0k2mo agoSKILL.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md
Scraplingby D4Vinci100104.9k5d agoMCP Server
crawl4aiby unclecode10087.7k2d agoMCP Server

Frequently asked questions

How do I install event-trace?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill event-trace. The install tabs above show the steps for each supported agent.
Which AI agents does event-trace work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is event-trace 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 event-trace still maintained?
The repository was last updated about 2 months ago, so event-trace is actively maintained.

name: event-trace description: > Trace the full event chain for one Claude Code session into an ordered timeline of every event type with tool_name and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?session_id= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step by step.

Event Trace

Build a chronological, annotated event timeline for a single session.

Input

The user provides: $ARGUMENTS

This is a session ID. It may also be:

  • latest / last — trace the most recently updated session
  • errors — trace the most recent session whose status is error

Data Sources

| Endpoint | Returns | |----------|---------| | GET /api/sessions?limit=N | session list (used to resolve latest/errors and the target id) | | GET /api/sessions/:id | full session detail (status, model, cwd, started_at, ended_at, cost, nested agents + events) | | GET /api/events?session_id=X | the ordered event stream: event_type, tool_name, summary, data, timestamp |

Report Sections

1. Resolve the session

If $ARGUMENTS is a raw id, use it. If latest/last, call GET /api/sessions?limit=1. If errors, call GET /api/sessions?limit=10&status=error and pick the newest. Confirm the id resolves via GET /api/sessions/:id; if not, report it as missing and stop.

2. Session header

From GET /api/sessions/:id: id, status, model, cwd, started_at → ended_at, total duration, cost (USD to 4 decimals), and counts (events, agents).

3. Ordered timeline

From GET /api/events?session_id=X, list every event in timestamp order. One row per event:

| # | time | Δ since prev | event_type | tool_name | summary |

Cover all event types present: SessionStart, PreToolUse, PostToolUse, Stop, SubagentStop, Compaction, APIError, TurnDuration, Notification, SessionEnd.

4. Gap & failure highlights

Annotate the timeline:

  • Gaps: any Δ > 30s between consecutive events — mark ⏳ and note the wait.
  • Unpaired tool calls: a PreToolUse with no matching PostToolUse (same tool_name, next in stream) — mark ⚠️ "no completion recorded".
  • Failures: APIError events and PostToolUse whose summary/data indicates an error — mark ❌ with the error text.
  • Compaction: mark ♻️ and note it resets the visible token baseline.
  • Missing bookends: no SessionStart at the head or no Stop/SessionEnd at the tail of an ended session — mark 🚩.

5. Verdict

One line: CLEAN, GAPS DETECTED, or FAILURES PRESENT — with the count of each flag type and the single most likely thing to investigate next.

Output

  • Markdown timeline table, events in strict timestamp order.
  • Status glyphs inline: ✅ ok, ❌ error, ⚠️ warning/unpaired, ⏳ gap, ♻️ compaction, 🚩 missing bookend.
  • Currency in USD to 4 decimals.
  • Cite only event data returned by the API — do not invent timestamps or summaries.
  • 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
CategoryOperations
Updated2mo 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