Creating interactive data visualisations using d3.js. This skill should be used when creating custom charts, graphs, network diagrams, geographic visualisations, or any complex SVG-based data visualisation that requires fine-grained control over visual elements, transitions, or interactions. Use this for bespoke visualisations beyond standard charting libraries, whether in React, Vue, Svelte, vanilla JavaScript, or any other environment.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/agent-d3js-skill/SKILL.mdQuality
Discovery
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.
This is a strong skill description that excels across all dimensions. It clearly specifies the technology (d3.js), lists concrete visualization types, explicitly states when to use it with natural trigger terms, and distinguishes itself from standard charting libraries. The description uses proper third-person voice and provides comprehensive guidance for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'custom charts, graphs, network diagrams, geographic visualisations, complex SVG-based data visualisation' with additional specifics about 'fine-grained control over visual elements, transitions, or interactions'. | 3 / 3 |
Completeness | Clearly answers both what ('Creating interactive data visualisations using d3.js') and when ('should be used when creating custom charts, graphs...' and 'Use this for bespoke visualisations beyond standard charting libraries'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'd3.js', 'charts', 'graphs', 'network diagrams', 'geographic visualisations', 'SVG', 'data visualisation', plus framework mentions (React, Vue, Svelte, vanilla JavaScript) that users might reference. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - specifically targets d3.js and 'bespoke visualisations beyond standard charting libraries', which differentiates it from generic charting skills or other visualization libraries. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a table of contents rather than actionable guidance. While it appropriately delegates detailed content to sub-skills, the main file lacks any executable examples, a complete workflow explanation, or quick-start content that would make it immediately useful. The 'Core workflow' section is empty, which is a significant gap.
Suggestions
Add a minimal executable quick-start example showing a basic D3 visualization (e.g., a simple bar chart) directly in the main skill file
Complete the 'Core workflow' section with a clear numbered sequence explaining how the sub-skills connect (e.g., '1. Set up → 2. Choose pattern → 3. Structure code → 4. Add chart type → 5. Add interactions')
Organize the 23 sub-skills into logical categories (Setup, Chart Types, Interactions, Scales, etc.) with brief descriptions of when to use each
Remove the explanatory text about what D3.js is and focus on project-specific conventions or patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section contains some unnecessary explanation about what D3.js is ('Data-Driven Documents') that Claude already knows. The 'When to use' section is helpful but could be more concise. | 2 / 3 |
Actionability | The skill body contains no executable code, no concrete examples, and no specific commands. It only provides a list of links to sub-skills without any actionable guidance in the main file itself. | 1 / 3 |
Workflow Clarity | The 'Core workflow' section header exists but has no content beneath it. The numbered sub-skills suggest a sequence but there's no explanation of how they connect or when to use which modules. | 1 / 3 |
Progressive Disclosure | Good use of sub-skills for detailed content, but the main file lacks a quick-start example or any substantive overview content. The sub-skill list is overwhelming (23 items) without clear categorization or guidance on navigation. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
332e58b
Table of Contents
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.