Agent skill · software engineering · getstream
stream-android
Build and integrate Stream Chat, Video, and Feeds in Android apps. Use for Jetpack Compose, Android Studio, and Gradle project work — including Stream package setup, auth and token wiring, screen blueprints, and any follow-up Stream UI work such as adding screens, navigating between channel list and channel/message screens, channel tap handling, deep links, push routing, theming, custom channel/message UI, video calling flows (joining/starting calls, ringing, custom call controls and participant tiles), and Feeds surfaces (timeline, activity composer, threaded comments, follow graph / profile, notification feed, stories).
Why this skill is useful
Provides specific integration patterns and setup procedures for Stream Chat, Video, and Feeds in Android apps that the AI wouldn't reliably generate on its own.
What it needs
Requires getstream installed locally. About 8k tokens when loaded. Last updated 2026-08-05. 17 stars on the source repository.
What this skill does
Stream Android - skill router + execution flow Rules: Read RULES.md once per session - every non-negotiable rule is stated there, nowhere else. This file is the single entrypoint: intent classification, local project detection, and module pointers for Stream work in Android apps. --- Step 0: Intent classifier (mandatory first - never skip) Before any tool call, decide the track from the user's input alone - no probes first. Signals -> track Signal in user input Track --- --- Explicit product/framework token: Chat Compose, Chat XML, Video Android, Video Compose, Feeds Android, Feeds Compose, etc. C - Reference lookup Words "docs" or "documentation" around Stream Android/Compose work C - Reference lookup "How do I {X} in Compose/XML/Android?", "What does {SDK type/Composable/View/Fragment} do?" C - Reference lookup "Build me a new Android app", "create a Compose app", "new Android app" + Stream product A - New app "Add/integrate Stream into this app", "wire Chat/Video/Feeds into my Android project" B - Existing app "Install Stream packages", "set up Stream in Android Studio", "wire auth/token flow" with no broader feature request D - Bootstrap / setup Request carries a target appearance - a screenshot, a Figma frame, or "make the chat look like WhatsApp / Telegram / Slack / \<app\>" B (or A) + the styling-depth flag below -> design-matching.md "Migrate from Sendbird", "replace the Sendbird Chat SDK with Stream", "we're switching off Sendbird / SendbirdUIKit / uikit-compose" B + the migration flag below -> sendbird-migration.md Bare /stream-android with no args List the tracks briefly and wait Disambiguation flow If the request is ambiguous between build/integrate and reference lookup, ask one short question and wait: Do you want me to wire this into the project, or just map the Android SDK pattern and files? After classification Tracks A, B, D -> run Step 0.5 (credentials) first, then Project signals once per session, then continue in builder.md and sdk.md. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills getstream/stream-android