Install

Three ways to install, ordered by how much you trust the tooling between you and the files. They all end up putting the same markdown in the same place. Pick the method that matches how you like to vet what reaches your machine.

The shortest path. One command fetches the core skills (the router plus the CLI, docs and builder specialists) into your agent's conventional skills directory:

npx skills add GetStream/agent-skills -s stream stream-cli stream-docs stream-builder

This trusts the skills.sh CLI to do the fetching for you. The CLI is open source and pulls markdown directly from GetStream/agent-skills. Works on every supported agent.

The platform packs (Swift, Android, React Native) stay out of this install. The router pulls in whichever one your project needs on demand. To add one up front, name it: npx skills add GetStream/agent-skills -s stream-swift.

Network operations

Nothing executes when you install, whichever path you took.

Two later operations can touch the network, and the agent prompts you before either one runs:

  • The Stream CLI binary install, which runs on your first /stream-cli invocation and only if the CLI isn't already on your machine.
  • The optional frontend skills that /stream-builder offers to pull in for UI scaffolding.

Both are explained in full, with the checksum and approval details, on the Security and trust page. Read it before installing, the same way you'd review any tool that touches your project. The complete file-by-file audit lives in the repo README.md.

Claude Code auto mode

Auto mode blocks runtime network fetches. Run the steps that download something once in a normal session first, then switch to auto mode.

Claude Code's auto mode runs shell commands through a safety classifier that blocks downloading and running code from the network. That stops every step in this pack that fetches something at runtime:

  • a platform pack the router would otherwise pull in on demand
  • the Stream CLI binary install (a curl ... | bash)
  • the optional frontend skills /stream-builder offers

Run these once in a normal session before switching to auto mode. The core install already includes the CLI, docs and builder skills, so the router never fetches those mid-task. If you build for a native platform, pre-install that pack once too (for example npx skills add GetStream/agent-skills -s stream-swift), so the router doesn't have to fetch it under auto mode. The Stream CLI binary install and the optional frontend skills still need a normal session, since both fetch at runtime.