Skip to content
cccskills
FreePublished on GitHub

chart

Turn numbers into a chart — bar, line, area, pie, or doughnut. Use when asked to chart or graph data, visualize metrics/trends/breakdowns, or show numbers as a picture instead of a table. Produces a ready-to-render chart spec (renders live in the playground and exports as PNG) plus a one-line read of what the chart shows.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills
See how to install

Files included (1)

  • SKILL.md3.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Chart Skill

A table of numbers hides the story; a chart shows it. This skill turns data into a clean, correctly-typed chart — a trend as a line, a comparison as bars, a composition as a pie/doughnut — emitted as a small JSON spec inside a ```chart block that renders live in the playground (and exports as PNG).

Required Inputs

Ask for these only if they aren't already provided:

  • The data — the numbers, with their labels/categories (paste a table, list, or metrics).
  • What you want to show — a trend over time, a comparison between things, or parts of a whole. This decides the chart type.
  • Series — one metric or several (e.g. revenue and churn over the same months).
  • Title (optional) — what the chart is about.

If the data implies the wrong chart type for the goal, pick the right type and say why.

Output Format

[What the chart shows]

A one-line read — the takeaway the chart makes obvious.

{
  "type": "line",
  "title": "MRR vs. churned MRR (2026)",
  "labels": ["Jan", "Feb", "Mar", "Apr", "May", "Jun"],
  "series": [
    { "name": "MRR ($k)", "data": [120, 138, 151, 167, 180, 201] },
    { "name": "Churned ($k)", "data": [8, 9, 7, 11, 9, 8] }
  ]
}

Notes (optional) — caveats, the source of the numbers, or what a follow-up chart would show.

Chart Spec Rules (so it renders)

  • Emit a single ```chart block containing valid JSON (double-quoted keys/strings, no trailing commas, no comments).
  • type: "bar", "line", "area", "pie", or "doughnut".
  • labels: the x-axis categories (or the slice names for pie/doughnut).
  • series: an array of { "name": "...", "data": [numbers] }. Pie/doughnut uses the first series only.
  • Every series' data length must match labels length. Numbers only — no units inside the array (put units in the series name or title).
  • Choose the type by intent: trend over time → line/area; compare categories → bar; parts of a whole → pie/doughnut.

Quality Checks

  • Chart type matches the intent (trend → line, comparison → bar, composition → pie)
  • The JSON is valid and renders without edits (no trailing commas, all strings quoted)
  • Every series' data length equals the number of labels
  • Units/scale are clear (in the title or series names), and the one-line read states the takeaway
  • Multiple series are used only when they share the same axis/scale

Anti-Patterns

  • Do not use a pie chart for more than ~6 slices or for trends — pies show composition, not change
  • Do not put units or text inside the numeric data array — it breaks the chart
  • Do not emit invalid JSON (trailing commas, single quotes, comments) — it won't render
  • Do not mismatch lengths — a series shorter/longer than the labels misaligns the chart
  • Do not chart numbers you weren't given — flag gaps instead of inventing data points

Based On

Data-visualization practice (chart-type-to-intent: trend/comparison/composition), emitted as a renderable chart spec.

Example Trigger Phrases

  • "Chart this data."
  • "Graph our monthly revenue."
  • "Visualise these metrics."
  • "Show these numbers as a picture instead of a table."

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

360-feedback-template

Free

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 21, 2026

401k-plan-decoder

Free

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 21, 2026

ab-test-planner

Free

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 21, 2026

ab-test-readout

Free

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 21, 2026

academic-cv

Free

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 21, 2026

accessibility-audit

Free

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

The English summary is being prepared. Showing the original description.

mohitagw15856/pm-claude-skills1.5KUpdated Oct 21, 2026

See all skills by mohitagw15856

Report a problem with this skill