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.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/d3-visualization/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, lean catalogue entry that clearly directs the user to install the upstream bundle, and it includes runnable clone commands and example prompts. Its weakness is that it contains none of the actual skill content locally — the real D3 knowledge, examples, and scripts are one unverified URL away, and the post-clone workflow is delegated to an external README rather than stated. Bundling key references or an explicit post-install checklist would materially improve it.

Suggestions

State the exact post-clone steps locally (expected folder layout, how the agent should resolve 'skills/snow-d3') instead of deferring to 'Inspect the upstream README for exact paths' — this is the main gap hurting both actionability and workflow clarity.

Add a validation checkpoint after installation (e.g., 'verify skills/snow-d3/SKILL.md exists and the trigger phrases load') so the install workflow has a feedback loop.

Bundle at least one concrete D3 quick-start example or reference file locally (e.g., references/examples.md) so the skill delivers some value without network access to the upstream repo, and remove the verbatim duplication of the description in 'What it does'.

Dimension	Reasoning	Score
Conciseness	The body is short and sectioned, but "What it does" repeats the frontmatter description verbatim and "This catalogue entry advertises the skill in OpenDesign so the agent discovers it during planning" is meta-padding that adds no instructional value. It is a 4 rather than 3 because there is no concept over-explanation (no D3 tutorials, no library background), and not a 5 because of the verbatim duplication and meta commentary.	4 / 5
Actionability	There is one concrete, executable command ("git clone https://github.com/jiannanya/snow-d3.git skills/snow-d3") plus example invocation prompts, but the critical step — what to do after cloning — is deferred entirely off-site ("Inspect the upstream README for exact paths"), and there is zero local D3 guidance, code, or examples. It is above a 2 because the clone command and invocation examples are specific and runnable, but below a 4 because the key steps to actually use the skill are missing.	3 / 5
Workflow Clarity	A rough sequence exists (inspect upstream README → clone into skills/ → invoke by name or trigger), but step 1 is a gap-filler that delegates the real workflow to an external README, and there is no validation that the install landed in the right place. It is above a 2 because the steps are coherent and in a sensible order, and below a 4 because a checkpoint (verifying the install path / that the agent recognizes the skill) is absent and the sequence has an unresolved hole.	3 / 5
Progressive Disclosure	No local bundle files exist (no references/, scripts/, or assets/ directories), so the body is evaluated as a short standalone entry: it has clear sections (What it does, Source, How to use) and a single one-level-deep pointer to the upstream repo. It is above a 3 because the structure is clean and nothing is inlined that belongs elsewhere, but below a 5 because the advertised assets/scripts/references live entirely off-repo behind an unverified URL, so navigation to the actual skill content is not self-contained.	4 / 5
	Total	14 / 20 Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states what the skill does and anchors it to a specific library (D3.js), but it leans on marketing-style over-claims ("expert-level knowledge", "comprehensive") instead of concrete capability listings, and it lacks an explicit 'Use when...' trigger clause. Adding explicit trigger guidance and specific chart-type capabilities would raise both completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for D3 charts, interactive visualizations, or editorial graphics' — this directly lifts the completeness score, which is capped at 3 without one.

Replace the vague claims ('expert-level knowledge to generate complex, interactive visualizations') with 2-3 concrete actions such as 'build bar, line, treemap, sankey, and force-directed charts with zoom and scroll animations'.

Include natural trigger variations users say ('graph', 'plot', 'data viz') to move trigger-term coverage from good to comprehensive.

Dimension	Reasoning	Score
Specificity	The description names the domain ("D3.js") and one concrete action ("produce D3 charts and interactive data visualizations") but pads the rest with over-claims like "expert-level knowledge to generate complex, interactive visualizations" rather than listing specific actions. It is above a 2 because a real concrete action is stated with the domain, but below a 4 because no enumeration of distinct capabilities (e.g., chart types, techniques, or outputs) is given.	3 / 5
Completeness	The 'what' is clear ("Teaches the agent to produce D3 charts and interactive data visualizations"), but there is no explicit 'Use when...' clause — the closest is the weakly implied "Useful for editorial dashboards, reports, data-rich prototypes, and explanatory graphics", which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is fully stated, and not a 4 because the 'when' is contextual description rather than explicit trigger guidance.	3 / 5
Trigger Term Quality	Natural phrases a user would say are present: "D3 charts", "interactive data visualizations", "editorial dashboards", "reports", "explanatory graphics". It is below a 5 because common variations users actually say are missing ("graph", "plot", "chart types", file/format terms), and above a 3 because coverage goes beyond a couple of generic keywords.	4 / 5
Distinctiveness Conflict Risk	The D3-specific framing ("D3.js skill", "D3 charts") carves out a clear niche distinct from document or code skills, with only minor overlap risk against generic charting/visualization skills via broad phrases like "data visualization". It is not a 5 because those broad dataviz phrases could overlap with general chart libraries, and no library-specific triggers appear in the description itself.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/d3-visualization/SKILL.md
Commit: 1b47e60

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.