trace

Name: trace
Availability: InStock
Author: gtpgg1013

Generate a chronological trace timeline and summary of agent session interactions.

Updated Mar 21, 2026

Search Tags:#workflow #debugging #monitoring #logging #audit #agent #trace

Ready to run

npx skills add https://github.com/gtpgg1013/claude-skills-collection --skill trace-gtpgg1013

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Chronicles and clarifies the sequence of interactions in an AI agent workflow by generating a trace timeline and a concise summary of the session flow, enabling debugging and auditing.

Core Features & Use Cases

Timeline: chronological trace of hooks, keywords, skills, agents, and tools.
Summary: aggregated statistics including mode transitions and bottlenecks.
Use Case: Troubleshoot unexpected agent behavior by inspecting the flow and performance across a session.

Quick Start

Provide a chronological trace timeline and a concise summary of how hooks, keywords, skills, agents, and tools interacted during the session.

Frequently Asked Questions about trace

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

FAQPage Schema

How do I debug unexpected AI agent behavior by inspecting the workflow timeline?▼

To debug unexpected AI agent behavior, generate a chronological trace timeline that extracts transitions, bottlenecks, and flow patterns across hooks, keywords, skills, agents, and tools. This provides a declarative overview for troubleshooting session performance.

What is an agent flow trace timeline used for in session auditing?▼

An agent flow trace timeline chronicles the sequence of interactions during a session, providing a concise summary of how components interacted. It is used for auditing workflows and clarifying the exact sequence of events to ensure correct execution.

Can I filter the trace timeline to focus on specific agent events like hooks and tools?▼

Yes, you can use filter parameters to focus the trace timeline on specific event types such as hooks, skills, agents, keywords, tools, and modes. This allows targeted debugging by isolating individual component interactions within the latest session.

How do I identify bottlenecks and mode transitions in an agent workflow?▼

You identify bottlenecks and mode transitions by generating an aggregated summary from the session's trace timeline. This summary highlights performance bottlenecks and tracks how hooks, skills, and tools interacted chronologically throughout the workflow.

Does the agent trace timeline require external dependencies to monitor a session?▼

No external dependencies are required to monitor a session. The trace timeline operates independently to extract a declarative overview of the agent flow, aggregating statistics and session interactions without needing additional components.