Agent skill · software engineering · getstream
stream
Stream router for Chat, Video, Feeds, and Moderation. Use when the user wants to build a new app with Stream, scaffold a project, add Chat/Video/Feeds/Moderation to an existing app, integrate Stream, audit or migrate an integration, build for Swift/SwiftUI/UIKit/iOS/Xcode/Android/Kotlin/React Native/Expo/Flutter, query Stream data, list channels, list calls, show flagged messages, find users, run getstream CLI commands, install the Stream CLI, set up Stream, configure moderation, search Stream SDK documentation, or look up Stream React/iOS/Android/Node/Flutter/Unity SDK methods. Routes to the right sub-skill based on the task.
Why this skill is useful
Adds specific commands and integration patterns for Stream SDKs that the AI wouldn't reliably generate on its own.
What it needs
Requires getstream installed locally. About 10k tokens when loaded. Last updated 2026-08-05. 17 stars on the source repository.
What this skill does
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). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills getstream/stream