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

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Discovery

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.

This is an excellent skill description that clearly defines its scope, provides explicit trigger terms, and distinguishes itself from generic file-handling skills. It effectively communicates both what the skill does and when to use it, including helpful anti-guidance about what NOT to do manually. The description is concise yet comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: installation, Vite config, worker setup, and component usage for CogniteFileViewer integration. Also specifies the file types (PDFs, images, text) and the context (Flows app, CDF files).	3 / 3
Completeness	Clearly answers both 'what' (handles installation, Vite config, worker setup, component usage for CogniteFileViewer in Flows apps) and 'when' (whenever integrating CogniteFileViewer to preview CDF files, with explicit trigger terms listed). Also includes anti-guidance ('Do NOT manually wire up react-pdf').	3 / 3
Trigger Term Quality	Includes a comprehensive explicit list of natural trigger terms: 'file viewer', 'file preview', 'CogniteFileViewer', 'PDF viewer', 'view CDF files', 'document viewer', 'preview file'. These cover both domain-specific and general user language.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: CogniteFileViewer integration in Flows apps for CDF files. The domain-specific terms (CogniteFileViewer, CDF, Flows app) and the explicit anti-pattern guidance make it very unlikely to conflict with generic file or PDF skills.	3 / 3
	Total	12 / 12 Passed

Implementation

77%

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

This is a well-structured, highly actionable integration skill with a clear step-by-step workflow and excellent concrete code examples. Its main weakness is length — the full props reference, tips & tricks, and troubleshooting sections make it quite long and could benefit from being split into separate reference files. The workflow is well-sequenced with good attention to common failure modes.

Suggestions

Move the full props reference and tips & tricks sections into separate files (e.g., PROPS_REFERENCE.md, TIPS.md) and link to them from the main skill to reduce token footprint.

Trim the supported file types table — Claude doesn't need this enumeration since the component handles it internally; a one-liner noting 'supports PDF, images, text, and Office documents' would suffice.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and avoids explaining basic concepts, but the full props reference section and supported file types table are quite lengthy. The tips & tricks section, while useful, adds significant token weight — some of it could be trimmed or moved to a separate reference file.	2 / 3
Actionability	Every step includes concrete, executable commands and copy-paste-ready code examples. Package manager variants are specified, Vite config changes are shown as real code, and component usage includes multiple realistic TSX examples with all prop variations.	3 / 3
Workflow Clarity	The 5-step workflow is clearly sequenced with explicit ordering ('Complete these steps in order'), includes a prerequisite reading step before modifications, and addresses error scenarios in the common pitfalls table. The pnpm-specific validation note in Step 3 acts as a checkpoint for a known failure mode.	3 / 3
Progressive Disclosure	The skill references a `code/` directory for source files (good separation of library code from instructions), but the SKILL.md itself is monolithic — the full props reference, tips & tricks, and troubleshooting table could be split into separate files. No bundle files were provided to verify the `code/` directory references.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: cognitedata/builder-skills
Commit: d6af887

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.