trace

Display chronological trace events and summaries for debugging sessions.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/RJJJJ/project2 --skill trace-rjjjj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/RJJJJ/project2/tree/main/.codex/skills/trace
Command: npx skills add https://github.com/RJJJJ/project2 --skill trace-rjjjj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitors and clarifies how hooks, keywords, skills, agents, and tools interact by rendering a clear trace timeline and a compact summary.

Core Features & Use Cases

  • Timeline view: shows chronological sequence of events for a given session.
  • Summary view: aggregates counts and metrics across events.
  • Use case: debugging and optimizing complex agent workflows in interactive sessions.
  • Use Case example: diagnosing why a particular skill didn't trigger when expected.

Quick Start

Run a trace by calling trace_timeline with no arguments to view the latest session, then inspect the summary with trace_summary.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I trace agent flow to debug why a skill didn't trigger when expected?

Trace agent flow by rendering a chronological timeline of session events to clarify how hooks, keywords, skills, agents, and tools interact. It helps diagnose unexpected trigger behavior in complex interactive workflows through a clear timeline view.

What's the best way to monitor agent workflow execution for performance analysis?

Monitor agent workflow execution by displaying the chronology of a session's trace events for debugging and performance analysis. It provides both a timeline showing the chronological sequence and a summary aggregating counts and metrics across events.

Can I use trace tools on sessions without modifying the underlying workflow data?

Yes, trace tools apply to tracing hooks, keywords, skills, agents, and tools across sessions while ensuring safe, read-only data handling. This satisfies requirements for deterministic execution and clear output formatting without altering source data.

How do I view a summary of trace events across an interactive session?

View a summary of trace events by calling trace_summary after running a trace. The summary view aggregates counts and metrics across events, providing a compact overview that complements the detailed chronological timeline of the session.

What does a trace timeline show when debugging complex agent workflows?

A trace timeline shows the chronological sequence of events for a given session, making it easier to debug and optimize complex agent workflows. It visually maps how hooks, keywords, skills, agents, and tools interact over time.