claude-d3js-skill

This skill provides guidance for creating sophisticated, interactive data visualisations using d3.js.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The content is highly actionable with extensive executable d3 code examples and a clear core workflow, but it is verbose and heavily duplicates material already present in the reference bundle. Progressive disclosure is undermined by inline duplication and a filename mismatch between referenced and actual asset files.

Suggestions

Move the full 'Scales reference' and per-chart-type pattern code into the existing reference files (scale-reference.md, d3-patterns.md) and replace the inline blocks with brief pointers, keeping SKILL.md as a lean overview.

Fix the asset references so they match the actual files: 'chart-template.jsx' and 'interactive-template.jsx' instead of '.js'.

Add an explicit validation/verification checkpoint to the core workflow (e.g. confirm the SVG rendered and data bound correctly before declaring success) to support error recovery.

Dimension	Reasoning	Score
Conciseness	The body is very long (~820 lines) and duplicates content that already lives in the bundle's reference files — a full 'Scales reference' section parallels scale-reference.md and many chart-pattern code blocks parallel d3-patterns.md — so it is mostly useful but could be tightened considerably, fitting anchor 2 rather than the lean anchor 3.	2 / 3
Actionability	Provides numerous complete, executable, copy-paste-ready functions (bar chart, chord diagram, heatmap, force-directed network, tooltips, zoom) with real d3 APIs, matching the 'fully executable code; copy-paste ready' anchor.	3 / 3
Workflow Clarity	The 'Core workflow' is clearly numbered (set up, choose pattern, structure code, responsive sizing) but contains no explicit validation checkpoints or validate->fix->retry feedback loops within the workflow, so it sits at anchor 2 rather than the checkpoint-driven anchor 3.	2 / 3
Progressive Disclosure	A Resources section lists and describes real reference and asset files (verified to exist), but topics that should live in those separate files are duplicated inline, and the referenced asset names 'chart-template.js'/'interactive-template.js' do not match the actual '.jsx' files on disk, fitting the 'content that should be separate is inline' anchor 2.	2 / 3
	Total	9 / 12 Passed

Description

50%

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 the skill's purpose and domain but is generic and lacks an explicit 'Use when...' trigger clause. It names the d3.js niche yet misses common natural trigger terms and concrete capability listings that would make it more distinctive and complete.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when creating custom, interactive charts, graphs, or data visualisations with d3.js.'

List a few concrete capabilities (e.g. bar/line/scatter charts, force-directed networks, chord diagrams, heatmaps) to raise specificity and distinctiveness.

Include natural trigger variations users actually say, such as 'charts', 'graphs', and 'data viz'.

Dimension	Reasoning	Score
Specificity	Names the domain ('data visualisations using d3.js') and one general action ('creating'), but does not list multiple specific concrete actions like building bar charts, force-directed graphs, or chord diagrams, so it stops at anchor 2 rather than 3.	2 / 3
Completeness	Clearly states what the skill does ('creating sophisticated, interactive data visualisations using d3.js') but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric guidelines caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('d3.js', 'data visualisations', 'interactive') but misses common variations users would say such as 'charts', 'graphs', or 'data viz', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Pins the niche to d3.js, but the bare phrase 'data visualisations' could overlap with other general charting/viz skills and there are no distinct trigger terms to differentiate it, fitting anchor 2 rather than the clearly-distinct anchor 3.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (829 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 615669b

Reviewed: 1 day 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.