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

The canonical home for this skill is claude-d3js-skill in sickn33/agentic-awesome-skills

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 highly actionable, executable d3 code with a clear workflow and real validation habits, but it fails as an overview: it inlines hundreds of lines that duplicate its own reference files, explains concepts Claude already knows, and lists asset filenames that don't match the actual bundle. Trimming the body to a pattern index with pointers into references/ would fix its two weakest dimensions at once.

Suggestions

Move the full pattern implementations (chord diagram, heatmap, pie, force-directed network) and the "Scales reference" section into references/d3-patterns.md and references/scale-reference.md, keeping only a one-line-per-pattern index in SKILL.md with pointers to those files.

Fix the asset filenames in the Resources section to match the actual bundle files (chart-template.jsx and interactive-template.jsx, not chart-template.js / interactive-template.js).

Replace the comment-only "Performance optimisation" and "Accessibility" code blocks with either a short bulleted list or concrete code, and drop the Overview paragraph explaining what D3.js is.

DimensionReasoningScore

Conciseness

The ~820-line body is noticeably verbose: the Overview explains what D3.js is, a full "Scales reference" section re-lists d3's scale API (which Claude already knows), and complete chord/heatmap/pie/force implementations duplicate content that the bundled references/d3-patterns.md and references/scale-reference.md exist to hold. It stays above a 1 because the bulk is substantive, usable code rather than tutorial prose.

2 / 5

Actionability

Mostly executable, copy-paste-ready functions (drawBarChart, drawChordDiagram and drawHeatmap with documented data formats, responsive setup with cleanup, drag handlers, tooltips). Minor gaps keep it from a 5: the line/pie/scatter snippets depend on undefined setup variables, and the "Performance optimisation" block is comment-only with no code.

4 / 5

Workflow Clarity

A clear numbered core workflow (set up d3 → choose integration pattern → structure the code → responsive sizing) with data validation present in every code example ("if (!data || data.length === 0) return") plus a "Common issues and solutions" section for error recovery. No explicit post-render verification checkpoint, so not a 5.

4 / 5

Progressive Disclosure

References are real, one level deep, and listed in a descriptive Resources section, but content that clearly belongs in them — the full scales reference and the chord/heatmap/pie/force pattern implementations — is inlined in the body, duplicating the actual reference files. Additionally, the Resources section lists "chart-template.js" and "interactive-template.js" while the actual asset files are chart-template.jsx and interactive-template.jsx, so the referenced paths don't resolve.

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.

A strong description: it states concrete capabilities in third person, gives two explicit and specific when-to-use clauses, and carves out a clear niche with a boundary against standard charting libraries. The only gaps are minor missing trigger synonyms and the fact that all capabilities are phrased as variations of one action (creating visualisations).

DimensionReasoningScore

Specificity

Names the domain and several specific capability types ("custom charts, graphs, network diagrams, geographic visualisations", "fine-grained control over visual elements, transitions, or interactions"), but everything sits under the single verb "creating", short of the multi-action comprehensiveness of a 5.

4 / 5

Completeness

Explicitly answers both what ("Creating interactive data visualisations using d3.js" with concrete capability types) and when, with two explicit trigger clauses: "This skill should be used when creating custom charts, graphs, network diagrams..." and "Use this for bespoke visualisations beyond standard charting libraries".

5 / 5

Trigger Term Quality

Good natural-term coverage ("charts", "graphs", "network diagrams", "d3.js", "interactive", "bespoke"), but a few common variants users would say are missing, e.g. "plot", "map", and the US spelling "visualization".

4 / 5

Distinctiveness Conflict Risk

Clear d3.js niche with an explicit boundary against "standard charting libraries", but "custom charts, graphs" could also plausibly match a generic charting skill, leaving minor overlap risk.

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.