CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

d3-viz

Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/d3-viz/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers strong, mostly executable d3.js guidance with a clear workflow and well-organized bundle files, but it is noticeably over-long: it explains basics Claude already knows and duplicates large amounts of content that already lives in its own reference files. Trimming the body to an overview plus pointers would materially improve token efficiency and progressive disclosure.

Suggestions

Move the full chord diagram, heatmap, and "Scales reference" sections into references/d3-patterns.md and references/scale-reference.md (where equivalent content already exists), replacing them in SKILL.md with one-line pointers — the body duplicates roughly 200+ lines of its own bundle files.

Delete the Overview paragraph explaining what D3.js is and the "When to use d3.js" section that restates the frontmatter description, keeping only the alternatives pointer (Three.js for 3D); this assumes Claude's competence and cuts pure token overhead.

Make the fragment snippets (line, pie, scatter, force-directed) self-contained by noting required setup or folding them into the complete structure example, so all code is copy-paste ready rather than context-dependent.

DimensionReasoningScore

Conciseness

The Overview explains what D3.js is ("D3.js (Data-Driven Documents) excels at binding data to DOM elements..."), a concept Claude already knows, and the body inlines a full chord diagram (~75 lines), a full heatmap (~100 lines), and an entire "Scales reference" section that duplicate the dedicated references/d3-patterns.md and references/scale-reference.md files — several unnecessary and padded sections. Not 3 because the duplication and over-explanation are extensive rather than incidental; not 1 because most of the body is dense, usable code rather than tutorial-style prose padding.

2 / 5

Actionability

Mostly executable guidance: complete functions like drawBarChart, drawChordDiagram, and setupResponsiveChart with documented data formats ("data format: array of objects with source, target, and value"), plus working drag, tooltip, zoom, and transition snippets. Not 5 because Pattern A contains a "// ... d3 code here ..." placeholder and the line/pie/scatter/force snippets are fragments relying on implicit undefined context (g, xScale, svg, width).

4 / 5

Workflow Clarity

The core workflow is clearly sequenced (set up d3 → choose integration pattern → structure the code → responsive sizing) with explicit decision criteria for Pattern A vs B and an error-recovery "Common issues and solutions" section. Not 5 because the workflow itself contains no explicit validation checkpoints (data-validation guidance appears only under best practices); not 3 because the sequence, decision guidance, and troubleshooting provide most checkpoints. No destructive/batch cap applies since chart rendering is non-destructive.

4 / 5

Progressive Disclosure

The bundle structure is sound — all listed files (references/d3-patterns.md, scale-reference.md, colour-schemes.md, assets/*.jsx, sample-data.json) exist, are one level deep, and the Resources section describes each — but roughly 200+ lines of content that belongs in those reference files (chord diagram, heatmap, scales reference) are inlined in the body. This matches the anchor where content that should be separate is inline despite references being present; not 4 because the split is poorly executed through substantial duplication, not 2 because structure and reference signaling are clear rather than buried.

3 / 5

Total

13

/

20

Passed

Description

83%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 is strong: it answers both what and when explicitly, uses third-person voice, and lists concrete visualisation types as triggers with an explicit differentiation from standard charting libraries. The main weaknesses are a few missing natural synonyms (plot, map) and slight generic-trigger overlap with general charting skills.

DimensionReasoningScore

Specificity

"Creating interactive data visualisations using d3.js" plus "custom charts, graphs, network diagrams, geographic visualisations" names the domain and several concrete artifact types, matching the anchor for several specific actions with minor gaps. Not 5 because action coverage centers on chart types rather than a comprehensive action list (no tooltips, zoom, or animation capabilities named); not 3 because well more than 1-2 concrete actions are listed. Voice is third person throughout, so no pronoun penalty applies.

4 / 5

Completeness

Both questions are explicitly answered: what ("Creating interactive data visualisations using d3.js") and when ("This skill should be used when creating custom charts, graphs, network diagrams... Use this for bespoke visualisations beyond standard charting libraries"). The when-clause includes multiple concrete trigger phrases plus environment guidance, matching the anchor-5 example structure; a 4 would require a less explicit or less specific when-clause, which this exceeds.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered: "charts", "graphs", "network diagrams", "geographic visualisations", "custom", "bespoke visualisations", matching good keyword coverage with a few natural terms missing. Not 5 because common synonyms like "plot", "map", or plain "diagram" are absent, though no file extensions are relevant to this domain.

4 / 5

Distinctiveness Conflict Risk

"Bespoke visualisations beyond standard charting libraries" and "fine-grained control over visual elements, transitions, or interactions" actively carve a niche from generic charting skills, matching the mostly-distinct anchor. Not 5 because the generic triggers "custom charts, graphs" still carry minor overlap risk with a general charting skill; not 3 because the differentiation is explicit rather than merely implied.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (821 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

calesthio/OpenMontage

Path

.agents/skills/d3-viz/SKILL.md

Reviewed

Table of Contents

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.