Skip to main content
skill CX Codex

integrate-atlas-chat — Claude Code skill: in-app Atlas chat

A skill that wires the Atlas chat into your app's own UI. Use it when the Fusion/EOS sidebar is not an option.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add cognitedata/builder-skills --skill integrate-atlas-chat -a claude-code
Open on GitHub

What integrate-atlas-chat does

This skill walks the exception path: it connects useAtlasChat inside the app instead of relying on the Atlas sidebar. First it probes your code for @cognite/app-sdk and connectToHostApp or useHostApp. If the host connect resolves inside Fusion/EOS, the skill stops and points you to integrate-fusion-agent.

In-app chat is allowed only for standalone apps, where host connect always rejects and the app never loads in Fusion. When the case is unclear, the skill tells you to ask and defaults to the sidebar. Then it wires useAtlasChat for the agent you pass as [agent-external-id], following the Cognite docs.

Your product UI stays as it is; the chat does not replace the app view. One more limit: do not map send() or chat completions over DMS rows. If per-item completions are required, the cap is 5 per user action with a ceiling of 50, cached by space:externalId:lastUpdatedTime.

What it helps with

  • embed the Atlas chat in a standalone app
  • check whether the Fusion/EOS sidebar is available
  • wire useAtlasChat following the Cognite docs
  • cap per-item chat completions and cache them
  • add a chat without replacing the product UI

Example prompts for the agent

  • Add an in-app Atlas chat — the sidebar won't work here
  • Wire useAtlasChat for agent my-agent-id
  • Check if connectToHostApp resolves inside Fusion before embedding the chat

How to install integrate-atlas-chat

1Skills CLI (Vercel)

npx skills add cognitedata/builder-skills --skill integrate-atlas-chat -a claude-code

2Manually: put the files in place

~/.claude/skills/integrate-atlas-chat/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/integrate-atlas-chat/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about integrate-atlas-chat

How do I install integrate-atlas-chat in Claude?

Run npx skills add cognitedata/builder-skills --skill integrate-atlas-chat -a claude-code. The skill lands in ~/.claude/skills/integrate-atlas-chat/SKILL.md.

What does integrate-atlas-chat do?

It embeds the Atlas chat in your app's UI through useAtlasChat. It first confirms the Fusion/EOS sidebar is not an option, then follows the non-standard path.

When should I use integrate-atlas-chat instead of integrate-fusion-agent?

Only when the user explicitly asks for an embedded chat and host connect cannot provide the EOS sidebar — a standalone app, where connect always rejects. Otherwise the skill sends you to integrate-fusion-agent.

Source text

SKILL.md · Apache-2.0
---
name: integrate-atlas-chat
description: >-
  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".
allowed-tools: Read, Glob, Grep, Edit, Write, Bash
metadata:
  argument-hint: "[agent-external-id]"
---

# Integrate Atlas Agent Chat (exception path)

**Stop.** Use **`integrate-fusion-agent`** (Atlas / EOS sidebar) unless all of:

1. The user asked for an **in-app / embedded** chat — not "add Atlas" / "add a chat"
2. The host Atlas sidebar cannot work. There is **no manifest field** for this. Probe the app:
   - `@cognite/app-sdk` + `connectToHostApp` / `useHostApp` resolving inside Fusion/EOS → sidebar works; do not continue
   - Standalone-only (host connect always rejects; app is never loaded in Fusion) → in-app chat is allowed
   - If unsure, ask. Default to the sidebar.
3. The user accepted this as the non-standard path

Then follow https://docs.cognite.com/cdf/flows/guides/ai_agent_integration and wire `useAtlasChat` for **$ARGUMENTS**. Keep the product UI; do not replace the app with a chat view.

Do not map `send()` / chat completions over DMS rows. If per-item completions are required: **5** per user action, ceiling **50**, cache by `space:externalId:lastUpdatedTime`. See `integrate-fusion-agent`.

© cognitedata · Apache-2.0 · cognitedata/builder-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set12

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor