dataviz

Design guidance for charts, graphs, dashboards, maps, and data visualizations, including a local palette validator.

Quality

73%

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 ./packages/core/src/skills/bundled/dataviz/SKILL.md

Quality

Content

86%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 tight, well-structured overview with an executable palette-validation command, a clear sequenced workflow with a final checkpoint, and clean one-level-deep references to real bundle files.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is lean: a five-step workflow, one executable command, and tight mark-rule bullets with no padding or explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	A copy-paste-ready command ("node <skill-base-directory>/scripts/validate_palette.js '#1d4ed8,#b45309,#166534' --mode light") plus concrete FAIL/WARN handling and specific reference paths give mostly executable guidance, though the workflow steps are instructional directives rather than executable code.	4 / 5
Workflow Clarity	A clearly numbered five-step sequence ends with a "check anti-patterns before finalizing" checkpoint and a palette FAIL/WARN validation gate, but there is no explicit validate→fix→retry feedback loop spelled out in the main workflow.	4 / 5
Progressive Disclosure	The body is a concise overview that signals one-level-deep references (choosing-a-form.md, palette.md, anti-patterns.md) and the validate_palette.js script, all of which exist as real bundle files; content is appropriately split and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

61%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 scopes a data-visualization design niche with good natural trigger terms, but the evaluated description field lacks an embedded "when" clause and relies on generic "design guidance" phrasing rather than a comprehensive list of concrete actions.

Suggestions

Fold a concise "Use when..." trigger clause into the description field itself (or merge when_to_use content) so the evaluated description explicitly answers both what and when.

Replace the generic "Design guidance for" phrasing with a few concrete actions (e.g., "Choose chart forms, pick accessible palettes, and validate color contrast") to lift specificity.

Add one or two library/tool synonyms (D3, Plotly, matplotlib) into the description to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Design guidance for charts, graphs, dashboards, maps, and data visualizations, including a local palette validator" names the domain broadly and one concrete capability (palette validator), but the action "design guidance" is generic and not a comprehensive list of concrete actions.	3 / 5
Completeness	The description field gives a clear "what" but contains no "Use when..." clause within it; per the judging guideline, a missing explicit trigger clause in the evaluated description caps completeness at 3 even though a sibling when_to_use field exists.	3 / 5
Trigger Term Quality	Natural user-facing terms ("charts, graphs, dashboards, maps, and data visualizations") are present and relevant, though the description field omits library/tool synonyms (D3, Plotly, matplotlib) that live only in when_to_use.	4 / 5
Distinctiveness Conflict Risk	The data-visualization niche plus the palette-validator hook is mostly distinct with minimal conflict risk, with only minor overlap against general design/styling skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: QwenLM/qwen-code
Path: packages/core/src/skills/bundled/dataviz/SKILL.md
Commit: 054eabb

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.