CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

integrate-file-viewer

MUST be used whenever integrating CogniteFileViewer into a Flows app to preview CDF files (PDFs, images, text). Do NOT manually wire up react-pdf or file resolution — this skill handles installation, Vite config, worker setup, and component usage. Triggers: file viewer, file preview, CogniteFileViewer, PDF viewer, view CDF files, document viewer, preview file.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-sequenced integration guide with copy-paste-ready commands, config, and JSX plus a strong troubleshooting table. The main refinements would be adding an explicit verification step and moving the exhaustive props reference into a separate reference file.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no filler explaining PDFs or libraries — and content like the pitfalls table and height warning earns its tokens. However, the ~65-line inline "Full props reference" and parts of Tips & tricks could be trimmed or offloaded. Not 5 because of those minor over-explanation instances; not 3 because there is no clearly unnecessary explanation.

4 / 5

Actionability

Fully executable throughout: package-manager-specific install commands (pnpm/npm/yarn), a concrete Vite `optimizeDeps.exclude` config block, copy-paste JSX for all three source types, and a Common pitfalls table mapping each error to cause and fix. Covers the common cases the way the anchor's copy-paste-ready example does.

5 / 5

Workflow Clarity

"Complete these steps in order. Read each file before modifying it" precedes five clearly sequenced steps, and the pitfalls table doubles as error-recovery guidance. Not 5 because there is no explicit validation checkpoint (e.g., run the dev server and confirm the worker loads); not 3 because the sequence is complete and well-defined with implicit checkpoints.

4 / 5

Progressive Disclosure

Well-sectioned with headers, and the `code/` bundle is referenced exactly one level deep with all nine files explicitly listed. Not 5 because the full annotated props reference is inlined in SKILL.md where a separate reference file would fit the ideal overview-plus-references shape; not 3 because navigation is easy and references are clearly signaled. (No `code/`, `references/`, `scripts/`, or `assets/` directories are present in the workspace to verify the file listing against.)

4 / 5

Total

17

/

20

Passed

Description

83%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 strong description that explicitly states both what the skill does and when to use it, with a dedicated trigger list anchored on a specific component and platform. The main improvement space is broadening trigger synonyms (file extensions, image-related terms) and slightly expanding the action list.

DimensionReasoningScore

Specificity

Quotes like "this skill handles installation, Vite config, worker setup, and component usage" list several specific concrete actions in third person, with only minor gaps in coverage (e.g., annotation overlay support is not mentioned). Not 5 because the action list, while specific, stops short of comprehensively covering what the skill does; not 3 because far more than 1-2 concrete actions are named.

4 / 5

Completeness

It explicitly answers both questions: "MUST be used whenever integrating CogniteFileViewer into a Flows app to preview CDF files" gives a concrete 'when' (reinforced by a Triggers list), and "handles installation, Vite config, worker setup, and component usage" gives the 'what'. Matches the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

The explicit trigger list "file viewer, file preview, CogniteFileViewer, PDF viewer, view CDF files, document viewer, preview file" covers good natural phrases plus the component name, but misses common variations like ".pdf" extensions or image-viewer synonyms. Not 5 for those gaps; not 3 because coverage clearly goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

"CogniteFileViewer", "CDF files", and "Flows app" establish a clear niche with minimal conflict risk, but fairly generic trigger phrases like "file preview" and "document viewer" carry minor overlap risk with generic file-viewing skills. Not 5 because of that overlap; not 3 because the niche is far more specific than 'somewhat specific'.

4 / 5

Total

17

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

cognitedata/builder-skills

Path

skills/integrate-file-viewer/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.