stream-docs
Skill21 starsChanged 7 days agoApache-2.0View on GitHub
Compatibility entrypoint for requests naming stream-docs. Uses getstream docs for SDK documentation lookups.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nnawar706/fluentotheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nnawar706/fluento★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- stream-androidSkill
- stream-builderSkill
- stream-feeds-migrationSkill
- stream-flutterSkill
- stream-react-nativeSkill
- stream-reactSkill
- streamSkill
- stream-swiftSkill
- stream-unitySkill
- stream-unrealSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Only when the CLI cannot be installed, fall back to fetching https://getstream.io/docs/llms.txt and following the links there.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Stream Docs (compatibility)
The recommended way to access Stream platform and SDK documentation is
getstream docs. Read getstream docs -h for supported arguments. Refer to
stream skill for CLI guidance.
In a command substitution like $(getstream docs <id>) don't add 2>&1 to
redirect stderr. The path you need is on stdout.
Cite every page you answer from with the URL in its "For the most recent version of this documentation" line.
Only when the CLI cannot be installed, fall back to fetching
https://getstream.io/docs/llms.txt and following the links there. Cite the URL
of each page you used.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.