Stream

Stream - skill router + CLI

This skill picks the track from the user's input. Building (web + platform) and docs go to dedicated sub-skills; CLI tasks - querying data, configuring an app, onboarding, installing skills - are handled here (see Stream CLI below), since the getstream CLI underlies every track.

Read first: `RULES.md`. Non-negotiable rules apply, including the Peer skills procedure. `peers.yaml` (schema: `peers.schema.json`) is the single source of truth for peer names, Glob paths, install commands, and routing signals. Install a missing peer on demand per its policy in peers.yaml (Glob its path, run its install command - getstream skills <name>), then invoke via the Skill tool or Read it inline. Don't call Skill before the Glob; it surfaces a confusing "Unknown skill" error. Do not stop after naming the track.

By task

Build or integrate Stream in a platform-specific app -> peer pack from `peers.yaml` (check peer signals first)

• Match user input or cwd against each peer's signals (e.g. swift / swiftui / .xcodeproj -> stream-swift; react native / expo / stream video react native -> stream-react-native; unreal / .uproject / umg -> stream-unreal; unity / monobehaviour / .unitypackage -> stream-unity)
• All peers install on demand - install if missing, then route, no prompt
• An SDK/engine signal beats an OS-target signal. When both appear, the pack that owns the SDK wins: "build an Unreal chat app for iOS" is stream-unreal (not stream-swift), "a Unity game on Android" is stream-unity (not stream-android). ios / android / xcode / gradle describe the build target; unity / unreal / .uproject / .unitypackage / umg / flutter / react native describe the SDK. Same rule for flutter + ios.
• Name the engine for game requests. stream-unreal and stream-unity both claim generic game phrasing (in-game chat, game chat). An explicit engine token decides it; with neither engine named and no .uproject / ProjectSettings/ in the cwd, ask one short question ("Unity or Unreal?") rather than guessing. Note the capability difference that answer implies: Unity has Chat and Video, Unreal has Chat only.
• Peer signals take precedence over the web rows below. A request like "add a video call to my Expo app" or "scaffold a React Native app with Stream Video" matches stream-react-native, not the web packs - the platform token wins.

Build / enhance / audit / migrate a web app with Stream (React / Next.js) -> use the stream-react skill (the default web pack when no other platform signal is present)

• "build me a Chat/Video/Feeds app", "scaffold", "create a new ...", "add Chat to this app", "integrate Video", "drop Feeds into ...", "upgrade/migrate ... to vN" - and no platform signal (no react native, expo, swift, ios, android, etc.)
• React / Next.js tokens (stream-chat-react, @stream-io/video-react-sdk, useCreateChatClient, MessageList, ...) with a build/integrate verb also route here
• Covers Track A (scaffold, Steps 0-7), Track E (enhance an existing project), Track F (read-only best-practices audit), Track M (migrate/upgrade an SDK version)

Build with the framework-agnostic builder -> use the stream-builder skill only when the user names it explicitly ("use stream-builder", "/stream-builder")

• stream-builder is the generic builder being extended to other app kinds; web React/Next.js defaults to stream-react above

Audit/review an existing Stream Video integration against best practices (read-only - no scaffolding, no CLI, no build steps)

• Peer signal (react native / expo) -> stream-react-native; web / React / Next.js or no platform signal -> stream-react (Track F)
• Video only. The dedicated best-practices audit covers Stream Video. Chat/Feeds have no dedicated audit checklist yet - stream-react handles those requests with a general docs-based review and says so up front.
• Triggers: "audit/review my video integration", "is my video app production-ready?", "what am I missing before launch?"
• Routes here even when the request contains "check" - the audit intent takes precedence over the CLI "check {anything}" route below

Build or review a Feeds v2 -> v3 sync mapping -> use the stream-feeds-migration skill

• "what mapping do we need?", "set up our v2 to v3 migration", "review our v3sync mapping", "why did the migrated activity lose its text/attachments/comments?"
• Produces the mapping config object by sampling the v2 app's own activities and reactions - it does not build or change an app
• Needs the v2 app's API key and secret in the environment; see the skill's Step 1 and `RULES.md` > Secrets

Query Stream data or run a CLI command -> handled here (see Stream CLI below)

• "list calls", "show channels", "any flagged", "find users", a literal getstream command, or "install the CLI" / "set up stream"

Search Stream SDK documentation -> use the stream-docs skill

• "docs", "documentation", explicit SDK token (Chat React, Video iOS, Feeds Node, Moderation)
• "how do I ... in <framework>", "how does <hook/component/method> work?", "what does <SDK thing> do?"

Pick a track

Scan the user's input for the signals below in order. The classifier is deterministic - no probes, no fetches, no CLI checks at this stage.