CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-d3js-skill

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

59

Quality

69%

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

73%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 content is highly actionable with a clear workflow and well-organized sections, but it is verbose through heavy duplication of reference-file content inline and has minor asset-reference inaccuracies.

Suggestions

Move the full 'Common visualisation patterns' and 'Scales reference' sections into the existing reference files, keeping only a concise example plus a link in the body.

Fix the asset citations in the Resources section to match the real filenames ('chart-template.jsx', 'interactive-template.jsx').

Trim the Overview paragraph so it no longer explains what D3.js is, and remove the single-item 'Consider alternatives' bullet or expand it into a useful decision list.

DimensionReasoningScore

Conciseness

Mostly efficient code, but the body inlines full implementations of every chart type and a dedicated scales reference that largely duplicate the contents of d3-patterns.md and scale-reference.md, and the Overview mildly over-explains what D3 is.

3 / 5

Actionability

Extensive executable JavaScript covering common cases, but several snippets (pie, scatter, force-directed) reference undefined context variables like `g`, `width`, and `height`, leaving minor gaps from fully copy-paste-ready.

4 / 5

Workflow Clarity

A clear four-step core workflow (setup, choose pattern, structure code, responsive sizing) with a data-prep validation step and a troubleshooting section; minor validation gaps only, and the skill is non-destructive so no cap applies.

4 / 5

Progressive Disclosure

References and asset templates are signaled in a Resources section, but large blocks of pattern and scale content that belong in the reference files are inlined in the body, and cited asset filenames ('chart-template.js', 'interactive-template.js') do not match the actual '.jsx' bundle files.

3 / 5

Total

14

/

20

Passed

Description

65%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 is specific and clearly distinct, but it lacks an explicit 'when to use' trigger clause and only names one broad capability, capping completeness and specificity.

Suggestions

Add a 'Use when...' clause naming concrete trigger phrases (e.g., custom charts, force-directed graphs, D3 visualisations, .d3.js).

List 2-3 concrete capabilities (e.g., build custom charts, add interactive zoom/brush, render network/geographic visualisations) instead of a single 'creating visualisations' action.

Include common synonyms like 'charts' and 'graphs' alongside 'data visualisations' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the domain (d3.js) and one concrete action ('creating sophisticated, interactive data visualisations'), but offers only a single broad action type rather than a comprehensive list of specific capabilities.

3 / 5

Completeness

It states a clear 'what' but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes good natural keywords users would say ('d3.js', 'interactive data visualisations'), though it omits common synonyms like 'charts' and explicit file/extension terms.

4 / 5

Distinctiveness Conflict Risk

D3.js is a clear, specific niche with distinct triggers, so the description is unlikely to fire for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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