chart-chooserlisted

Choosing a chart is a reasoning problem that most tools skip straight past into rendering. This skill does the reasoning out loud. Give it the question the chart has to answer and the shape of the data behind it; it returns one recommendation, the argument for it, the alternatives it rejected with the reason each fails *this* question, the encoding decisions that make or break the read, and the code in whichever library you work in. The rejected list is what you paste into the thread when a stakeholder asks for a pie chart of twelve categories. Nothing here needs a running environment, so it works on claude.ai, in Claude Code, and in Claude Cowork alike. ## When to use this skill - You have a finding and no idea which of six plausible charts shows it. - Somebody requested a chart type you suspect will mislead, and you need the reason written down. - A chart is technically correct and nobody can read it, and the encoding needs rethinking. - You are drafting a figure and want a caption that says what it does and does not show. > [!NOTE] > This is a decision skill, not a rendering skill. It produces the choice, the reasons, and the code; it does not execute the code or read your data. It is also not dashboard design: laying out many panels so an on-call engineer can read a service at a glance belongs to the [dashboard-designer](/skills/observability/dashboard-designer) skill. This skill designs one chart that answers one question. ## Instructions 1. **Get the question in on