trace

Visualize agent execution flows with chronological timelines and performance statistics.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/JustineDevs/roblox-ai-os --skill trace-justinedevs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/JustineDevs/roblox-ai-os/tree/main/plugins/roblox-ai-os-creator-skills/skills/trace
Command: npx skills add https://github.com/JustineDevs/roblox-ai-os --skill trace-justinedevs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the lack of visibility into complex agentic workflows by providing a clear, chronological timeline and summary of how hooks, tools, and skills interact during a session.

Core Features & Use Cases

  • Chronological Timeline: View the exact sequence of events, including hook fires, tool calls, and mode transitions.
  • Aggregate Statistics: Identify performance bottlenecks and flow patterns through summary metrics.
  • Use Case: When an agent behaves unexpectedly, use this Skill to trace the exact chain of keywords and tool activations that led to the error, allowing for rapid debugging of the execution logic.

Quick Start

Use the trace skill to display the latest session timeline and aggregate performance summary.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I debug an unexpected agent execution flow during a session?

Debug an unexpected agent execution flow by visualizing the chronological timeline of hook fires, tool calls, and mode transitions to trace the exact chain of activations that caused the error.

What is the best way to identify performance bottlenecks in agentic workflows?

Identify performance bottlenecks in agentic workflows by aggregating chronological event timelines and summary statistics to evaluate flow patterns and optimize execution logic.

Do I need specific tools to trace agent execution timelines?

You need integration with the trace_timeline and trace_summary MCP tools to generate session-specific diagnostic data and aggregate performance statistics for your workflows.

Can I track keyword activations and tool interactions within my debugging workflow?

Track keyword activations and tool interactions by aggregating chronological event timelines that display the exact sequence of hook fires and mode transitions during complex agentic workflows.

Why does my agent workflow lack visibility into hook and skill interactions?

Agent workflows lack visibility because chronological event timelines and aggregate statistics are not visualized, obscuring the sequence of hook fires, tool calls, and skill interactions needed for debugging.