claude-d3js-skill

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

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/claude-d3js-skill/SKILL.md

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

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 is highly actionable with executable d3 code and a clear core workflow, but it is verbose — inlining pattern and scale content that duplicates the bundle references — and its asset references point to nonexistent .js filenames instead of the actual .jsx files.

Suggestions

Trim the inline pattern implementations and 'Scales reference' section into pointers to d3-patterns.md and scale-reference.md so SKILL.md stays a lean overview.

Fix the asset filenames in the Resources section from chart-template.js/interactive-template.js to the actual chart-template.jsx/interactive-template.jsx.

Add a brief render-verification checkpoint to the core workflow (e.g., confirm the svg rendered and check the console for d3 errors) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The ~815-line body inlines full pattern implementations (chord, heatmap, force-directed) and a complete 'Scales reference' section that duplicate the provided references/ files, constituting several padded sections rather than a lean overview; this fits the 'noticeably verbose; several unnecessary padded sections' anchor below the efficient midpoint.	2 / 5
Actionability	It provides concrete, executable d3 v7 code for most chart types (full functions for bar/heatmap/chord), but the line, scatter, pie, and force-directed examples are fragments lacking the surrounding svg/group setup, leaving minor gaps versus the fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The 'Core workflow' lays out a clear numbered sequence (setup, choose pattern, structure code, responsive sizing), and while there are no explicit render/validation checkpoints, this is a non-destructive visualisation skill so the gaps are minor, fitting anchor 4 over the checkpoint-absent anchor 3.	4 / 5
Progressive Disclosure	A Resources section clearly signals the one-level-deep reference and asset files, but substantial content that belongs in those files (full pattern code, scales reference) is inlined, and the asset paths are wrong (body says chart-template.js/interactive-template.js while the real files are .jsx), so it fits the 'content that should be separate is inline' anchor rather than the well-placed anchor 4.	3 / 5
	Total	13 / 20 Passed

Description

53%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 clearly states what the skill does and targets a reasonably distinct d3.js niche, but it omits any explicit use-when trigger guidance and lacks common chart/graph synonyms that users would naturally say.

Suggestions

Add a 'Use when...' clause naming concrete triggers, e.g. 'Use when building custom or interactive charts, graphs, or data visualisations with d3.js'.

Include common synonyms like "chart", "graph", and "plot" so the description matches natural user phrasing.

Drop the filler phrase 'provides guidance for' and lead with the concrete action verbs.

Dimension	Reasoning	Score
Specificity	The description names the domain (d3.js) and one concrete action — "creating sophisticated, interactive data visualisations" — but lists no further specific actions, matching the 'names domain and 1 concrete action, not comprehensive' anchor rather than the multi-action anchor 5 or the minimal-action anchor 2.	3 / 5
Completeness	It gives a clear 'what' (guidance for creating d3.js visualisations) but has no 'when'/Use-when clause; per the rubric's cap, a missing explicit trigger guidance limits completeness to 3, matching the 'clear what but when missing' anchor.	3 / 5
Trigger Term Quality	It contains relevant natural terms ("data visualisations", "interactive", "d3.js") but omits common synonyms a user would say such as "chart", "graph", "plot", or "dashboard", fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The d3.js niche is fairly distinct, but the broad term "data visualisations" carries minor overlap risk with general charting/dataviz skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict anchor 5.	4 / 5
	Total	13 / 20 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 (824 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/claude-d3js-skill/SKILL.md
Commit: 57c135b

Reviewed: 2 days 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.