CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

canvas2d-data-visualization

Render data visualizations with Canvas2D. Use when the visualization needs high mark counts, fast redraws, immediate-mode rendering, custom hit testing, or a hybrid Canvas plus SVG or HTML architecture.

Quality

78%

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/canvas2d-data-visualization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, information-dense design guide: concrete API-level guidance, a clear decision framework, and appropriate offloading of detail to real reference files. The main improvement levers are consolidating topic repetition (mobile, hit testing, DPR), adding one minimal executable snippet, and labeling each reference with its purpose.

Suggestions

Replace the bullet description of the DPR/backing-store setup with a short executable snippet (style.width/height, canvas.width/height = cssSize * pixelRatio, setTransform) — it is already fully specified, just not copy-paste ready.

Consolidate the repeated mobile/pinch-zoom and hit-testing guidance, which currently spans Overview, Core Practices, Performance Defaults, and Output Expectations.

Add a one-line purpose note next to each reference path (e.g., 'read rendering-architecture.md when layering canvases or splitting Canvas from SVG/HTML') and clarify that the shared `../../references/foundations/` paths live outside this bundle.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — exact API calls like `ctx.setTransform(pixelRatio, 0, 0, pixelRatio, 0, 0)` and a backing-store memory formula appear with zero concept-explanation padding. It falls short of score 5 because several topics repeat across sections: mobile/pinch-zoom concerns appear in the Overview, Core Practices items 1 and 8, Performance Defaults, and Output Expectations; hit testing and DPR handling likewise recur.

4 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: exact attributes (`canvas.width = cssSize * pixelRatio`), exact context options (`getContext("2d", { willReadFrequently: true })`), pointer-event mechanics (`setPointerCapture()`, `lostpointercapture`), and a computable memory budget formula. Score 5 is withheld only because no complete executable snippet exists — e.g., the four-line DPR setup would be copy-paste ready but is described as bullets instead of code.

4 / 5

Workflow Clarity

The decision workflow is explicit and well-sequenced ('Choose Canvas2D When' / prefer SVG-when / move to WebGL-when), and 'Output Expectations' acts as a response checklist including validation-ish checks (compute memory as `width * height * pixelRatio^2 * 4 * layerCount * instanceCount`). Score 5 is withheld because there is no implementation sequence with checkpoints tying the practices into a build order; Core Practices is a numbered practice catalog rather than an ordered process.

4 / 5

Progressive Disclosure

SKILL.md is a clean overview with details correctly split into four real one-level-deep local files (`./references/rendering-architecture.md`, `high-density-interaction.md`, `performance-playbook.md`, `sparklines-and-microcharts.md`), all present in the bundle, plus clearly labeled shared-theory references. It falls short of score 5 only because the References section lists bare paths with no per-file indication of when to read which, and the `../../references/foundations/*.md` shared paths are not resolvable within this bundle.

4 / 5

Total

16

/

20

Passed

Description

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

A well-formed description with an explicit third-person action statement and a concrete, well-scoped 'Use when' trigger list. Its main weaknesses are a single-action what-clause and trigger vocabulary that is more developer-technical than the natural phrases users would say when they need this skill.

Suggestions

Enumerate the concrete workloads in the what-clause (e.g., 'Render dense scatterplots, heatmaps, streaming traces, and sparkline walls with Canvas2D') to raise specificity.

Add natural user phrasings to the triggers, such as 'million-point scatterplot', 'too many SVG nodes', or 'canvas is too slow', alongside the current technical terms.

Clarify the boundary with WebGL in the description (e.g., 'before reaching for WebGL') to reduce overlap with a WebGL rendering skill.

DimensionReasoningScore

Specificity

The what-clause names the domain and one concrete action — "Render data visualizations with Canvas2D" — but no further concrete actions follow; the remaining clauses are all triggers. This matches "names domain and 1-2 concrete actions, but not comprehensive" (score 3) rather than score 4, which would require several listed actions like rendering heatmaps, sparkline walls, or draggable workspaces.

3 / 5

Completeness

Both parts are explicit: what ("Render data visualizations with Canvas2D") and when ("Use when the visualization needs high mark counts, fast redraws, immediate-mode rendering, custom hit testing, or a hybrid Canvas plus SVG or HTML architecture") with concrete trigger conditions. This matches the score-5 anchor exactly; score 4 would require the when-clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Triggers like "high mark counts", "fast redraws", and "custom hit testing" are relevant but lean technical; "immediate-mode rendering" is jargon a user would rarely say. Natural phrases users actually utter for this need ("million-point scatterplot", "dense heatmap", "sparklines in a table", "canvas is slow/too many SVG nodes") are missing, matching score 3 rather than 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

"Canvas2D", "immediate-mode rendering", and "custom hit testing" carve a clear niche separate from SVG and DOM skills. Minor overlap remains: "high mark counts" could also plausibly trigger a WebGL skill, and "hybrid Canvas plus SVG" overlaps general dataviz skills — matching score 4 ("mostly distinct; minor overlap risk") rather than 5's minimal-conflict bar.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/build-web-data-visualization/skills/canvas2d-data-visualization/SKILL.md

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.