CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reveal-3d

Integrates the @cognite/reveal-widget npm package into Flows apps for an interactive Cognite Reveal 3D Scene/CAD/point cloud/360-image viewer. Use when adding 3D viewer, 3D visualization, Reveal, CAD model, Point cloud model, 360 image collection, Scenes, RevealWidget, RevealWidgetController, DM 3D mapping, asset 3D model, model browser, HTML overlay, 3D marker, 3D label, notification or badge on a 3D position, or Cognite 3D content to a Flows application.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, well-structured integration skill: ordered workflow with explicit validation and a thorough verification checklist, expert-level density with no concept padding, and clean progressive disclosure to three well-signaled reference files. The two deductions are the non-compiling useCoreDm reference in the minimal example and minor verbosity from inline version pins and repeated rules across sections.

Suggestions

Make the Minimal Example compile as written: pass useCoreDm (and its determination) as a prop or define it in the component, e.g. viewerOptions={{ sdk, useCoreDm: props.useCoreDm }}, so the snippet is copy-paste ready.

Consolidate the time-sensitive version pins into a single place (the Dependencies section framed with an old-patterns note for the stale 0.3.x/4.35.3 range) and drop the duplicated pin/disposal statements between the workflow steps, Critical Rules, and checklist.

Trim tangential background such as the legacy --classic / useDune() scaffold parenthetical in Prerequisites, or move it to a reference file.

DimensionReasoningScore

Conciseness

The body is dense and expert-level with no basic-concept padding, but it is not fully lean: exact version pins ("^1.48535.0", "4.36.0", "10.17.0") are time-sensitive and sit inline in the Dependencies table and prose rather than a deprecated/old-patterns section, the reveal pin and disposal rules are stated three times (workflow step, Critical Rules, checklist), and the legacy "--classic" scaffolds parenthetical is tangential. Efficient overall with minor trims possible — the score-4 anchor, not the every-token-earns-its-place of score 5.

4 / 5

Actionability

Guidance is concrete and near copy-paste ready: a complete typed controller class and RevealWidget mount, an exact install command ("pnpm add @cognite/reveal-widget @cognite/reveal@4.36.0..."), and specific inspect/dedupe/CSP actions. However, the minimal example's viewerOptions={{ sdk, useCoreDm }} references useCoreDm, which is not in scope in the snippet (neither prop nor variable), so the example fails typecheck as written — a minor gap that keeps it off the fully-executable score-5 anchor.

4 / 5

Workflow Clarity

The Integration Workflow gives 10 ordered, concrete steps ending in an explicit validation gate ("Run typecheck and build (tsc --noEmit, pnpm build, etc.) and fix any dependency/peer-version issues"), reinforced by a 16-item Verification Checklist and troubleshooting references for error recovery. This is the clear-sequence-with-explicit-validation-and-checklist pattern of the score-5 anchor; this is an integration task, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The body is a true overview (workflow, minimal example, critical rules) with bulk detail correctly split into three real, one-level-deep reference files (implementation.md, vite-config.md, csp-and-fixes.md — all verified present, with the html-overlays anchor matching an actual heading and no nested second-level references). Each pointer clearly signals its contents (e.g. "For CSP/manifest.json allowances, the useCoreDm/StrictMode gotchas, the point-cloud app-side fix, and 360-collection troubleshooting, read csp-and-fixes.md"), matching the well-signaled one-level-deep score-5 anchor.

5 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: third-person, names a specific package and platform, states a multi-capability what, and follows an explicit 'Use when...' clause with ~17 natural trigger terms including synonyms and component names. The only weakness is that a handful of generic 3D terms create slight overlap risk with non-Cognite 3D or visualization skills.

DimensionReasoningScore

Specificity

"Integrates the @cognite/reveal-widget npm package into Flows apps for an interactive Cognite Reveal 3D Scene/CAD/point cloud/360-image viewer" names a concrete action and a specific package, and comprehensively enumerates the capability surface (Scene, CAD, point cloud, 360-image viewing). It matches the comprehensive-coverage anchor rather than the score-4 anchor, which reserves minor gaps the what-clause here does not have.

5 / 5

Completeness

It explicitly answers both questions: what ("Integrates the @cognite/reveal-widget npm package... viewer") and when ("Use when adding... to a Flows application") with a long list of concrete trigger phrases. This structurally mirrors the rubric's score-5 example; the score-4 anchor's weaker/less-explicit 'when' does not apply.

5 / 5

Trigger Term Quality

The when-clause packs natural user phrasings and synonyms — "3D viewer", "3D visualization", "Reveal", "CAD model", "Point cloud model", "360 image collection", "model browser", "HTML overlay", "3D marker", "3D label", "notification or badge on a 3D position" — plus the component names users paste from errors (RevealWidget, RevealWidgetController). This is comprehensive natural-term coverage, not the few-terms-missing level of score 4.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (Cognite Reveal 3D in Flows apps via a named npm package), but several triggers are generic on their own — "3D viewer", "3D visualization", "Scenes" — and could overlap with a generic 3D or dataviz skill even with the trailing "to a Flows application" qualifier. That is minor overlap risk with closely related skills (score 4), not the minimal-conflict profile of score 5.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

cognitedata/builder-skills

Path

skills/reveal-3d/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.