trace

Generate an Omagy session trace timeline and aggregate agent activity summary.

3|Updated May 24, 2026
One-click install
npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill trace-shayne-snap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/shayne-snap/oh-my-antigravity/tree/main/plugin/skills/trace
Command: npx skills add https://github.com/shayne-snap/oh-my-antigravity --skill trace-shayne-snap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand what Omagy actually did during the current session by showing the flow trace timeline and a high-level summary, so you can debug confusion about modes, hooks, and tool activity.

Core Features & Use Cases

  • Session activity timeline: Reports recent hook/tool events and mode lifecycle activity in a chronological, trace-focused view.
  • Aggregate trace summary: Provides counts and lifecycle metrics across modes to quickly spot what ran and what may be missing.
  • Missing-data clarity: Explicitly explains when expected trace data is unavailable (for example, a missing logs directory indicates no hook events were recorded yet).

Quick Start

Ask: Show me the Omagy trace timeline and summary for the current session.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I view a timeline of agent hook events and mode transitions for debugging?

To view an agent trace timeline for debugging, you need a chronological report of recent hook and tool events. This session trace displays mode lifecycle activity so you can validate whether hooks ran as expected.

What is an Omagy session trace summary and when do I need it?

An Omagy session trace summary is an aggregate report of counts and lifecycle metrics across modes. You need it when auditing mode execution to quickly spot what ran and what may be missing during the current session.

How do I get a chronological trace of tool activity to debug user-reported issues?

To get a chronological trace of tool activity, request a session timeline view. It reports recent hook and tool events in a trace-focused format, providing the flow data needed to debug user-reported issues.

Can I generate a trace summary using MCP tools or do I need CLI fallbacks?

You can generate a trace summary using MCP tools like omagy_trace_summary when available. If those are missing, the system applies CLI fallbacks such as omagy trace summary --json to retrieve the aggregate data.

Why does my session trace show no hook events recorded yet?

Your session trace shows no hook events because expected trace data is unavailable. A missing logs directory explicitly indicates that no hook events were recorded yet during the current Omagy session.

What's the best way to audit mode execution and validate workflow transitions?

The best way to audit mode execution is to review a trace timeline alongside an aggregate summary. This combination validates workflow transitions and counts lifecycle metrics to spot missing mode activity accurately.