graph-viewer

Integrate the reusable CDF graph viewer (useGraphViewer) into a Flows app by copying the local code bundle. Use when embedding a graph visualization, adding a knowledge graph, or showing CDF data model relationships and instances.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

The body is concise, actionable, and has a well-sequenced workflow with validation checkpoints. The main gap is progressive disclosure: advanced content is deferred to a code/ bundle that is not present in this review set, so the references cannot be verified.

Suggestions

Ensure the referenced bundle (skills/graph-viewer/code/ and code/README.md) ships alongside the skill so the 'Advanced Reference' pointers resolve to real, one-level-deep files.

Consider adding a brief one-line summary of what code/README.md contains so readers know whether to open it before navigating into the bundle.

Dimension	Reasoning	Score
Conciseness	Lean throughout: short prerequisite list, numbered workflow, a single minimal code example, a compact dependency table, and a focused cost section — no padding or explanations of concepts Claude already knows.	3 / 3
Actionability	Provides a copy-paste-ready minimal example, concrete import path, an executable install command with versioned packages, and specific config knobs (whitelistedRelationProps, initialConnectionLimit, maxNodes, coreReverseQueries) with their tuple shape.	3 / 3
Workflow Clarity	Six clearly sequenced steps ending in a typecheck/build validation step, plus an explicit Verification Checklist with feedback items ('tsc --noEmit and the app's build both pass'), giving clear checkpoints for a fragile copy-integration operation.	3 / 3
Progressive Disclosure	The body references 'code/README.md' and 'code/' for advanced details, which is well-signaled, but the referenced bundle directory (skills/graph-viewer/code/) is not present in the review bundle, so the referenced paths cannot be verified to exist one level deep.	2 / 3
	Total	11 / 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 concrete, well-scoped, and third person, with an explicit 'Use when' trigger clause and natural language a user would actually say. It cleanly satisfies the top anchor on all four dimensions.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Integrate the reusable CDF graph viewer (useGraphViewer)', 'copying the local code bundle', 'embedding a graph visualization, adding a knowledge graph, or showing CDF data model relationships and instances' — matching the top anchor.	3 / 3
Completeness	Explicitly answers both what (integrate the useGraphViewer code bundle into a Flows app) and when ('Use when embedding a graph visualization, adding a knowledge graph, or showing CDF data model relationships and instances'), satisfying the top anchor.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ('embedding a graph visualization', 'adding a knowledge graph', 'showing CDF data model relationships and instances'), giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Narrowly scoped to a CDF/Flows graph viewer with a specific hook and clear triggers, making it unlikely to fire for unrelated skills.	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: 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.