Dialog Tree

Maintain a visual "dialog tree" — a data file plus a self-contained HTML viewer in the project repo that map the branches of a long conversation (user questions → the steps/variants of the answers) as an interactive tree with resolve/delete marks and a "built up to" marker for incremental updates. Use whenever the user asks to "create/set up a dialog tree", "update the tree", "add this to the tree", "show open branches", or mentions dialog-tree.html — and proactively offer it when a deep-dive discussion branches enough that the user risks losing track of unexplored side-threads.

3 starsGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add ikotelkin/claude-skills --skill dialog-tree

Manual install

git clone --depth 1 https://github.com/ikotelkin/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/dialog-tree ~/.claude/skills/dialog-tree

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Dialog Tree

## Why

A "question → clarification → clarification" conversation is a depth-first search: the user dives into one branch while the unexplored sibling branches silently pile up in their head. When the tree gets deep, backtracking becomes painful. This skill offloads that bookkeeping into files: an HTML page in the project repo that shows every branch of the discussion as a tree, lets the user mark branches resolved, and delete dead ones.

The tree is built by the assistant, not by the app: the viewer only renders the data file. "Update the tree" means appending nodes to it. The tree doubles as a session conspectus — after context loss (compaction, new session) reading the data file restores the map of what was discussed, how it branched, and what is still open.

## Data / view split, file naming

Two files side by side in the project, **named after the treeId** — a generic name like `dialog-tree.html` collides as soon as one machine, one static server, or several sessions host more than one tree:

- **`<treeId>-tree.html`** — the view, a generic dependency-free renderer. Never edited per-project; upgrading the skill = replacing this file wholesale (any file name keeps working).

Read the full skill on GitHub

Details

Skill name: dialog-tree
Repository: ikotelkin/claude-skills
Path: skills/dialog-tree/SKILL.md
License: MIT
Repo updated: 7 September 2026
Listed in: karanb192/awesome-claude-skills

FAQ

What does the Dialog Tree skill do?

How do I install the Dialog Tree skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add ikotelkin/claude-skills --skill dialog-tree. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dialog Tree popular?

It lives in ikotelkin/claude-skills, which has 3 GitHub stars and 0 forks, and is included in 1 curated skill list.

Related skills

Working Memory

ikotelkin/claude-skills

Maintain a project's mid-term working memory — a WORKING.md file in the repo holding the current stage's state (decision log, what was tried and failed, what's next) so it survives context compaction and new sessions. Use to set up WORKING.md in a project, to read it at the start of a session, to checkpoint progress into it after a meaningful step or before /compact, and to consolidate settled conclusions into long-term assistant memory (then reset WORKING.md) when a stage completes. Triggers: "set up working memory", "checkpoint", "save state", "resume where we left off", "consolidate memory"

Productivity & NotesIn 1 list

Structured Gist

domattioli/structured-gist

Render explanatory or process-recap prose as a nested lecture-note outline instead of paragraphs — fixed role ladder concept (-) → attribute (▸, a named property) → enumerator (I./A./i./a.) → explanation (↪, one prose sentence, usually a leaf). No plain bullets. Render modes — block (fenced, literal glyphs; default on every surface) and responsive (opt-in real GFM nested list for GitHub bodies and chat replies; glyph-free, role carried by typography). One granularity level (standard); skim and deep are archived. Independent of caveman (structure vs wording). Opt-in report preset (`/structured-

Git & Code ReviewIn 1 list

Shipreel

theBstar/shipreel

Turn a pull request into a short narrated walkthrough video (about two and a half minutes) with animated diagrams, code panels, optional screen recordings of the real app, captions, crossfade cuts and an ambient music bed. Runs locally with no paid services by default. Use when asked for a PR video, PR walkthrough, demo video of a change, or "make a shipreel".

Git & Code ReviewIn 1 list

Prospeak

giorgiozamboni/prospeak

Rewrites EXISTING text into the register of a professional world (board, deck, LinkedIn, postmortem, offerta tecnica, bando, CV), keeping it credible and not AI-sounding: it adds the jargon on purpose. Use whenever the user wants a text to sound more professional, executive, managerial, technical, formal, "da ufficio marketing", to raise or adjust the register, tune the tone for an audience (capo, CFO, cliente, management), calibrate how much English or itanglese to use, or "buzzword it up", even if they never say "corporate". Two dials: five intensity levels and thirteen sector branches (tech

Git & Code ReviewIn 1 list

Gitlab Skill

ekohe/gitlab-skill

GitLab integration for fetching issues/MRs, generating executive summaries, performing comprehensive code reviews, and automating issue resolution workflows. Use when working with GitLab issues, merge requests, or when asked to summarize, review, comment on, or resolve GitLab work items.

Git & Code Review

Changelog Generator

Automatically creates user-facing changelogs from git commits. Transform technical commit messages into customer-friendly release notes.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.