agentleFS
npownpow/claude-skills/chart/SKILL.md

chart

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Renders interactive charts in the browser using Chart.js. Use when the user wants to visualize data, plot numbers, draw a bar chart, line chart, pie chart, doughnut chart, radar chart, graph metrics, compare benchmarks, show a cost curve, or display a time series. Always renders live in browser — never as a static image.

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before delivering, verify ALL:

    line 28
  2. Very specific:

    Always use new_page for first open: Use mcp__chrome-devtools__new_page with url: file:///tmp/chart.html.

    line 46
  3. Distinctive:

    Never hardcode colors inline in datasets: Always use colors from the standard palette array defined in TEMPLATE.md.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chart

Renders interactive charts in the browser using Chart.js from context-supplied data and chart type.

Workflow

  1. Extract data and chart type — identify labels, datasets, and chart type (bar, line, pie, doughnut, radar) from the user's request or conversation context.
  2. Choose colors — assign dataset colors from the standard palette. See TEMPLATE.md for the palette.
  3. Write the HTML file — write a complete self-contained file to /tmp/chart.html using the Chart.js template matching the chart type. See TEMPLATE.md for all templates.
  4. Render in browser — follow _shared/chrome-devtools-render.md to open /tmp/chart.html, wait for render, screenshot, and fix-and-reload if needed. wait_for the static <h2 id="ready"> text (Chart.js renders to canvas — canvas text is NOT detectable by wait_for). See TROUBLESHOOTING.md for chart-specific fixes.

Self-review checklist

Before delivering, verify ALL:

  • Screenshot shows the chart with visible title, labels, and data — no blank canvas
  • Chart text is readable on dark background — not invisible black-on-dark
  • Container div has explicit height (e.g. 500px) in CSS — not just on the canvas element
  • Both responsive: true and maintainAspectRatio: false are set in chart options
  • Chart.defaults.color and Chart.defaults.borderColor are set before new Chart()
  • Dataset colors are from the standard palette — no ad-hoc inline colors
  • CDN URL is exactly https://cdnjs.cloudflare.com/ajax/libs/Chart.js/4.4.1/chart.umd.min.js
  • wait_for is called with the chart title text before take_screenshot

Golden rules

Hard rules. Never violate these.

  1. Never set width or height on the canvas element. Set dimensions on the wrapper div via CSS (height: 500px). Canvas attributes override Chart.js responsive sizing.
  2. Always set both responsive: true and maintainAspectRatio: false. Either alone is insufficient — the chart collapses to 0 height without both.
  3. Always set Chart.defaults.color and Chart.defaults.borderColor before creating any chart. Without them, all text renders as black and is invisible on the dark background.
  4. Always use new_page for first open. Use mcp__chrome-devtools__new_page with url: file:///tmp/chart.html. Use navigate_page with type: reload only for subsequent fixes.
  5. Always add a static <h2 id="ready">Title</h2> above the canvas and wait_for it. Chart.js renders text onto canvas — canvas text is invisible to wait_for. The static element is the only reliable render signal.
  6. Never hardcode colors inline in datasets. Always use colors from the standard palette array defined in TEMPLATE.md.

Reference files

FileContents
TEMPLATE.mdComplete Chart.js HTML templates for bar, line, and pie/doughnut; color palette; data format patterns
TROUBLESHOOTING.mdFailure diagnosis table: symptoms, causes, fixes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.