CtrlK
BlogDocsLog inGet started
Tessl Logo

d3-data-visualization

Build custom data visualizations with D3. Use when the user needs SVG or DOM-based charts, rich annotation, domain-native contextual backgrounds, data joins, custom scales or interactions, scroll-driven SVG scene states, or precise control over browser visualization behavior.

65

Quality

78%

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 ./plugins/build-web-data-visualization/skills/d3-data-visualization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured, opinionated skill body that externalizes detail to real one-level references and encodes highly specific actionable defaults. The main gaps are the absence of complete code examples and explicit validate/feedback loops in the working pattern.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific opinionated defaults (exact px values, CSS properties, D3 methods) and mostly avoids explaining concepts Claude already knows, but the 'Core D3 Building Blocks' module list and the lengthy 'Editorial Defaults' section include minor trimmable over-explanation, keeping it just below a 5.

4 / 5

Actionability

Guidance is concrete and specific ('10-12 px axis ticks', 'shape-rendering: crispEdges', '.tickSizeOuter(0)', 'vector-effect: non-scaling-stroke', explicit reference paths), so the absence of full code blocks is not heavily penalized for this instruction-oriented skill; minor gaps in complete executable examples hold it at 4 rather than 5.

4 / 5

Workflow Clarity

The 10-step 'Working Pattern' is a clear, ordered sequence with a 'before calling the chart finished' checkpoint and an 'Output Expectations' checklist, but there is no explicit validate-then-fix feedback loop, leaving minor validation gaps.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references; all five local bundle files (d3-module-map, d3-architecture-patterns, d3-interaction-and-annotation, d3-pitfalls-and-scale-limits, svg-polish-and-crispness) are present and cited, and detailed polish is appropriately externalized to the svg-polish reference.

5 / 5

Total

17

/

20

Passed

Description

78%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 with an explicit 'Use when' trigger clause and clear domain framing, distinguished by concrete trigger phrases. Its main weakness is action specificity, since only one concrete verb ('Build') is given while the rest of the text enumerates scenarios rather than actions.

Suggestions

Add one or two more concrete action verbs (e.g., 'generate', 'wire up', 'export') so the 'what' lists several specific actions rather than a single verb.

Soften or relocate jargon triggers like 'data joins' and 'scroll-driven SVG scene states' toward phrasings a user would actually say, or pair them with natural synonyms.

Clarify the boundary against the sibling scrollytelling skill in the trigger clause to reduce overlap on scroll-driven scene work.

DimensionReasoningScore

Specificity

It names the domain clearly ('Build custom data visualizations with D3') but offers only one concrete action verb; the remaining 'Use when' clauses list capabilities/scenarios rather than distinct actions Claude performs, so coverage is not comprehensive as required for a 4 or 5.

3 / 5

Completeness

It explicitly answers both 'what' ('Build custom data visualizations with D3.') and 'when' via a concrete 'Use when the user needs...' clause enumerating specific triggers, matching the anchor that requires explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms like 'data visualizations', 'D3', 'charts', 'SVG', 'custom scales', and 'interactions' give good keyword coverage, but jargon such as 'data joins', 'scroll-driven SVG scene states', and 'domain-native contextual backgrounds' are not phrases users naturally say, and common chart-type synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The D3 custom-visualization niche is clearly distinct with specific triggers, but 'scroll-driven SVG scene states' overlaps with a sibling scrollytelling skill and several related viz skills are referenced, creating minor overlap risk rather than minimal conflict.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.