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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The body is highly actionable with concrete code and a clear step sequence, but it is held back by missing validation checkpoints in the workflow and a lack of genuine progressive disclosure — the cited 'code/' bundle files are absent and large reference material is inlined rather than split out.

Suggestions

Add explicit verification checkpoints after the fragile steps — e.g., after Step 4 run the dev server and confirm the pdfjs worker resolves, and after Step 3 confirm `pdfjs-dist` is hoisted for pnpm — to lift workflow clarity.

Either provide the missing `code/` bundle files referenced in Step 2 (the nine `code/*.ts(x)` files) or remove/correct the references, so the skill's external structure is real.

Move the 'Full props reference' and 'Tips & tricks' sections into a separate reference file (e.g., `references/props.md`) referenced one level deep, to reduce inline length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining known concepts, but the inline 'Full props reference' and 'Tips & tricks' sections make it a dense ~280-line single file that could be tightened; not level 3 because it is not lean, and not level 1 because it is not padded with concepts Claude already knows.	2 / 3
Actionability	Fully executable guidance throughout — per-package-manager install commands, exact Vite config, copy-paste imports and usage, a typed full-props example, and a pitfalls table with concrete fixes — matching the 'fully executable, copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1–5 with 'Complete these steps in order') but there are no explicit validation checkpoints for the fragile config/worker setup; per the rubric, missing verification steps in build/config manipulation caps workflow clarity at 2 rather than 3.	2 / 3
Progressive Disclosure	The single file is reasonably sectioned, but the 'Full props reference' and tips are inline content that could be split out, and the referenced 'code/' bundle (Step 2 lists nine files) does not exist on disk; no real one-level-deep references are present, so it is not the well-split level 3 but not a disorganized wall of text either.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 strong: third-person voice, concrete sub-tasks, an explicit trigger list, and a tightly scoped product niche that answers both what and when. No meaningful weaknesses to address.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'installation, Vite config, worker setup, and component usage' plus previewing 'CDF files (PDFs, images, text)' — matching the 'multiple specific concrete actions' anchor; not level 2 because the enumerated sub-tasks are comprehensive rather than partial.	3 / 3
Completeness	Clearly answers what the skill does and when to use it — 'MUST be used whenever integrating CogniteFileViewer... this skill handles installation, Vite config, worker setup, and component usage' plus explicit Triggers — hitting the score-3 'both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	An explicit 'Triggers:' list gives natural user phrasings ('file viewer, file preview, CogniteFileViewer, PDF viewer, view CDF files, document viewer, preview file') with good coverage, matching the score-3 anchor rather than the partial-keyword level 2.	3 / 3
Distinctiveness Conflict Risk	Tied to a named library and environment ('CogniteFileViewer into a Flows app', 'CDF files') with distinct triggers, giving a clear niche unlikely to conflict with other skills; not level 2 because the scope is tightly product-specific rather than broadly overlapping.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: cognitedata/builder-skills
Commit: ab7b5f8

Reviewed: 1 day 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.