trace

Visualize chronological event timelines of hooks, keywords, skills, agents, and tools.

2|1|Updated Oct 8, 2009

Search Tags:#workflow #performance #debugging #timeline #agents #trace

Ready to run

npx skills add https://github.com/riethmayer/dotfiles --skill trace-riethmayer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/trace
Command: npx skills add https://github.com/riethmayer/dotfiles --skill trace-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Show the agent flow timeline and summarize how hooks, keywords, skills, agents, and tools interact during a session.

Core Features & Use Cases

Visualize end-to-end interaction flows with a chronological event timeline.
Generate a concise summary of decisions, transitions, and tool usage for quick reviews.
Identify bottlenecks, mode transitions, and failure points to improve reliability and performance.

Quick Start

Run the trace skill on your most recent session to display its timeline and summary.

Frequently Asked Questions about trace

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

FAQPage Schema

How do I visualize an agent interaction timeline for debugging?▼

To debug an agent workflow, you need to visualize the agent interaction timeline by tracing chronological events. This process identifies the sequence of interactions between hooks, keywords, skills, agents, and tools to reveal exact decision paths and bottlenecks during a session.

What is the best way to profile tool performance across agent sessions?▼

Profiling tool performance across agent sessions requires aggregating chronological event data into summary statistics. By auditing the sequence of tool interactions and transitions, you generate a concise summary that highlights execution patterns, mode transitions, and failure points to improve reliability.

How do I audit agent decision paths during a session?▼

Auditing agent decision paths involves mapping the chronological sequence of events when hooks, keywords, and tools interact. By generating a timeline of these interactions, you can review end-to-end flows and identify exactly where mode transitions or failures occur within the session.

Can I generate aggregate statistics for an agent workstream?▼

Yes, you can generate aggregate statistics for an agent workstream by summarizing how hooks, skills, agents, and tools interact. This produces a concise summary of decisions, transitions, and tool usage, allowing you to quickly review performance and identify bottlenecks across sessions.

How do I identify bottlenecks and failure points in my agent workflow?▼

Identifying bottlenecks and failure points in an agent workflow requires visualizing the chronological timeline of tool and agent interactions. By tracing these events, you isolate mode transitions and specific failure points to improve overall reliability and performance across the session.

Do I need any specific dependencies to trace agent interactions?▼

No specific dependencies are required to trace agent interactions. The process relies on internal trace tools to produce a chronological timeline and aggregate statistics, allowing you to debug workstreams and audit decision paths without external setup or environment configuration.