What problem does it solve? Developers who want to embed a pre-built GAIA hub agent into their own application face uncertainty about which agents exist, which runtime to pick, and how the two integration shapes (npm sidecar vs. Python framework plugin) actually work. ## Core Features & Use Cases - Live agent discovery: Lists hub/agents/ at runtime to find the current set of agents and their available runtimes instead of trusting a hardcoded list. - Two integration shapes: Explains the npm shape (install package, fetch and SHA-256-verify a binary, spawn a local HTTP sidecar, call a typed TypeScript client, shut down) versus the Python shape (pip install, auto-registration via the gaia.agent entry-point group, invocation through the GAIA registry or process_query). - Per-agent handoff: Checks for an agent-specific SKILL.md and executes it when present, otherwise synthesizes steps from the agent's README, manifest (gaia-agent.yaml / package.json), and source entry point. - Use Case: A developer building an Electron app asks to add the email agent; the skill identifies the npm agent-email package, then follows its own SKILL.md and SPEC.md for the exact sidecar integration contract. ## Quick Start Ask the assistant to integrate a specific GAIA hub agent, such as the email or analyst agent, into your application and specify whether your project is JavaScript/TypeScript or Python.
