Stream

Routes Stream SDK work to the right specialist without you having to guess. If you're building a React Native app with video calls, it finds stream-react-native. If you need to list flagged messages or query channels, it hands off to stream-cli. Documentation lookups go to stream-docs, web scaffolding to stream-builder, and platform-specific integration to the matching peer skill. The routing is deterministic, matching your input against signals in peers.yaml, so you get Swift tooling for Xcode projects and web scaffolding when there's no platform hint. It's a dispatcher, not a worker. The actual CLI commands, SDK wiring, and doc searches happen in the sub-skills it loads on demand.

skills.sh installs: 1.6K
GitHub stars: 21
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add getstream/agent-skills --skill stream --agent claude-code

Installs into .claude/skills of the current project.

Files

Stream

Stream (getstream.io) provides APIs and SDKs for adding Chat, Video (calls and livestreaming), Activity Feeds, and Moderation to apps. A Stream account has organizations; an organization has apps; an app has one or more API key + secret pairs. All data - users, channels, calls, feeds - is scoped to an app. Client SDKs cover React, iOS, Android, React Native, Flutter, Unity, and Unreal; server-side SDKs mint user tokens and call the same API. Most client SDKs provide UI kits.

Stream Agents runs voice and text AI agents on Stream's backend. An agent is a folder of plain files (agents/<name>/agent.yaml, instructions, guardrail, knowledge, skills, simulations) synced with getstream agents, and sessions with it are opened through the Agents SDKs (@stream-io/stream-agents on the web). A session's conversation is a Chat channel and its voice is a Video call, so the app around an agent is a Chat and Video app like any other.