decision-tree

Convert state.json agent execution traces into interactive HTML decision-tree reports.

21|4|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/JotJunior/cstk --skill decision-tree-jotjunior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-tree
Source: https://github.com/JotJunior/cstk/tree/main/global/skills/decision-tree
Command: npx skills add https://github.com/JotJunior/cstk --skill decision-tree-jotjunior

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve?

This skill generates a navigable, self-contained visualization of an execution's decision history from a state.json, enabling quick understanding of IA outcomes.

Core Features & Use Cases

  • Visualize the decision path as an interactive tree with phase coloring and a detail panel.
  • Produce a standalone HTML report that can be opened offline to review decisions.
  • Use for debugging and auditing agent-00c/feature-00c decision flows and other state.json decision traces.

Quick Start

Run the render script with the path to your state.json and optional output file.

Frequently Asked Questions about decision-tree

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

FAQPage Schema
How do I visualize agent decision history from a state.json file?

You can visualize agent decision history from a state.json file by running the render script, which uses jq to extract data and generates a standalone interactive HTML decision-tree report for offline review.

What is the best way to debug agent-00c execution flows?

Debugging agent-00c execution flows is best achieved by converting the state.json decision trace into a navigable HTML tree visualization, enabling quick understanding and auditing of IA outcomes.

Can I generate an offline HTML report from a state.json decision trace?

Yes, you can generate a completely self-contained HTML report from a state.json decision trace. This standalone file can be opened offline to review the interactive decision-tree.

Do I need jq installed to render a state.json decision tree?

Yes, jq is required. The skill depends on jq to read the state.json file and extract the execution decision data required to render the HTML visualization.

Does visualizing a state.json decision trace modify the original source file?

No, visualizing a state.json decision trace never modifies the source state. The process strictly reads the file to render the HTML report, preserving the original execution data.