threejs-data-visualization

Render WebGL-accelerated data visualizations with Three.js, raw WebGL, deck.gl, luma.gl, PixiJS, Sigma.js, Plotly WebGL traces, ECharts GL, CesiumJS, Babylon.js, or related GPU libraries. Use when the visualization needs true spatial structure, dense 2D or 3D GPU rendering, particle or flow animation, volumetric views, or interactive exploration that adds real analytical value.

Quality

85%

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

70%Weight 40%Scale 1-3

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 well-structured, well-disclosed decision guide with strong workflow sequencing and clean reference navigation. Its main gaps are the absence of any executable code examples and mild verbosity/overlap between the Overview, Choose/Avoid lists, and the when-3d reference.

Suggestions

Add at least one minimal, copy-paste-ready code scaffold (e.g., a Three.js BufferGeometry/instancing scene or a typed-array buffer setup) so the skill's actionability matches its API-level vocabulary.

Tighten the Overview to avoid restating the description's 'Use when' triggers, and de-duplicate the 'Choose WebGL When'/'Avoid WebGL When' lists against references/when-3d-is-justified.md.

Consider trimming or consolidating a few of the 15 Default Architecture steps, moving detail that is unlikely to be re-derived into the existing references.

Dimension	Reasoning	Score
Conciseness	The body is dense with actionable decision criteria and avoids explaining concepts Claude already knows, but the Overview restates the description and the 'Choose WebGL When'/'Avoid WebGL When' lists overlap with the when-3d-is-justified reference, so it could be tightened.	2 / 3
Actionability	Concrete decision rules and named APIs (BufferGeometry, instancing, typed arrays) provide solid guidance, but the skill ships zero executable code or scaffolding for a GPU-rendering topic where a minimal scene/buffer template would help, matching the 'some concrete guidance but incomplete' anchor.	2 / 3
Workflow Clarity	The 15-step Default Architecture is a clear sequenced process with validation checkpoints (the advanced-interactive-visualization-contract template, the scene-readiness QA reference) and an Output Expectations checklist, matching the anchor-3 'clear sequence with explicit validation steps' example.	3 / 3
Progressive Disclosure	A clear overview links to eight verified one-level-deep ./references files plus shared foundations and a template, with inline signals (mobile reference at line 14, contract template at step 13), matching the anchor-3 well-signaled one-level-deep pattern.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 specific, third-person, and answers both what and when with a concrete 'Use when' trigger and a comprehensive library list. It is well-distinguished from adjacent 2D/SVG visualization skills.

Dimension	Reasoning	Score
Specificity	Enumerates concrete rendering tools (Three.js, raw WebGL, deck.gl, luma.gl, PixiJS, Sigma.js, Plotly WebGL traces, ECharts GL, CesiumJS, Babylon.js) and concrete tasks (spatial structure, particle/flow animation, volumetric views), matching the 'lists multiple specific concrete actions' anchor rather than the partial anchor at 2.	3 / 3
Completeness	Explicitly states what ('Render WebGL-accelerated data visualizations with ...') and when via an explicit 'Use when the visualization needs true spatial structure...' clause, satisfying the anchor-3 requirement of both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Includes natural user-facing terms ('Three.js', 'WebGL', 'particles', 'flow animation', 'volumetric views', '3D') with good coverage users would actually say, matching anchor 3; not 2 because common variations are present rather than missing.	3 / 3
Distinctiveness Conflict Risk	A clear GPU/WebGL visualization niche with named libraries and distinct spatial/GPU triggers makes it unlikely to fire for sibling D3 or Canvas2D skills, matching the anchor-3 'clear niche with distinct triggers' example.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/build-web-data-visualization/skills/threejs-data-visualization/SKILL.md
Commit: 11c74d6

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