dataviz

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

Quality

86%

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

Quality

Content

100%

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-organized overview that pairs concrete executable guidance with a sequenced, validated workflow and one-level-deep references to real bundle files, hitting the top anchor on every dimension.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what a chart or palette is, and every line (workflow steps, mark rules, the validation command) earns its place.	3 / 3
Actionability	It gives a fully executable command ("node <skill-base-directory>/scripts/validate_palette.js '#1d4ed8,#b45309,#166534' --mode light") plus concrete FAIL/WARN handling rules, which is copy-paste ready.	3 / 3
Workflow Clarity	The numbered workflow is clearly sequenced and includes validation checkpoints — palette validation with FAIL/WARN outcomes and a final anti-patterns check before finalizing — forming an explicit feedback loop.	3 / 3
Progressive Disclosure	It is a concise overview with one-level-deep, clearly signaled references (choosing-a-form.md, palette.md, anti-patterns.md, validate_palette.js), all of which exist in the bundle, with no nested indirection.	3 / 3
	Total	12 / 12 Passed

Description

72%

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 concise and uses strong natural trigger terms within a clear, distinctive niche, but it lacks an explicit "when to use" clause in the description field itself and the stated action is somewhat abstract.

Suggestions

Add an explicit "Use when…" trigger clause to the description (e.g., "Use when creating or revising charts, dashboards, or maps") so completeness can reach 3.

Replace the abstract "Design guidance" phrasing with a few concrete actions (e.g., "Choose chart forms, pick and validate color palettes, and avoid common visualization anti-patterns") to lift specificity.

Dimension	Reasoning	Score
Specificity	It names the domain ("charts, graphs, dashboards, maps, and data visualizations") and one concrete capability ("a local palette validator"), but the action is a single abstract phrase ("Design guidance") rather than a list of multiple specific actions, so it stops short of a 3.	2 / 3
Completeness	It clearly answers what the skill does, but the description itself has no explicit "Use when…" trigger clause (that guidance lives in the separate when_to_use field), so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	"charts, graphs, dashboards, maps, and data visualizations" are exactly the natural terms a user would say when requesting this skill, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The dataviz niche and concrete trigger terms are distinct from general-purpose skills and unlikely to fire for unrelated work.	3 / 3
	Total	10 / 12 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: 8878264

Reviewed: 5 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.