Chart Skill — Development skill for Claude Code

chart-skill

**English** · [中文](README.zh-CN.md) · [日本語](README.ja.md)

**Same question. Two answers.**


Left: **25 seconds**, seven numbered paragraphs — the reader has to prioritise them. Right: **28 seconds**, one flowchart — branches, exits and the next step are all on the canvas.

**Nearly the same time.** The difference is what the model decides to do with those three seconds. It doesn't change what the model *can* do. It changes what it *chooses* to do.

This is an **agent skill**, not a charting library. Drop it into your agent's skill directory and it starts choosing diagrams over paragraphs — with hard rules for both directions: when it *must* draw, and when it *must not*.

---

What it actually changes

Prose is **linear**: you have to read to the end to know what matters, then rebuild the structure in your head. A diagram is **parallel**: structure, proportion, flow and order are visible at once.

So the question is never "can this be drawn" but:

**Is this information already shaped like a diagram?**

If yes, drawing it saves the reader half the work. If no, drawing it is just decoration. This skill encodes both halves — and the second one (restraint) is the part most tools miss.

What a conversation looks like after installing it

Triage: five paragraphs → one flowchart

**Before** — the reader has to sort out the priorities:

This error usually has three causes. First, the port is taken… second, the config path is wrong… third, dependencies are missing… the first is the most common…

**After**:


Scheduling: "about six weeks" → a gantt you can argue with


Structure: one breathless sentence → a mind map


---

But the hard part isn't drawing. It's **knowing when not to**.

Three numbers or fewer: use a table. Two s