CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

connect-atlas-mcp

MUST be used when a Fusion Custom apps Start building or Build app prompt is in chat and Industrial / Atlas MCP must be connected. Triggers: ---Start Building---, Intent sketch from Fusion Custom apps, createdVia fusion.customApps.buildPrompt, "Industrial MCP for this project", or a Fusion MCP command such as claude mcp add-json cognite, cursor --add-mcp, or code --add-mcp. Do not use for docs MCP or dm-graph-traversal.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-structured instruction-only skill that respects the token budget and gives concrete, executable guidance for the happy path and the main failure modes. The remaining gaps are the unspecified per-tool config locations in the fallback and the absence of an OAuth-failure recovery step.

Suggestions

In the section 1 fallback, name the per-tool MCP config locations (e.g., the Claude config file, Cursor's mcp.json path) so the manual route is fully executable.

Add a brief recovery step in section 2 for OAuth failure (e.g., what to check or retry before falling back to manual config).

Include a verification command for the happy path (e.g., 'claude mcp list' or the tool's equivalent) so connection success can be checked programmatically, not just in the browser flow.

DimensionReasoningScore

Conciseness

Every line carries non-obvious information (the command-shape table, PowerShell 5.1 vs 7.3 quoting rules, 'Do not paste tokens. Do not scrape the CLI keychain.') with no padding or explanations of concepts Claude already knows.

5 / 5

Actionability

Guidance is mostly executable: run the command verbatim, exact Windows quoting transformation, and a fallback that names the server 'cognite'. Minor gap: the manual-config fallback omits per-tool MCP config file locations, so it is not fully copy-paste ready in the failure case.

4 / 5

Workflow Clarity

A clear three-step sequence with error-recovery paths (truncated-prompt detection, command-failure fallback) and a success checkpoint ('Success is connected in the tool, not a file on disk'). Not destructive or batch, so no cap applies; OAuth-failure recovery is left unspecified.

4 / 5

Progressive Disclosure

A single-purpose skill (~55 lines) with no need for external references: well-organized numbered sections, appropriately self-contained content, and one clearly signaled cross-skill pointer ('Graph reads in app code: dm-graph-traversal').

5 / 5

Total

18

/

20

Passed

Description

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

A strong, highly targeted trigger description with excellent literal trigger phrases and explicit exclusion boundaries. Its only weakness is that the skill's concrete actions are implied by condition phrasing rather than stated as capabilities.

DimensionReasoningScore

Specificity

The description names the domain (Fusion Custom apps, Industrial/Atlas MCP) and includes concrete command triggers ('claude mcp add-json cognite', 'cursor --add-mcp', 'code --add-mcp'), but it does not enumerate the skill's own actions (run command, finish OAuth, explore models), leaving minor gaps in coverage.

4 / 5

Completeness

The 'when' is explicit with concrete trigger phrases, but the 'what' is phrased as a condition ('Industrial / Atlas MCP must be connected') rather than an explicit capability statement, falling just short of the both-fully-explicit anchor.

4 / 5

Trigger Term Quality

It lists the literal strings that appear in the triggering chat ('---Start Building---', 'createdVia fusion.customApps.buildPrompt', 'Industrial MCP for this project') plus all three tool command shapes, giving comprehensive natural-trigger coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

It occupies a narrow Fusion-specific niche and includes explicit negative boundaries ('Do not use for docs MCP or dm-graph-traversal'), giving minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

cognitedata/builder-skills

Path

skills/connect-atlas-mcp/SKILL.md

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.