CtrlK
BlogDocsLog inGet started
Tessl Logo

data-visualization

Route web data visualization work. Use when the user needs chart choice, visual critique, dashboards, maps or geospatial views, Gantt timelines, UML/software diagrams, scrollytelling, reports or exports, testing, accessibility, browser implementation, or concept-first visual design.

64

Quality

76%

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 ./plugins/build-web-data-visualization/skills/data-visualization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, dense router skill with a clear sequenced workflow, strong checklists, and sound progressive disclosure. Its weaknesses are moderate redundancy (the anti-atmosphere and mobile guidance repeated across sections) and the absence of inline worked examples that would make the routing heuristics directly actionable.

Suggestions

De-duplicate the anti-atmosphere enumeration: state it once (e.g., in Quality Gates) and reference it from the Overview to remove the repeated 'broad brush strokes, wispy ribbons, bokeh/orbs' list.

Add one or two inline worked routing examples (sample prompt -> job classification -> chosen route) so the heuristics are copy-paste-ready rather than purely descriptive.

Consolidate the mobile guidance that currently recurs across Overview, Router Workflow, Quality Gates, and Response Contract into a single canonical statement with cross-references.

DimensionReasoningScore

Conciseness

The body is dense and avoids explaining known concepts, but the anti-atmosphere list ('broad brush strokes, wispy ribbons, bokeh/orbs, cinematic wallpaper') is repeated in both Overview and Quality Gates, and mobile guidance recurs across four sections, so it could be tightened rather than earning 'every token earns its place.'

2 / 3

Actionability

Guidance is concrete and specific (a 9-step workflow, a routing matrix, element checklists, exact file references), but steps are classification heuristics ('Classify the analytical job', 'Define the reading path') with no inline worked examples or copy-paste-ready artifacts, falling short of 'fully executable ... specific examples; copy-paste ready.'

2 / 3

Workflow Clarity

The Router Workflow is a clearly sequenced 9-step process, Quality Gates and the Response Contract function as explicit checklists, and there are explicit checkpoints ('pause for approval', 'QA checks'), satisfying clear sequence with validation steps and checklists.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview with well-organized sections and a dedicated References section; the three bundled './references/*.md' files are real and one-level-deep with inline 'read X' signaling, and content is appropriately split between the overview and reference files.

3 / 3

Total

10

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, trigger-rich description that clearly answers what the skill does and when to use it with an explicit 'Use when' clause. Its main weakness is that it leans on one routing action plus a broad domain list, and several triggers are broad enough to overlap with sibling skills.

Suggestions

Lead with a second concrete action verb beyond 'Route' (e.g., 'Classify, route, and brief specialist visualization skills') to lift specificity toward the score-3 anchor.

Scope the broadest triggers ('testing', 'accessibility', 'browser implementation') to a visualization context (e.g., 'visualization testing', 'chart accessibility') to reduce conflict with adjacent skills.

Consider grouping the trigger list into a few labeled clusters so the breadth reads as structured coverage rather than a flat enumeration.

DimensionReasoningScore

Specificity

It names the domain ('web data visualization') and one concrete action ('Route ... work'), but the long tail ('chart choice, visual critique, dashboards, ...') is a trigger list, not a set of distinct concrete actions, so it does not reach the score-3 bar of 'lists multiple specific concrete actions.'

2 / 3

Completeness

It states what ('Route web data visualization work.') and an explicit, comprehensive 'Use when the user needs ...' trigger clause, clearly answering both what and when.

3 / 3

Trigger Term Quality

Natural user-facing terms dominate the 'Use when' clause ('chart choice', 'dashboards', 'maps or geospatial views', 'Gantt timelines', 'UML/software diagrams', 'reports or exports', 'testing', 'accessibility'), giving broad coverage of phrases a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The niche ('web data visualization') is clear, but broad triggers like 'testing', 'accessibility', 'browser implementation', and 'reports or exports' overlap with adjacent non-visualization skills and with the specialist skills it routes to, so it is not 'unlikely to conflict.'

2 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.