Agent skill · writing content · getstream
stream-docs
Search live Stream SDK documentation for Chat, Video, Feeds, and Moderation. Look up how a Stream React/iOS/Android/Node/Flutter/Unity/Angular hook, component, or method works. Answer how-to questions about any Stream SDK across every framework and version. Triggers on 'docs', 'documentation', explicit SDK tokens (Chat React, Video iOS, Feeds Node, Moderation), and 'how do I ... in <framework>' phrasing. Answers come verbatim from getstream.io with citations - no CLI required.
Why this skill is useful
Provides access to live documentation for multiple Stream SDKs, enabling the AI to answer specific how-to questions with up-to-date information.
What it needs
About 12k tokens when loaded. Last updated 2026-08-05. 17 stars on the source repository.
What this skill does
Stream - Docs search (live SDK documentation) Read first (every session): Glob ../stream/SKILL.md and Read ../stream/RULES.md (both ship with this skill) - RULES.md includes a Peer skills table for installing/invoking any other pack skills on demand. Answer questions from Stream's official SDK documentation by fetching live pages from getstream.io. Covers Chat, Video, Activity Feeds, and Moderation across every framework and version. Docs index: https://getstream.io/cli/llms.txt No CLI gate, no up-front shell. This skill never invokes Write, Edit, npm, scaffold tools, or Bash(getstream ). Pure docs questions with an explicit SDK reach WebFetch without running any shell command. A small read-only probe runs only on demand - inside Step 1a below - when the SDK can't be resolved from the user's input. If the user's question requires running the CLI or building code, offer to switch - the user re-enters via the stream router or the stream-builder skill. --- Honesty rules (read before anything else) These rules are non-negotiable. Read them before every response. 1. Announce inference only when it happened. If you picked an SDK/version from anything other than explicit user input, say so in the first sentence - but only on the turn the inference happened: "Looking in Chat React v13 (detected from your package.json)..." "Inferring Video from your question about 'calls' - let me know if you meant something else..." On follow-ups within the same SDK, stay silent - the user knows what's loaded. Only re-announce when the SDK changes. For explicit input (e.g. /stream Chat React v14), no preamble is needed - go straight to the answer. 2. Write for humans, not for the skill. Users don't know (or care) how this skill works - they want their answer. No internal workflow terminology, status narration, or process commentary should ever appear in output. The answer itself proves the fetch worked. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills getstream/stream-docs