CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

integrate-fusion-agent

MUST be used when adding AI, Atlas, an agent, a chat UI, or LLM features to a Flows/Fusion app. Use the Atlas/EOS sidebar via @cognite/app-sdk — not useAtlasChat, vendored atlas-agent, or per-row chat completions. Triggers: atlas, EOS, PAIA, agent chat, chat UI, sendAgentMessage, sendAgentLayoutMode, registerAgentServer, connectToHostApp, useAtlasChat, LLM. In-app chat: integrate-atlas-chat only if the host sidebar cannot work.

Quality

91%

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.

An exemplary lean, executable integration guide — complete code, real error-handling checkpoints, and high-signal pitfall notes with no basic-concept padding. The weaknesses are a dangling 'use-topbar' reference in a bundle with no reference files and the absence of an explicit enforcement/verification step for the batch-completion cap.

Suggestions

Resolve the 'use-topbar' reference: either add the referenced file under references/ and link it as 'See [use-topbar.md](references/use-topbar.md)', or inline the one or two required Topbar configuration lines so Step 3 is self-contained.

Add an explicit validation checkpoint to the batch-LLM hard gate, e.g. 'Before finishing, count completion call sites in generated code and confirm <= 5 per user action and 50 hard ceiling' — this turns the cap table into a verify step rather than guidance only.

Consider moving the three full agent-server source files into a references/ code template (with the body keeping signatures and key lines), which would cut body tokens and resolve the skill's only structural gap.

DimensionReasoningScore

Conciseness

Dense imperative one-liners with zero padding ('Register on mount, unregister on unmount'); it explains only non-obvious SDK/React pitfalls like 'Comlink proxies are callable — setApi(proxy) ... stores a Promise' that Claude could not infer. Every code block earns its tokens.

5 / 5

Actionability

Fully executable end to end: 'pnpm add @cognite/app-sdk' with minimum version, a file layout, four complete copy-paste TypeScript files (hook, resources, actions, server wiring), and a runnable unit-test snippet covering the factories. Not 4 because there are no pseudocode gaps or missing key details.

5 / 5

Workflow Clarity

Steps 0–6 are clearly sequenced with real checkpoints: catch the outside-Fusion rejection, '.catch()' on register/unregister, and a final checklist. Not 5 because the batch-LLM hard gate states caps (5/50) and UX disclosure but no explicit validation step to verify the cap is enforced before shipping, so a feedback loop is missing for the batch case.

4 / 5

Progressive Disclosure

Step headers are well organized, but 'use-topbar' is referenced twice (Step 3 'see use-topbar' and the Checklist) as a bare inline code mention with no link, and no references/ or other bundle directory exists in this skill — the reference is dangling and unclearly signaled. This matches the 3 anchor (some structure, references present but not clearly signaled) rather than 4, where references would be mostly clear and resolvable.

3 / 5

Total

17

/

20

Passed

Description

95%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 tightly written trigger description: it states a precise what, an explicit and condition-gated when, comprehensive trigger synonyms, and clear separation from a conflicting alternative path. Only minor headroom on enumerating the skill's own capabilities versus routing instructions.

DimensionReasoningScore

Specificity

Names the concrete path ('Use the Atlas/EOS sidebar via @cognite/app-sdk') and enumerates several specific APIs (sendAgentMessage, sendAgentLayoutMode, registerAgentServer, connectToHostApp) with explicit anti-patterns. Falls just short of the 5 anchor because the actions are routing guidance rather than a comprehensive coverage of what the skill does.

4 / 5

Completeness

Explicitly answers both: what ('Use the Atlas/EOS sidebar via @cognite/app-sdk — not useAtlasChat, vendored atlas-agent, or per-row chat completions') and when ('MUST be used when adding AI, Atlas, an agent, a chat UI, or LLM features to a Flows/Fusion app'). Both are concrete and unambiguous.

5 / 5

Trigger Term Quality

'adding AI, Atlas, an agent, a chat UI, or LLM features' plus 'Triggers: atlas, EOS, PAIA, agent chat, chat UI, ... useAtlasChat, LLM' comprehensively covers natural phrasings, product synonyms, and API-level keywords a user or transcript would plausibly contain.

5 / 5

Distinctiveness Conflict Risk

Clear niche (Flows/Fusion apps, Atlas/EOS sidebar) with distinct trigger vocabulary, and it explicitly disambiguates against the sibling 'integrate-atlas-chat' skill ('only if the host sidebar cannot work'), minimizing wrong-skill triggering.

5 / 5

Total

19

/

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/integrate-fusion-agent/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.