What problem does it solve? Wiring the @amd-gaia/gaia npm package into a Node, TypeScript, or Electron app involves non-obvious details: a SHA-256 integrity gate that blocks fetches, platform gaps in the sidecar builds, a streaming SSE query contract, and authentication and confirmation behaviors that differ between transports. This Skill captures those rules so an integration works on the first attempt instead of after debugging 401s, 409s, and silent refusals. ## Core Features & Use Cases - Binary delivery and verification: Explains how the package fetches and SHA-256 verifies the agent sidecar and terminal UI against binaries.lock.json, including placeholder-hash blocking and platform coverage gaps (no linux-arm64 or win32-arm64 sidecar). - Sidecar lifecycle and REST contract: Covers startSidecar/shutdown tree-kill semantics, caller-auth bearer tokens, the /v1/gaia/query SSE event vocabulary, session_id retention, and cancel/respond endpoints. - Use Case: You are embedding GAIA into an Electron app. The Skill tells you to mint a bearer token via the env option, reuse one session_id per conversation, treat needs_confirmation as a terminal refusal over HTTP, and branch on /v1/gaia/init's ready field rather than /health. ## Quick Start Ask the agent to walk you through embedding @amd-gaia/gaia in a Node app, from fetchAll and startSidecar through a streaming /v1/gaia/query call.