D3 visualization

Skill nexu-io/open-design/skills/d3-visualization

Teaches the agent to produce D3 charts and interactive data visualizations. A comprehensive D3.js skill with examples across chart types and techniques giving the agent expert-level knowledge to generate complex, interactive visualizations. Useful for editorial dashboards, reports, data-rich prototypes, and explanatory graphics.From its SKILL.md

Install

npx -y skills add nexu-io/open-design --skill d3-visualization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

runs commandsInstructs the agent to run 1 command, including `git clone https://github.com/jiannanya/snow-d3.git skills/snow-d3`.

SKILL.md

2.0 KB, 307 tokens by cl100k_base, as published. Nobody here has run it

d3-visualization

Curated from @jiannanya.

What it does

Source

Upstream: https://github.com/jiannanya/snow-d3/
Category: diagrams

How to use

This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and reference documents, install the upstream bundle into your active agent's skills directory:

# Inspect the upstream README for exact paths
open https://github.com/jiannanya/snow-d3/

# Clone or copy the snow-d3/ folder into your workspace's skills/ directory
git clone https://github.com/jiannanya/snow-d3.git skills/snow-d3

Then ask the agent to invoke this skill by name (d3-visualization) or with one of the trigger phrases listed in this skill's frontmatter, e.g.:

"Create a zoomable treemap for my sales data" "Build a force-directed network graph like example 07 but for my own dataset" "Generate a calendar heatmap in D3"

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most data analysis skills give in 307 tokens

Counted across 230 of the 242 authors here whose files we hold, read 2026-09-06

Propose a regression test for each fixed bugin 16 of 230, across 12 files
Name tests after the bug they preventin 14 of 230, across 10 files
Test the API response shape, not the implementationin 14 of 230, across 10 files
Run the test suite before any code reviewin 14 of 230, across 10 files
Force sandbox mode in the test setupin 14 of 230, across 10 files
Write regression tests only for bugs already foundin 14 of 230, across 10 files
Assert sandbox and production paths return the same shapein 14 of 230, across 10 files
Clear stale state when setting an errorin 13 of 230, across 9 files
Keep the whole test suite under one secondin 10 of 230, across 6 files
Run the build type check before code reviewin 10 of 230, across 6 files
Use vectorized operations instead of row iterationin 9 of 230, across 6 files
Start bar chart Y-axes at zeroin 8 of 230, across 7 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.