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.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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 lean, highly actionable rule set with concrete D3 API guidance and a well-structured, verified reference split. Its main gap is that the 'Working Pattern' is a sequenced checklist without explicit validation or feedback-loop checkpoints.

Suggestions

Add an explicit validation/verification checkpoint to the Working Pattern (e.g., a 'finish' step that confirms svg-polish-and-crispness checks pass and the chart recomputes for mobile before declaring done), to lift workflow_clarity above 2.

Introduce a short feedback loop (validate → fix → re-validate) for the export/rebuild path so the workflow qualifies as having explicit error-recovery steps.

Consider one minimal copy-paste-ready D3 code skeleton in Core Building Blocks to make the actionability even more concrete for users who want a starting point.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no 'D3 is a JavaScript library...') and packs each line with concrete defaults and rules, so every token earns its place per the lean-and-efficient anchor.

3 / 3

Actionability

Highly actionable guidance with specific API calls ('.tickSizeOuter(0)', 'shape-rendering: crispEdges', 'vector-effect: non-scaling-stroke') and concrete px defaults; per the scoring note, absence of full code snippets in an instruction-only skill is not penalized when guidance is this concrete.

3 / 3

Workflow Clarity

The 'Working Pattern' gives a numbered sequence but reads as a best-practice checklist rather than a workflow with explicit validation checkpoints or fix/retry feedback loops, matching the steps-listed-but-checkpoints-missing level-2 anchor.

2 / 3

Progressive Disclosure

Clear sectioned overview with well-signaled one-level-deep references; all referenced local bundle files exist (d3-module-map.md, d3-architecture-patterns.md, d3-interaction-and-annotation.md, d3-pitfalls-and-scale-limits.md, svg-polish-and-crispness.md), and dense material like svg-polish is correctly split into a separate file.

3 / 3

Total

11

/

12

Passed

Description

100%

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 third-person, concise, and clearly states both what the skill does and when to use it with concrete natural-language triggers. It carves out a distinct D3/SVG visualization niche and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Build custom data visualizations', 'SVG or DOM-based charts', 'rich annotation', 'data joins', 'custom scales or interactions', 'scroll-driven SVG scene states' — matching the multiple-specific-actions anchor rather than the single-action level 2.

3 / 3

Completeness

Explicitly answers what ('Build custom data visualizations with D3') and when ('Use when the user needs...'), with an explicit 'Use when' clause that the level-2 anchor lacks.

3 / 3

Trigger Term Quality

Natural user-facing terms ('charts', 'annotation', 'data visualization', 'scales', 'interactions') appear alongside technical triggers; coverage matches the good-coverage anchor and is above the some-relevant-keywords level 2.

3 / 3

Distinctiveness Conflict Risk

Scoped to D3/SVG/DOM browser visualization with distinct triggers unlikely to collide with non-visualization skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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.