session-debug

Locate, parse, and summarize JSONL session logs for a given SESSION_ID.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/nocoo/deca --skill session-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-debug
Source: https://github.com/nocoo/deca/tree/main/skills/session-debug
Command: npx skills add https://github.com/nocoo/deca --skill session-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging AI agent sessions can be tedious when trying to understand what happened during a conversation, the tools invoked, and the resulting outcomes. This skill surfaces session data from JSONL logs and presents actionable insights.

Core Features & Use Cases

  • Locate and read JSONL session files stored under .deca/sessions for a given SESSION_ID.
  • Parse messages and tool_use blocks to reconstruct the dialogue and tool interactions.
  • Generate a structured session report with total messages, time range, duration, and key observations.

Quick Start

Enter a SESSION_ID to retrieve and analyze the corresponding session data.

Frequently Asked Questions about session-debug

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

FAQPage Schema
How do I analyze AI agent sessions from JSONL logs?

To analyze AI agent sessions from JSONL logs, provide a SESSION_ID so the tool can locate the corresponding file, parse tool_use and tool_result blocks, and generate a structured report of messages and tool interactions.

What is the best way to debug tool interactions in an AI agent session?

The best way to debug tool interactions is to parse tool_use and tool_result blocks from the session's JSONL logs, which reconstructs the dialogue and surfaces actionable insights about what happened during the conversation.

Can I extract a session report from .deca/sessions using a SESSION_ID?

Yes, you can extract a session report from .deca/sessions by providing a SESSION_ID, which allows the tool to locate the specific JSONL file and summarize the total messages, time range, and duration.

What data is included in a structured JSONL session debug report?

A structured JSONL session debug report includes total messages, time range, duration, key observations, and a detailed reconstruction of dialogue and tool interactions parsed from tool_use and tool_result blocks.

Do I need a specific SESSION_ID to debug agent conversations?

Yes, you need a specific SESSION_ID because the tool uses it to locate the correct JSONL file within the .deca/sessions directory to parse messages and analyze tool interactions across channels.