integrate-atlas-chat

MUST be used whenever building a chat UI with Atlas agents in a Flows app. Do NOT manually write useAtlasChat integration code — this skill handles installation, component structure, and hook wiring. Triggers: useAtlasChat, atlas chat, streaming chat, agent chat, chat interface, chat component, chat UI. For a full chat app, run skills in order: (1) integrate-atlas-chat, (2) create-client-tool (per tool), (3) setup-python-tools (if Python tools needed).

Jump to install

Repository: cognitedata/builder-skills
Last source activity: July 22, 2026 at 14:29
Detected SKILL.md language: English
Stars: 5
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/cognitedata/builder-skills --skill integrate-atlas-chat

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

13 files

SKILL.md

Source instructions · Read-only preview

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:

The user asked for an in-app / embedded chat — not "add Atlas" / "add a chat"
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.
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.

Back to search Back to installation

flows-code-review

Run the technical (code) review step of Flows app certification in a local git app. Loads flows-review-checks for the actual bar, then writes artifacts under reviews/code-review/feedback-round-<N>/. Use when the user asks for a Flows code review, technical review, pre-submit review, app certification code review, or "run flows-code-review". Re-run until 0 open Must Fix items remain before moving on to flows-design-review.

2026-09-07

flows-review-checks

Canonical Flows technical-review checks and scoring (hunt commands, coverage scope, package audit, public criteria, Must/Should/Nice). Loaded by flows-code-review and by any external review skill. Do not copy these checks into another skill. Do not use this skill to fix code. Use when an orchestrator says to load flows-review-checks, or when aligning two review flows on the same bar.

2026-09-07

aura-review

Checks how well an app uses Aura, Cognite's design system: what fraction of its components are Aura vs. custom-built, whether any custom components should really have been an existing Aura component, and whether Aura components got styled in ways that break the design system's own rules. Runs fully automatically by scanning the app's source and checking it against Aura's docs — no back-and-forth, so it also works unattended in CI. Writes a plain-language report to aura-review/report.md and a machine-readable aura-review/stats.json. Use when asked to run an Aura audit, check Aura compliance, or score how compliant an app is with the Aura design system.

2026-09-04

View all from this repository

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:

The user asked for an in-app / embedded chat — not "add Atlas" / "add a chat"
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.
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.

integrate-atlas-chat

Source facts

Install options

Review the source files

Integrate Atlas Agent Chat (exception path)

More from this repository

Integrate Atlas Agent Chat (exception path)

More from this repository