Quickstart

In the next five minutes we'll install Stream Agent Skills and run our first invocation. By the end your agent will be answering Stream SDK questions from live documentation, and you'll know how to reach for the right skill from here on.

You'll need:

An AI coding agent that reads standard skills locations. Claude Code, Cursor, Windsurf and others all qualify. If yours doesn't, see Installation for the manual paste path and rejoin us at step 3.
Node.js installed locally, so you can run npx.

Step 1. Install the skills

In your terminal, run:

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

The skills.sh CLI detects which agent you're using and writes the markdown to that agent's skills directory (for example ~/.claude/skills/ for Claude Code). Nothing executes. Only markdown files land on your machine.

This installs the core skills (router, CLI, docs and builder). The platform packs for Swift, Android and React Native install on demand the first time you build for one of those.

Step 2. Verify your agent picked them up

Open your agent. You should now see /stream, /stream-builder, /stream-cli and /stream-docs available as slash commands:

❯ /stream

/stream          Stream router for Chat, Video, Feeds, and Moderation. Use when
                 the user wants to build a new app with Stream, scaffold a…
/stream-cli      Query Stream data and run CLI operations against Chat, Video,
                 Feeds, and Moderation: list channels, show flagged messages…
/stream-docs     Search live Stream SDK documentation for Chat, Video, Feeds,
                 and Moderation. Look up how a Stream React/iOS/Android hook…
/stream-builder  Build a new app or add Stream products to an existing app.
                 Scaffold Next.js + Tailwind + Shadcn + Stream SDKs end-to-end…

The platform skills (/stream-swift, /stream-android, /stream-react-native) aren't installed yet. The router adds the one you need the first time you build for that platform.

If they aren't there, restart your agent so it rescans its skills directory.

Step 3. Your first invocation

The easiest skill to try first is /stream-docs, because it doesn't need credentials or any other setup. It looks up live SDK documentation and answers with a citation.

Type this into your agent:

/stream-docs how do I generate a user token in Node.js?

You should get a short answer that includes a code snippet using serverClient.createToken(), with a citation pointing at a getstream.io documentation URL:

❯ /stream-docs how do I generate a user token in Node.js?

Generate the token on your server with the API secret, then hand it to the
client. Never create user tokens in the browser.

  import { StreamChat } from "stream-chat";

  const serverClient = StreamChat.getInstance(apiKey, apiSecret);
  const token = serverClient.createToken("jdoe");

Source › https://getstream.io/chat/docs/node/tokens-and-authentication/

Click the citation. The code in the answer will match the code on that page.

That's the power of /stream-docs. Every answer is pulled from the current docs and quoted back to you with the source attached, so you can always check it.

Step 4. Let the router pick the skill

When you don't know which skill applies, invoke /stream and let it dispatch. Try:

/stream show me how to scaffold a Next.js chat app

The router reads the prompt, recognises it as a scaffolding request and hands off to /stream-builder. You'll see /stream-builder take over and start asking about your project:

❯ /stream show me how to scaffold a Next.js chat app

stream: classifying request… scaffold a new app
stream: dispatching to /stream-builder

stream-builder: I'll scaffold a Next.js chat app. A couple of questions first:
  1. What should I name the project?
  2. Add Video calling alongside Chat? (y/N)

You can cancel at the first prompt if you don't want to actually scaffold. The point is to see the routing work.

What you've done

In four steps you've:

Installed the full Stream skill pack with one command
Confirmed your agent picked the skills up
Used /stream-docs to pull a live, cited SDK answer
Seen /stream route a vague prompt to the right specialist

Where to go next

To scaffold a real app: read the /stream-builder reference for what the builder can produce and the prompts it understands.
To query your live Stream data: read the /stream-cli reference. The first invocation will prompt to install the Stream CLI binary.
To build for a native platform: pick the right platform skill. /stream-swift, /stream-android or /stream-react-native.
To understand the trust model: Security and trust covers everything that can touch the network and when.

Welcome

Install