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.
76
95%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 a well-crafted skill description that clearly identifies a specific integration task with explicit trigger guidance. It names the exact technology components involved (useGraphViewer, CDF, Flows app) and provides a clear 'Use when' clause with multiple trigger scenarios. The only minor weakness is that the 'what' portion could enumerate more specific actions beyond 'copying the local code bundle'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a specific domain (CDF graph viewer integration) and mentions some actions like 'copying the local code bundle' and 'embedding a graph visualization', but doesn't list multiple concrete actions comprehensively—it's more about one integration task. | 2 / 3 |
Completeness | Clearly answers both 'what' (integrate the reusable CDF graph viewer by copying the local code bundle) and 'when' (explicit 'Use when' clause with three trigger scenarios: embedding graph visualization, adding knowledge graph, showing CDF data model relationships). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'graph viewer', 'useGraphViewer', 'Flows app', 'graph visualization', 'knowledge graph', 'CDF data model', 'relationships and instances'. These cover multiple natural ways a user might describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: CDF graph viewer (useGraphViewer) in a Flows app. The combination of specific technology names (CDF, useGraphViewer, Flows app) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that is concise, actionable, and well-structured. It provides a clear integration workflow with validation checkpoints, a complete executable example, and appropriate progressive disclosure to advanced reference materials. The verification checklist is a strong addition that catches common failure modes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows React, TypeScript, and general development concepts. Every section serves a clear purpose — no unnecessary explanations of what CDF is, how React works, or what graph visualization means. The dependency table is compact and informative. | 3 / 3 |
Actionability | Provides a fully executable minimal example with real code, concrete install commands, specific file copy paths, and a clear dependency table with versions. The guidance is copy-paste ready and leaves no ambiguity about what to do. | 3 / 3 |
Workflow Clarity | The integration workflow is clearly numbered with 6 sequential steps, includes a validation step (step 6: typecheck and build), and ends with a comprehensive verification checklist. The checklist acts as a feedback loop to catch common integration errors before considering the task complete. | 3 / 3 |
Progressive Disclosure | The SKILL.md provides a concise overview with a minimal example, then clearly signals one-level-deep references to `code/README.md` for advanced configuration and the source files for implementation details. Content is appropriately split between the overview and referenced materials. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- cognitedata/builder-skills
- Commit
d6af887
- 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.