Install Charting Vega Lite
Pick your agent. Every command is ready to paste.
npx skills add oaustegard/claude-skills --skill charting-vega-liteThe open skills CLI detects your agents (Claude Code, Cursor, Codex and 70+ more) and installs to the right folder. Add -g to install globally.
01
Install it
Run the command above, or upload the folder in Claude.
02
Ask naturally
Describe the task. Your agent loads charting-vega-lite when the request matches its description.
03
Name it if needed
If it does not trigger, say “use the charting-vega-lite skill”. In Codex, type $charting-vega-lite.
Overview
This skill creates interactive Vega-Lite visualizations from uploaded data. The workflow:
- Analyze data structure and context
- Select 5-10 meaningful chart types based on what the data represents
- Build chart specifications programmatically
- Generate React artifact with embedded visualizations
Critical Technical Constraint: Inline Data Island
Claude artifacts cannot use fetch() for computer:// URLs.
All data must be embedded as an inline JavaScript constant:
const DATA = [ /* embedded data array */ ];
// Later in chart specs:
spec.data = { values: DATA };
DO NOT:
- Use fetch() to load external files
- Reference external data URLs
- Create separate data files
This is the only pattern that works in Claude's artifact environment.
Primary Workflow: Data Upload → Chart Explorer
Execute this sequence when user uploads data without specifying chart type:
1. Analyze Data Structure
python /mnt/skills/user/charting-vega-lite/scripts/analyze_data.py /mnt/user-data/uploads/<filename>
Extract from output:
fields[](with types and statistics)suggested_charts[](suggested chart types with encodings)sample_data(first 10 rows for understanding context)
If script fails: Use manual pandas analysis
import pandas as pd
df = pd.read_csv('/mnt/user-data/uploads/<filename>')
# Classify: numeric→quantitative, datetime→temporal, <20 unique→nominal
2. Understand Data Context
Read sample data and column names to infer what the data represents:
- Biomedical data? → Biomarkers, patient outcomes, clinical relevance
- Financial data? → Trends, comparisons, performance metrics
- Sensor data? → Temporal patterns, anomalies, correlations
- E-commerce? → Sales trends, product comparisons, conversions
Ask: What questions would someone analyzing this data want answered?
Examples:
- Assay data: Which biomarkers strongest? Patterns across samples? Variability?
- Financial: What are trends? How volatile? Seasonal patterns?
- IoT: Temporal patterns? Anomalies? Sensor correlations?
3. Select Meaningful Charts (5-10 suggestions)
Filter analyze_data.py suggestions based on context and readability:
Apply readability filters:
- Pie chart with >7 categories → Skip (unreadable)
- Heatmap with >50 categories per axis → Aggregate first
- Multi-line with >10 series → Consider faceting
Prioritize charts that answer domain questions:
- Comparison needs → Bar, box plot, grouped bar
- Distribution analysis → Histogram, box plot
- Pattern recognition → Heatmap, scatter
- Temporal trends → Line, area
- Part-to-whole → Stacked bar (pie only if <7 categories)
Don't suggest charts just because data types match - choose charts that reveal insights.
4. Generate Chart Specs
Build specs programmatically using analyze_data.py encodings:
For each suggested chart type, construct spec using:
- Templates from
assets/templates/for basic types (bar, line, scatter, pie, heatmap, area) - Builder patterns from
references/spec-builder-patterns.mdfor variations (histogram, boxplot, grouped-bar, etc.) - Vega-Lite examples from
references/vega-lite-examples-inventory.mdfor uncommon types
Structure each chart as:
{"type": "Chart Name", "reason": "Why this chart", "spec": {/* vega-lite spec */}}
5. Create Artifact with Inline Data Island
Load data, read template, replace __DATA__ and __CHART_SPECS__ placeholders, write using bash heredoc.
6. Provide Link
[View chart explorer](computer:///mnt/user-data/outputs/ChartExplorer.jsx)
Created 7 contextually relevant charts for your data.
Secondary Workflow: Specific Chart Request
When user specifies chart type (e.g., "make a bar chart"):
1. Analyze Data
python /mnt/skills/user/charting-vega-lite/scripts/analyze_data.py /mnt/user-data/uploads/<filename>
2. Validate Chart Fits Data
Check requirements:
- Bar: needs 1 nominal + 1 quantitative
- Line: needs 1 temporal + 1 quantitative
- Scatter: needs 2 quantitative
- Heatmap: needs 2 nominal + 1 quantitative
- Pie: needs 1 nominal + 1 quantitative + <7 categories
If data doesn't fit:
- Explain: "Bar chart needs categorical data, but all columns are numeric"
- Suggest 2-3 alternatives
- Use Primary Workflow to create explorer with alternatives
3. Generate Spec
Use templates or programmatic builders based on chart type complexity.
4. Create Artifact
Same pattern as Primary Workflow step 5, but with single chart.
Error Prevention
Common failures:
Using fetch() in artifacts
- Solution: Always use inline data island pattern
- Never create external data files
Chart doesn't render
- Verify scripts load: Vega → Vega-Lite → Vega-Embed
- Check data is injected:
spec.data = {values: DATA} - Confirm field names match data columns
Generic/random chart suggestions
- Solution: Consider data context and meaning
- Filter suggestions for relevance and readability
- Prioritize charts that answer meaningful questions
Resources
Scripts:
scripts/analyze_data.py- analyze structure, suggest 8-12 chart types
Components:
assets/components/ChartExplorer.jsx- multi-chart explorer template
Templates:
assets/templates/*.json- 6 basic chart templates (bar, line, scatter, pie, heatmap, area)
References - Progressive Disclosure:
Read spec-builder-patterns.md when building charts programmatically (histogram, boxplot, grouped/stacked bars, multi-line, etc.)
Read vega-lite-examples-inventory.md when user requests uncommon chart type not in spec-builder-patterns
Read chart-types.md when validating specific chart requirements or user asks "what chart should I use for..."
Read advanced-charts.md for complete specs of specialized charts (sankey, waterfall, violin plots, complex layered compositions)
Read contextual-chart-selection.md for extended domain examples if unfamiliar with data domain (biomedical, financial, IoT, etc.)
Read online-resources.md to fetch Vega-Lite docs for advanced features (custom selections, transforms, conditional encoding)
Complete Workflow Example
User uploads assay data CSV (51 assays, 74 samples)
# 1. Analyze
python /mnt/skills/user/charting-vega-lite/scripts/analyze_data.py /mnt/user-data/uploads/assay_data.csv
# 2. Understand context: Multi-analyte immunoassay
# Questions: Which biomarkers strongest? Patterns across samples? Variability?
# 3. Build contextual charts (5-7 specs)
# Bar: Mean signal by assay
# Heatmap: Sample × Assay
# Box plot: Signal distribution by assay
# Histogram: Overall signal distribution
# etc.
# 4. Load data and template
df = pd.read_csv('/mnt/user-data/uploads/assay_data.csv')
data = df.to_dict(orient='records')
template = open('/mnt/skills/user/charting-vega-lite/assets/components/ChartExplorer.jsx').read()
# 5. Replace placeholders and write
artifact = template.replace('__DATA__', json.dumps(data)).replace('__CHART_SPECS__', json.dumps(charts))
# Use bash heredoc to avoid XML conflicts in tool parameters
# 6. Provide link
View chart explorer
Created 7 charts for your assay data - bar charts show biomarker signals, heatmap reveals sample patterns, box plots display variability.
Critical Rules
- ALWAYS use inline data island pattern - No fetch(), no external files
- Consider data context - Choose meaningful charts based on what data represents, not just data types
- Filter by readability - Avoid charts with too many categories
- Use bash heredoc for file creation - Prevents XML conflicts when creating artifacts
- Provide links, not content - Output token efficiency
Tips for Charting Vega Lite
- • Start a fresh session after installing so your agent picks up the new skill.
- • This skill ships scripts. Read them before the first run, and run it in a project without secrets first.
- • It bundles reference files. The agent reads them only when needed, so they cost no context until then.
- • It is part of a pack with 30 skills. Install only the ones you need with --skill to keep triggers precise.
- • If two skills overlap, mention the one you want by name.
Questions about Charting Vega Lite
What does the Charting Vega Lite skill do?
Create interactive data visualizations using Vega-Lite declarative JSON grammar. Supports 20+ chart types (bar, line, scatter, histogram, boxplot, grouped/stacked variations, etc.) via templates and programmatic builders. Use when users upload data for charting, request specific chart types, or mention visualizations. Produces portable JSON specs with inline data islands that work in Claude artifacts and can be adapt
How do I install Charting Vega Lite?
Run "npx skills add oaustegard/claude-skills --skill charting-vega-lite" in your project. The skills CLI installs it for Claude Code, Cursor, Codex and 70+ other agents. In Claude on the web, upload the skill folder as a ZIP under Customize > Skills.
Does Charting Vega Lite work in Cursor and Codex?
Yes. Charting Vega Lite uses the open SKILL.md format, so it works in Claude Code, Claude, Cursor, OpenAI Codex, Gemini CLI, GitHub Copilot and other agents that support agent skills.
Is Charting Vega Lite free?
Charting Vega Lite is open source on GitHub under the MIT license. It is free to install; check the license before commercial use.
Who made Charting Vega Lite?
Charting Vega Lite is published by oaustegard in the oaustegard/claude-skills repository, together with 29 other skills.

