by software-mansion-labse3f00cdb3494MIT291 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago
Software Mansion's Fishjam — hosted WebRTC platform for video, audio, and one-to-many livestreaming. MUST USE before writing, reviewing, or debugging ANY code that talks to a Fishjam instance from a backend (Node, Python) or a client (React web, React Native / Expo). Routes to platform fundamentals and the right SDK sub-skill. Trigger on: 'Fishjam', 'fishjam.io', 'fishjam.swmansion.com', 'fishjam dashboard', 'Fishjam ID', 'management token', 'peer token', 'sandbox API', 'livestream room', '@fishjam-cloud/js-server-sdk', 'fishjam-server-sdk', '@fishjam-cloud/react-client', '@fishjam-cloud/react-native-client', '@fishjam-cloud/ts-client', 'FishjamClient', 'FishjamProvider', 'FishjamNotifier', 'FishjamAgent', 'createPeer', 'createRoom', 'createAgent', 'createLivestreamStreamerToken', 'createMoqToken', 'refreshPeerToken', 'webhook', 'gemini fishjam', 'vapi fishjam', 'fishjam expo plugin'.
Routes agents to Fishjam WebRTC platform fundamentals and the correct SDK sub-skill for backend or client code.
What it does
This skill is a routing guide for Software Mansion's hosted Fishjam WebRTC platform, covering video, audio, and one-to-many livestreaming. It points to a platform reference for the domain model (rooms, peers, tracks, tokens, notifications) and to sub-skills for the JavaScript server SDK, Python server SDK, React client, React Native/Expo client, and direct REST usage. It also states critical rules about management tokens, 24-hour peer tokens and refresh, and dev-only Sandbox API URLs.
When to use it
Use it before writing, reviewing, or debugging any code that talks to a Fishjam instance, whether from a Node or Python backend or a React, React Native, or Expo client. It is also relevant when working with Fishjam tokens, rooms, peers, webhooks, or livestreaming concepts.
Requirements
No scripts are shipped; it is instructions only. It assumes access to the referenced sub-skill files under references/ and, for actual use, a Fishjam account with management and peer tokens.
Fishjam
Software Mansion's hosted WebRTC platform. Routes between platform fundamentals and the four SDKs.
Read the references/platform/SKILL.md first for the domain model (rooms, peers, tracks, tokens, notifications). Then read the SDK sub-skill that matches what you're building. All sub-skills are in references/.
Which sub-skill do I need?
You are writing…
Sub-skill
Anything Fishjam — start here for glossary, room types, auth, notifications, REST
references/platform/SKILL.md
A Node.js / Express / Fastify / Hono backend
references/js-server-sdk/SKILL.md
A Python / FastAPI / Flask backend
references/python-server-sdk/SKILL.md
A React app in a browser
references/react-client/SKILL.md
A React Native / Expo app for iOS or Android
references/react-native-client/SKILL.md
Vanilla TS / Svelte / Vue / web worker (non-React)
references/react-client/SKILL.md → ts-client-escape.md (drop to @fishjam-cloud/ts-client)
Just calling REST directly (no SDK)
references/platform/rest-endpoints.md
A production Fishjam app always has a backend (server SDK) + a client (client SDK). For prototyping you can skip the backend with the Sandbox API — see references/platform/sandbox-vs-production.md.
Critical rules
Management token never leaves the backend. If it leaks, regenerate it from the Dashboard.
Peer tokens are valid for 24 hours from creation. The token is consumed during the initial WS handshake; an established session keeps running on its own. If the peer hasn't connected yet or needs to reconnect after 24h, call refreshPeerToken / refresh_peer_token to mint a new one.
Sandbox API URLs are dev-only. Anyone holding one can create rooms on your account — never ship in a production client build.
