skills.rest
andrew-t-james
andrew-t-jamesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

trace

Generate chronological timelines and summaries of hooks, skills, agents, and tools.

Updated Jul 3, 2025
Search Tags:#debugging#timeline#trace#summary#agent-flow
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill trace-andrew-t-james
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_codex/skills/trace
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill trace-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show agent flow trace timelines and summaries to simplify debugging and performance analysis.

Core Features & Use Cases

  • Timeline: display chronological events across hooks, skills, agents, and tools.
  • Summary: provide aggregate counts and metrics for trigger events, mode transitions, and bottlenecks.
  • Use Case: when an agent flow behaves unexpectedly, generate both a timeline and a summary to isolate the root cause.

Quick Start

Pull up the latest session trace by calling the trace tools to see both the event timeline and the summary.

Frequently Asked Questions about trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I visualize agent flow to debug multi-component orchestration?▼

To debug agent flow, you generate a chronological timeline of events across hooks, skills, agents, and tools to isolate root causes. This visualization simplifies debugging complex interaction chains and unexpected behavior in multi-component orchestration.

What is the best way to profile performance bottlenecks in agent interaction chains?▼

The best way to profile performance bottlenecks is to generate an aggregate summary of events and transitions. This provides metrics for trigger events and mode transitions, allowing you to pinpoint delays within multi-component agent orchestration.

How do I trace chronological events across hooks, skills, and tools?▼

Tracing chronological events requires generating a timeline that displays the sequence of hooks, skills, agents, and tools. This provides a single view of agent flow transitions to help you debug complex interaction chains effectively.

Does this debugging approach work with multi-component agent orchestration sessions?▼

Yes, this approach is specifically designed for multi-component agent orchestration sessions. It generates both a timeline and a summary to isolate root causes when agent flow behaves unexpectedly during complex interaction chains.

Why does my agent flow behave unexpectedly during complex interaction chains?▼

Unexpected agent flow behavior often stems from misconfigured trigger events or mode transitions. By generating both a timeline and an aggregate summary, you can isolate the root cause by comparing chronological events against transition metrics.

Related Skills

Explore More Software Engineering Skills→
leejaedusleejaedus

trace

Display chronological event timelines and aggregate summaries from Claude Code sessions.

Community
Intermediate
Brite-NitesBrite-Nites

systematic-debugging

Identify and resolve software bug root causes with a four-phase debugging workflow.

Official
Advanced
mvillmowmvillmow
18

suggest-optimizations

Analyze profiling data to identify optimization opportunities in performance-critical code paths.

Community
Intermediate
realsigridjinrealsigridjin
20

trace

Reveal chronological event flows and aggregate summaries of Codex agent sessions.

Community
Intermediate