Name: cognite
Rating: 62.4 (1 reviews)
Author: membranedev

cognite

Cognite integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cognite data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cognite/SKILL.md

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.

The body is highly actionable with executable commands and a sound connection-polling workflow, organized into clean sections; its main weaknesses are a marketing-fluff intro paragraph and a dangling 'Step 2' reference with no result-validation checkpoint.

Suggestions

Cut the marketing sentence in the intro ('helps asset-heavy industries extract value... improve efficiency and sustainability') to respect the token budget.

Fix the dangling 'skip to Step 2' reference by labeling the subsequent steps (e.g. '## 2. Search for actions').

Add a brief validation note for action results (e.g. check the `output` field and HTTP status for proxy requests) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete CLI commands, but the opening paragraph ('helps asset-heavy industries extract value from their data... improve efficiency and sustainability') is marketing fluff Claude does not need, and a few prose lines could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover every common flow — install, login (interactive and headless), connection ensure, polling, action list/run, proxy — plus a flag table, matching the anchor for specific examples covering common cases.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→handle-states→run sequence exists with a polling feedback loop (BUILDING→READY, re-poll after CLIENT_ACTION_REQUIRED), but the 'skip to Step 2' reference points to an unlabeled step and there is no validation of action results.	4 / 5
Progressive Disclosure	A single self-contained file is well-organized into clear sections with no nested references, appropriate for a CLI guide; the 23-line resource-type list is the one block that could plausibly live in a separate reference file.	4 / 5
	Total	17 / 20 Passed

Description

66%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.

The description cleanly pairs a 'what' with an explicit 'when' trigger and is highly distinct thanks to the Cognite product binding, but its action verbs are generic and it misses common product synonyms like 'CDF'.

Suggestions

Replace generic verbs with concrete actions, e.g. 'Query assets and time series, manage records, and automate workflows'.

Add the product synonyms users actually say — 'Cognite Data Fusion (CDF)' — to the trigger phrase.

Broaden the 'when' clause with additional trigger terms such as 'Cognite data', 'CDF', or 'industrial data'.

Dimension	Reasoning	Score
Specificity	Names the Cognite domain plus three action areas ('Manage data, records, and automate workflows'), but the verbs ('manage', 'automate') are generic rather than concrete like 'extract/fill/merge', matching the anchor that lists 1-2 actions without comprehensive coverage.	3 / 5
Completeness	Explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Cognite data'), but the 'what' is generic and offers fewer trigger phrases than the anchor-5 example.	4 / 5
Trigger Term Quality	Includes natural terms ('Cognite', 'Cognite data', 'interact with Cognite data') but omits the product's own common variations 'CDF' and 'Cognite Data Fusion' that the body itself emphasizes, leaving keyword coverage incomplete.	3 / 5
Distinctiveness Conflict Risk	Bound to a single named product (Cognite) with a product-specific trigger, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/cognite/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.