charting-vega-lite
Skill158 starsChanged 8 months agoMITView on GitHub
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 adapted for production.
In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessing-github-reposSkill
- agent-routingSkill
- animating-with-codeSkill
- api-credentialsSkill
- asking-questionsSkill
- assessing-impactSkill
- atprotoingSkill
- bm25Skill
- browsing-blueskySkill
- building-github-indexSkill
- building-github-index-v2Skill
- categorizing-bsky-accountsSkill
- challengingSkill
- chartingSkill
- check-toolsSkill
- cloning-projectSkill
- closing-issuesSkill
- coding-mojoSkill
- compiling-wgslSkill
- composing-htmlSkill
- configuringSkill
- container-layerSkill
- controlling-spotifySkill
- convening-expertsSkill
- converting-filesSkill
- crafting-instructionsSkill
- creating-bookmarkletsSkill
- creating-kbSkill
- creating-mcp-serversSkill
- creating-skillSkill
- creating-videoSkill
- deciding-with-confidenceSkill
- declaring-invariantsSkill
- declaudingSkill
- delegating-with-contextSkill
- describing-productsSkill
- detecting-tips-zonesSkill
- developing-preactSkill
- dispatching-subagentsSkill
- down-skillingSkill
- drawing-videoSkill
- drawing-with-pycairoSkill
- dunking-anonymouslySkill
- exploring-codebasesSkill
- exploring-dataSkill
- extracting-keywordsSkill
- featuringSkill
- fetching-blocked-urlsSkill
- finding-skillsSkill
- flowingSkill
- forecasting-reversoSkill
- gatingSkill
- generating-patchesSkill
- generative-thinkingSkill
- githubbingSkill
- hallucinating-labelsSkill
- hello-demoSkill
- image-to-svgSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 11 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
All data must be embedded as an inline JavaScript constant:
- Distinctive: line 30
Use fetch() to load external files
- Distinctive: line 32
Create separate data files
- Distinctive: line 51
If script fails: Use manual pandas analysis
- Distinctive: line 120
When user specifies chart type (e.g., "make a bar chart"):
- Distinctive: line 139
Use Primary Workflow to create explorer with alternatives
- Distinctive: line 143
Use templates or programmatic builders based on chart type complexity.
- Distinctive: line 155
Never create external data files
- Distinctive: line 158
Verify scripts load: Vega → Vega-Lite → Vega-Embed
- Very specific: line 159
Check data is injected: spec.data = {values: DATA}
- Very specific: line 180
Read spec-builder-patterns.md when building charts programmatically (histogram, boxplot, grouped/stacked bars, multi-line, etc.)
- Very specific: line 182
Read vega-lite-examples-inventory.md when user requests uncommon chart type not in spec-builder-patterns
- Very specific: line 184
Read chart-types.md when validating specific chart requirements or user asks "what chart should I use for..."
- Very specific: line 186
Read advanced-charts.md for complete specs of specialized charts (sankey, waterfall, violin plots, complex layered compositions)
- Very specific: line 188
Read contextual-chart-selection.md for extended domain examples if unfamiliar with data domain (biomedical, financial, IoT, etc.)
- Very specific: line 190
Read online-resources.md to fetch Vega-Lite docs for advanced features (custom selections, transforms, conditional encoding)
- Distinctive: line 227
ALWAYS use inline data island pattern: - No fetch(), no external files
- Distinctive: line 229
Filter by readability: - Avoid charts with too many categories
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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→nominal2. 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 linkView 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
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
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.

