
Data Visualization
Pick the right chart type and generate accessible, publication-quality Python figures with matplotlib, seaborn, or plotly.
Overview
data-visualization is an agent skill most often used in Grow (also Build, Ship) that selects appropriate chart types and produces accessible Python visualizations with matplotlib, seaborn, and plotly.
Install
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill data-visualizationWhat is this skill?
- Chart selection matrix mapping data relationships (trend, comparison, distribution, correlation, geo, flow) to recommend
- Python patterns for matplotlib, seaborn, and plotly with publication-quality and design-principle guidance
- Accessibility and color-theory considerations baked into visualization choices
- Alternatives column per relationship (e.g., lollipop vs bar, violin vs histogram) to avoid wrong-chart mistakes
- Chart selection guide table spans trend, comparison, ranking, composition, distribution, correlation, geographic, and fl
- Three Python visualization libraries documented: matplotlib, seaborn, plotly
Adoption & trust: 8k installs on skills.sh; 19.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have data in Python but keep picking misleading chart types or producing figures that fail accessibility and publication standards.
Who is it for?
Indie builders analyzing metrics, writing technical content, or packaging research who want a chart-type decision tree plus library-ready code.
Skip if: Teams needing a hosted BI dashboard, real-time streaming viz, or non-Python stacks exclusively.
When should I use this skill?
Building charts, choosing chart types for a dataset, creating publication-quality figures, or applying accessibility and color theory.
What do I get? / Deliverables
You get a relationship-driven chart recommendation and implementation patterns for clean, accessible figures ready to drop into reports or product docs.
- Recommended chart type with alternatives for the data relationship
- Python visualization code patterns aligned to the chosen chart
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Analytics and reporting are where solo builders most often need repeatable chart patterns after data exists. The skill centers on interpreting datasets and communicating metrics—core analytics work in the Grow phase.
Where it fits
Embed correlation heatmaps and distribution plots into technical documentation for an API analytics feature.
Plot latency or error distributions after a release to compare regressions across builds.
Turn funnel and retention exports into stacked bars and Sankey-style flow summaries for a weekly metrics review.
How it compares
Opinionated chart-selection plus Python recipes—not a generic notebook tutor or an MCP chart server.
Common Questions / FAQ
Who is data-visualization for?
Solo developers and analysts shipping Python-based reports, blog charts, or internal metrics views who want correct chart grammar and accessible styling.
When should I use data-visualization?
Use it in Grow when reporting analytics, in Build when documenting datasets in docs, and in Ship when visualizing test or performance results for stakeholders.
Is data-visualization safe to install?
Check the Security Audits panel on this Prism page; the skill is instructional Python patterns and should not require secrets unless you point it at private data paths.
SKILL.md
READMESKILL.md - Data Visualization
# Data Visualization Skill Chart selection guidance, Python visualization code patterns, design principles, and accessibility considerations for creating effective data visualizations. ## Chart Selection Guide ### Choose by Data Relationship | What You're Showing | Best Chart | Alternatives | |---|---|---| | **Trend over time** | Line chart | Area chart (if showing cumulative or composition) | | **Comparison across categories** | Vertical bar chart | Horizontal bar (many categories), lollipop chart | | **Ranking** | Horizontal bar chart | Dot plot, slope chart (comparing two periods) | | **Part-to-whole composition** | Stacked bar chart | Treemap (hierarchical), waffle chart | | **Composition over time** | Stacked area chart | 100% stacked bar (for proportion focus) | | **Distribution** | Histogram | Box plot (comparing groups), violin plot, strip plot | | **Correlation (2 variables)** | Scatter plot | Bubble chart (add 3rd variable as size) | | **Correlation (many variables)** | Heatmap (correlation matrix) | Pair plot | | **Geographic patterns** | Choropleth map | Bubble map, hex map | | **Flow / process** | Sankey diagram | Funnel chart (sequential stages) | | **Relationship network** | Network graph | Chord diagram | | **Performance vs. target** | Bullet chart | Gauge (single KPI only) | | **Multiple KPIs at once** | Small multiples | Dashboard with separate charts | ### When NOT to Use Certain Charts - **Pie charts**: Avoid unless <6 categories and exact proportions matter less than rough comparison. Humans are bad at comparing angles. Use bar charts instead. - **3D charts**: Never. They distort perception and add no information. - **Dual-axis charts**: Use cautiously. They can mislead by implying correlation. Clearly label both axes if used. - **Stacked bar (many categories)**: Hard to compare middle segments. Use small multiples or grouped bars instead. - **Donut charts**: Slightly better than pie charts but same fundamental issues. Use for single KPI display at most. ## Python Visualization Code Patterns ### Setup and Style ```python import matplotlib.pyplot as plt import matplotlib.ticker as mticker import seaborn as sns import pandas as pd import numpy as np # Professional style setup plt.style.use('seaborn-v0_8-whitegrid') plt.rcParams.update({ 'figure.figsize': (10, 6), 'figure.dpi': 150, 'font.size': 11, 'axes.titlesize': 14, 'axes.titleweight': 'bold', 'axes.labelsize': 11, 'xtick.labelsize': 10, 'ytick.labelsize': 10, 'legend.fontsize': 10, 'figure.titlesize': 16, }) # Colorblind-friendly palettes PALETTE_CATEGORICAL = ['#4C72B0', '#DD8452', '#55A868', '#C44E52', '#8172B3', '#937860'] PALETTE_SEQUENTIAL = 'YlOrRd' PALETTE_DIVERGING = 'RdBu_r' ``` ### Line Chart (Time Series) ```python fig, ax = plt.subplots(figsize=(10, 6)) for label, group in df.groupby('category'): ax.plot(group['date'], group['value'], label=label, linewidth=2) ax.set_title('Metric Trend by Category', fontweight='bold') ax.set_xlabel('Date') ax.set_ylabel('Value') ax.legend(loc='upper left', frameon=True) ax.spines['top'].set_visible(False) ax.spines['right'].set_visible(False) # Format dates on x-axis fig.autofmt_xdate() plt.tight_layout() plt.savefig('trend_chart.png', dpi=150, bbox_inches='tight') ``` ### Bar Chart (Comparison) ```python fig, ax = plt.subplots(figsize=(10, 6)) # Sort by value for easy reading df_sorted = df.sort_values('metric', ascending=True) bars = ax.barh(df_sorted['category'], df_sorted['metric'], color=PALETTE_CATEGORICAL[0]) # Add value labels for bar in bars: width = bar.get_width() ax.text(width + 0.5, bar.get_y() + bar.ge