skills.rest
hotaq
hotaqCOMMUNITY
Explore all skills by this author →
GitHub

trace

Display chronological agent flow timelines and aggregate session summaries.

Updated Apr 20, 2026
Search Tags:#debugging#timeline#hooks#mcp#trace#summary#agent flow
One-click install
npx skills add https://github.com/hotaq/Sprite_harmess --skill trace-hotaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/hotaq/Sprite_harmess/tree/main/.codex/skills/trace
Command: npx skills add https://github.com/hotaq/Sprite_harmess --skill trace-hotaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand how an AI session actually executed by exposing the event flow behind hooks, keywords, skills, agents, and tools.

Core Features & Use Cases

  • Chronological Trace View: Shows the latest session timeline so you can inspect what happened and when.
  • Aggregate Session Summary: Reports hook counts, detected keywords, activated skills, mode transitions, and tool bottlenecks.
  • Debugging and Analysis: Useful for reviewing execution patterns, diagnosing slow tools, and understanding keyword-to-skill-to-agent chains.

Quick Start

Use the trace skill to display the latest session timeline and summary of agent flow interactions.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I view the agent flow timeline for an AI session?▼

To view the agent flow timeline, you can use the trace skill to display the chronological event sequence of hook, tool, and agent interactions. It relies on the trace_timeline MCP tool to produce a chronological view of your latest session.

Can I detect tool bottlenecks and slow execution patterns in my agent flow?▼

Yes, you can detect tool bottlenecks by generating an aggregate session summary. The trace skill uses the trace_summary MCP tool to report statistics and identify slow tools or execution pattern bottlenecks within the session.

How do I debug hook, keyword, and skill interactions in a session?▼

Debugging hook, keyword, and skill interactions is done by reviewing the chronological trace view. This exposes the event flow behind these components, helping you understand the keyword-to-skill-to-agent chains and diagnose execution issues.

Does the trace summary support filtering results and limiting event outputs?▼

Yes, the trace summary supports optional filtering and result limits when analyzing the session timeline. This allows you to narrow down the chronological events and aggregate statistics to focus on specific interactions or execution patterns.

What is the best way to analyze mode transitions and activated skills in an AI session?▼

The best way to analyze mode transitions and activated skills is to generate an aggregate session summary. This provides reports on detected keywords, activated skills, and mode transitions alongside other aggregate statistics for review.

Related Skills

Explore More Software Engineering Skills→
lis186lis186
46

flow

Trace business logic execution paths from a given entry point.

Community
Advanced
sigridjinethsigridjineth
20

trace

Visualize agent execution timelines and aggregate statistics via MCP tools.

Community
Intermediate
rafaelcallejarafaelcalleja
2

agent-observability

Stream Claude Code agent events to a filesystem-based observability dashboard.

Community
Advanced
softmgsoftmg

V3 MCP Optimization

Optimize claude-flow v3 MCP servers with connection pooling and O(1) tool lookup.

Official
Advanced