SkillAgentSearch skills...

chart-data-extractor

Extract pixel-level data from an image of a chart or graph and produce a structured data table

Install / Use

npx skills add mohitagw15856/pm-claude-skills --skill chart-data-extractor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Claude Code

Our assessment of chart-data-extractor

chart-data-extractor scores 82/100 on our quality scale, 2275th of 4,140 Development & Engineering skills we index.

Its SKILL.md is 4.6 KB long, well organised into 14 sections with 1 code example: a solid amount of guidance for an agent.

With 1,396 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
12/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 6 days ago, so chart-data-extractor is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

chart-data-extractor compared with similar skills

All 4 of these similar skills score higher than chart-data-extractor; compare them before choosing.

SkillScoreStarsUpdatedFormat
chart-data-extractor (this skill)by mohitagw15856821.4k6d agoSKILL.md
Agent-Reachby Panniantong10086.4k15d agoCLAUDE.md
ai-job-searchby MadsLorentzen10044.6k1d agoCLAUDE.md
claude-howtoby luongnv8910041.7ktodayCLAUDE.md
LocalAIby mudler10049.3ktodayMCP Server

Frequently asked questions

How do I install chart-data-extractor?
Run npx skills add mohitagw15856/pm-claude-skills --skill chart-data-extractor. The install tabs above show the steps for each supported agent.
Which AI agents does chart-data-extractor work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is chart-data-extractor safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is chart-data-extractor still maintained?
The repository was last updated 6 days ago, so chart-data-extractor is actively maintained.

name: chart-data-extractor description: "Extract pixel-level data from an image of a chart or graph and produce a structured data table. Use when asked to extract data from a chart image, transcribe numbers from a graph, digitise a chart, or turn a screenshot of data into a table. Produces a structured table with extracted values, confidence levels, and a reconstructed chart source. Best used with Claude Opus 4.7 or newer for reliable chart data extraction."

Chart Data Extractor Skill

Extracts data from images of charts and graphs — bar charts, line charts, pie charts, scatter plots, and tables in images — producing a structured data table that can be used in spreadsheets or rebuilt in any charting tool. Built to leverage Opus 4.7 pixel-level image analysis capabilities.

Required Inputs

Ask the user for these if not provided:

  • The chart image (upload a screenshot or image file)
  • Chart type (if ambiguous — bar / line / pie / scatter / other)
  • What matters most (approximate trends / precise values / specific data points / categorisation)
  • Known axis values (optional — if the user knows the max/min values to anchor the extraction)

Output Structure

1. Chart Identification

| Attribute | Value | |---|---| | Chart type | [Bar / Line / Pie / Scatter / Area / Other] | | Chart title (if visible) | [Title text] | | X-axis label | [Label + unit] | | Y-axis label | [Label + unit] | | Number of series | N | | Legend categories | [List] | | Data period (if time-based) | [Start — End] |

2. Extracted Data Table

| [X axis] | [Series 1] | [Series 2] | ... | |---|---|---|---| | [Value] | [Value] | [Value] | |

3. Confidence Levels

For each data point or series, flag confidence:

  • High confidence: data points where the value is clearly readable against gridlines or labels
  • Medium confidence: data points where the value is interpolated between gridlines
  • Low confidence: data points where the value is ambiguous or overlaps with other elements

Low-confidence points should be explicitly listed — not silently included in the main table.

4. Notable Observations

Observations that the data itself reveals:

  • Peak value: [Value, when, in which series]
  • Lowest value: [Value, when, in which series]
  • Largest delta between series: [Details]
  • Any anomalies or outliers visible in the chart

5. Reconstructed Source

CSV format for direct use:

[x_axis],[series_1],[series_2]
[value],[value],[value]

6. Assumptions and Caveats

  • Grid resolution: [How precisely values could be read — e.g. "Y-axis has major gridlines every 10 units, minor every 2"]
  • Interpolation used: [Any values that required estimating between gridlines]
  • Unclear data: [Anything in the chart that could not be read reliably]
  • Axis scale: [Linear/logarithmic/etc — note if not obvious]

7. Follow-up Options

Ask the user which of these they want:

  • Rebuild the chart in a specified format (Excel formula, Python matplotlib, D3, etc.)
  • Produce a narrative description of what the chart shows
  • Compare this data against another chart or source
  • Flag potentially misleading visual choices in the original (truncated axes, misleading scales, etc.)

Quality Checks

  • [ ] Every extracted number specifies which series it belongs to
  • [ ] Confidence levels are explicit for ambiguous points
  • [ ] Low-confidence values are flagged separately, not silently included
  • [ ] Assumptions about axis scale and interpolation are stated
  • [ ] CSV output is clean and directly usable

Anti-Patterns

  • [ ] Do not silently include low-confidence data points in the main table — flag them separately so the user knows which values to verify
  • [ ] Do not assume a linear scale without confirming it — logarithmic axes make extracted values incorrect by orders of magnitude if misread
  • [ ] Do not report extracted values with false precision — if the chart's Y-axis only shows gridlines every 10 units, a reported value of 37 is invented, not extracted
  • [ ] Do not omit the assumptions and caveats section — partial image quality, overlapping bars, or unlabelled axes must be disclosed

Example Trigger Phrases

  • "Extract the data from this chart"
  • "Transcribe the numbers in this graph"
  • "Turn this chart image into a spreadsheet"
  • "Digitise this chart so I can rebuild it"
  • "What are the exact values in this bar chart?"

Why This Works Better on Opus 4.7

Earlier models struggled with pixel-level data transcription from charts, often hallucinating values or misreading gridline positions. Opus 4.7 uses a higher image resolution (2576px vs 1568px) with coordinates mapping 1:1 to pixels, making chart data extraction reliable for practical use.

Related Skills

View on GitHub
GitHub Stars1.4k
CategoryDevelopment
Updated6d ago
Forks249

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions