CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

integrate-atlas-chat

Exception path. Use integrate-fusion-agent for Atlas/chat/agent. Only when the user explicitly requires in-app useAtlasChat and connectToHostApp cannot provide the EOS sidebar (standalone app, always rejects). Triggers: useAtlasChat, in-app atlas chat, embedded chat, vendored atlas-agent. Not for generic "add a chat".

64

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 exceptionally token-efficient gating skill with concrete probe criteria and hard operational limits, well organized for its size. Its main gap is that the actual integration procedure — the reason the skill exists — is delegated to an external docs URL rather than inlined.

Suggestions

Inline the minimal useAtlasChat wiring (provider setup, mount point, a short code snippet) so the skill is executable without fetching the external docs URL, which may be unavailable or version-drifted.

Add a post-integration verification step, e.g. 'Confirm the chat renders in the app shell and host-connect attempts still reject, before considering the integration done.'

Localize the docs.cognite.com guide's key steps into a references/ file so the body can stay lean while keeping the procedure on-bundle.

DimensionReasoningScore

Conciseness

The 14-line body is lean with zero padding: every line is either an eligibility gate, a concrete probe ('@cognite/app-sdk + connectToHostApp / useHostApp resolving inside Fusion/EOS'), or a hard constraint ('5 per user action, ceiling 50, cache by space:externalId:lastUpdatedTime'). It assumes Claude's competence and explains nothing the model already knows.

5 / 5

Actionability

Concrete guidance exists for the eligibility probe and the rate-limit/cache rules, but the primary task — 'follow https://docs.cognite.com/... and wire useAtlasChat' — contains no executable steps or code, deferring entirely to an external URL and a sibling skill. This matches 'some concrete guidance but incomplete; missing key details' rather than the mostly-executable anchor 4.

3 / 5

Workflow Clarity

The numbered 1-3 gate sequence is clear, and the probe step includes explicit decision signals plus a checkpoint ('If unsure, ask. Default to the sidebar.'). It falls short of 5 because there is no validation or verification of the integration outcome (e.g. confirming the chat mounts and host-connect rejects as expected).

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ do not exist), and the body is organized into clear gate, instruction, and constraint sections with well-signaled pointers ('See integrate-fusion-agent', the docs URL). Per the simple-skill guideline, this warrants a 5.

5 / 5

Total

17

/

20

Passed

Description

78%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 scoped exception-path description with explicit trigger conditions, natural trigger terms, and strong disambiguation from its sibling skill. Its main weakness is that the capability itself (what the skill does once triggered) is implied rather than stated.

Suggestions

State the 'what' explicitly, e.g. prepend 'Wires the in-app Atlas chat (useAtlasChat) into a standalone Cognite app.' before the exception-path conditions.

Add a couple of natural trigger synonyms such as 'atlas agent in-app' or 'chat widget' to the Triggers list.

DimensionReasoningScore

Specificity

The description lists several concrete entities and actions — 'Use integrate-fusion-agent for Atlas/chat/agent', 'requires in-app useAtlasChat', 'connectToHostApp cannot provide the EOS sidebar' — rather than vague language. It falls short of a 5 because it never states what the skill actually does (wire/integrate an in-app chat), only the conditions under which it applies.

4 / 5

Completeness

The 'when' is exceptionally explicit ('Only when the user explicitly requires in-app useAtlasChat and connectToHostApp cannot provide the EOS sidebar (standalone app, always rejects)'), satisfying the 'Use when...' requirement. The 'what' is only implied via the skill domain and API name rather than stated ('Exception path' describes the role, not the capability), so it matches anchor 4 rather than 5.

4 / 5

Trigger Term Quality

'Triggers: useAtlasChat, in-app atlas chat, embedded chat, vendored atlas-agent' plus the negative trigger 'Not for generic "add a chat"' give good natural keyword coverage, including the API name users would cite. Missing common synonyms/extensions (e.g. 'chat widget', 'atlas agent', casing variants), so not a 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche and actively disambiguates from the sibling skill: 'Use integrate-fusion-agent for Atlas/chat/agent', 'Only when...', and the explicit exclusion 'Not for generic "add a chat"'. Minimal conflict risk with any other skill.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

cognitedata/builder-skills

Path

skills/integrate-atlas-chat/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.