stream

Stream overview, CLI, and router for Chat, Video, Feeds, Moderation, and Agents. Use for any Stream task: building or integrating Stream into web, iOS, Android, React Native, Flutter, Unity, or Unreal apps, building voice or text AI agents with Stream Agents, querying Stream data, running getstream CLI commands, looking up Stream SDK docs, or migrating (from Sendbird, or Feeds v2 to v3). Routes to the right skill.

1,561
installs: 0 up / 0 down, score 0.00
votes: 20
repo stars
Updated: less than a month ago
In the catalog since: 1 Oct 2026
From: getstream/agent-skills

Get it through your agent npx skills add getstream/agent-skills@stream

Skill instructions

Rendered from the published SKILL.md, 78 lines.

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/calypso 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.

The CLI

The getstream CLI is the base tool for everything account- and data-side: authenticating, onboarding a project (org, app, credentials), calling any API endpoint, obtaining credentials, minting user tokens, reading the docs, and installing the other Stream skills. Don't work from memory of it - run getstream -h and getstream <command> -h and follow what they print.

To install (unless already present):

curl -fsSL https://getstream.io/cli.sh | bash
getstream --version

Alternatively, the user can install the CLI from getstream.io/cli.

The getstream agents commands are only in beta builds, whose version is a date and a commit (YYYY-MM-DD-<commit>) rather than semver. A stable build answers them with "agents unavailable". Install the beta over it:

curl -fsSL https://getstream.io/cli/beta/install.sh | bash

Routing

First match wins:

Work on an app for a specific platform (build, integrate, audit, upgrade): use the platform-specific skill.
- stream-react (React / Next.js)
- stream-react-native (React Native / Expo)
- stream-swift (iOS / SwiftUI / UIKit)
- stream-android (Kotlin / Compose)
- stream-flutter
- stream-unity (Chat and Video)
- stream-unreal (Chat only)
Install a missing skill with getstream skills <name>, then follow it. For a web app, or a generic app, pick stream-react. A framework beats an OS: "an Unreal chat app for iOS" is stream-unreal.

An app built around Stream Agents is platform work too, even when the request only says "agent" or "voice agent". Configure the agent from its folder and getstream docs agents/<sdk> (javascript, ios, android, flutter), and build the app with the platform skill: its Chat UI kit renders the session's conversation and its Video SDK holds the call. React Native, Unity, and Unreal have no Agents client SDK - tell the user before building.
Migrate Feeds v2 to v3: use stream-feeds-migration skill.
Migrate from Sendbird: use the platform-specific skill to migrate the code; to move the data itself (users, channels, message history), read sendbird-data-migration.md.
Docs / "how does X work" questions: use the getstream docs command. In a command substitution like $(getstream docs <id>) don't add 2>&1. The path you need is on stdout.
Query or mutate app data ("list channels", "any flagged messages?", one-off API calls): use the getstream api command.
Genuinely ambiguous: ask.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "stream"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository getstream/agent-skills
Listing on skills.sh

From getstream/agent-skills via skills.sh

Related skills

streaming
Streaming wire protocols and backend helpers for assistant-ui, built on the assistant-stream package. Use when building a custom streaming endpoint outside the Vercel AI SDK with createAssistantStreamResponse, createAssistantStream, or createAssistantStreamController; choosing between the Data Stream protocol (useDataStreamRuntime, DataStreamEncoder, DataStreamDecoder) and the Assistant Transport protocol (AssistantTransportEncoder, AssistantTransportDecoder); decoding a response with AssistantStream.fromResponse, UIMessageStreamDecoder, or PlainTextDecoder; or wiring resumable streams through assistant-stream/resumable with in-memory, Redis, or ioredis stores. Route here for wire level symptoms: an unexpected part-start or text-delta shape, a tool call that never settles, a part that silently drops, a Content-Type mismatch, or a reload that cannot resume a response. For runtime hooks use runtime; for AI SDK route handlers without a custom protocol use setup; for cloud persistence use cloud.
6,408 installs
native-data-fetching
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).
46,367 installs
dart-build-cli-app
Architectural patterns, entrypoint structure, exit codes, stream routing, and subprocess spawning for Dart command-line interface (CLI) applications. Use when building CLI tools, console utilities, scripts, argument parsing with `package:args` (ArgParser or CommandRunner), handling exit codes, configuring executables in pubspec.yaml, spawning Dart subprocesses, or compiling native CLI binaries. Don't use for Flutter UI widgets, web applications, or standalone HTTP backend servers.
17,845 installs
dart-build-cli-app
Architectural patterns, entrypoint structure, exit codes, stream routing, and subprocess spawning for Dart command-line interface (CLI) applications. Use when building CLI tools, console utilities, scripts, argument parsing with `package:args` (ArgParser or CommandRunner), handling exit codes, configuring executables in pubspec.yaml, spawning Dart subprocesses, or compiling native CLI binaries. Don't use for Flutter UI widgets, web applications, or standalone HTTP backend servers.
13,744 installs
ios-networking
Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patterns. Use when working with REST APIs, downloading files, uploading data, WebSocket connections, pagination, retry logic, request middleware, caching, background transfers, or network reachability monitoring. Also use when handling HTTP requests, API clients, network error handling, or data fetching in Swift apps.
4,357 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.