CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-d3js-skill

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

52

Quality

57%

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 ./skills/claude-d3js-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 a concise, well-organised overview that correctly delegates detail to a reference and states clear scope and limitations. Its weakness is execution: it provides no inline code, numbered workflow steps, or validation checkpoints, and only one of several bundle files is linked from the body.

Suggestions

Add a minimal inline 'Quick start' code snippet (e.g. a basic d3 scale + selection) so Claude can act without first loading the reference.

Surface the other references and assets from the body with signalled links, e.g. an 'Advanced features' section pointing to d3-patterns.md, scale-reference.md, colour-schemes.md, and the templates in assets/.

Add a short numbered workflow with an explicit validation/preview checkpoint before treating output as final, even if detail lives in the guide.

DimensionReasoningScore

Conciseness

The body is lean, delegates the full procedure to a reference, and assumes Claude's competence; only the elaboration on focused vs end-to-end reading is mildly trimmable.

4 / 5

Actionability

The 'When to use' and 'Consider alternatives' bullets are concrete scoping guidance, but the body contains no executable d3.js code or step-by-step instructions—those are deferred to the reference rather than shown inline.

3 / 5

Workflow Clarity

A rough sequence exists via the 'read the detailed guide, treat prerequisites/validation as mandatory' instruction, but the body lists no numbered steps and validation checkpoints are only implicitly referenced in the guide, not surfaced here.

3 / 5

Progressive Disclosure

The body is a well-structured overview with a clearly signalled one-level reference to detailed-guide.md; however the three other references (colour-schemes, d3-patterns, scale-reference) and the three assets are not surfaced or linked from the body.

4 / 5

Total

14

/

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 identifies the d3.js data-visualisation domain but reads as a single general sentence rather than an action-and-trigger statement. It lacks an explicit 'Use when…' trigger clause and enumerates no concrete actions, so it lands at the midpoint across most dimensions.

Suggestions

Replace 'provides guidance for creating' with concrete actions, e.g. 'Create custom interactive charts, force-directed graphs, geographic projections, and animated transitions using d3.js.'

Add an explicit trigger clause: 'Use when the user needs custom or interactive data visualisations, charts, graphs, or non-standard chart types that off-the-shelf libraries cannot handle.'

Include natural synonyms users say ('charts', 'graphs', 'plots') alongside 'data visualisations' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain (d3.js data visualisations) and the action of creating them, but 'provides guidance for' with 'sophisticated, interactive' is generic framing rather than a list of concrete capabilities.

3 / 5

Completeness

There is a clear 'what' (creating interactive data visualisations with d3.js) but no explicit 'Use when…' clause, which caps completeness at 3 per the rubric guidance.

3 / 5

Trigger Term Quality

'data visualisations', 'd3.js', and 'interactive' are relevant terms, but common user phrases such as 'charts', 'graphs', 'plots', or 'interactive charts' are absent.

3 / 5

Distinctiveness Conflict Risk

'd3.js' names a distinct niche with minimal overlap risk against general charting skills; it is mostly distinct with only minor overlap with adjacent visualisation skills.

4 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-skills
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.