Menu

Individual skill

chart-type-selection

0upvotes

Picks the right chart type for your data and your message using a decision tree, so the chart proves the point instead of just showing numbers.

skills/chart-type-selection/SKILL.md

Read pinned source

Source commit 45f80c2fab1ea7fc4d78b09b3c7c51d0ab4fc44a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
26
Repository last updated
Sep 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Chart Type Selection

## When to use
Use this skill first, before you build anything. You have a table of numbers and a point to make, but you are not sure whether it should be a bar, a line, a scatter, a waterfall, or something else. Run this skill to convert "what data do I have" plus "what am I trying to say" into one defensible chart type.

## What it does
It returns a single recommended chart type, a short reason tied to your message, and two runner-up options with the trade-offs. It also flags when a chart is the wrong tool and a table or a single number would land better. The output is structured so you can drop the recommendation straight into the build step.

## Method
The skill runs a message-first decision tree. The driving question is never "what does the data look like" alone. It is "what is the one sentence the audience should remember, and which encoding proves that sentence fastest."

Step 1. State the message in one sentence.
Force the message into a single declarative claim, for example "European margin fell while volume held" or "two segments drive eighty percent of revenue." If you cannot write the sentence, stop. The chart cannot be chosen until the claim exists.
Back to top