Claude Code skills for integrating CloudSignal real-time messaging into your applications.
npx skills add cloudsignal/agent-skills| Skill | Command | Description |
|---|---|---|
| cloudsignal-websocket | /cloudsignal-websocket |
React MQTT context for real-time notifications over WebSocket. Supports Clerk, Supabase, Auth0, Firebase auth providers. |
| cloudsignal-rest | /cloudsignal-rest |
Python REST publisher for serverless backends. Connection pooling, retry, throttling. |
Invoke the skill in Claude Code:
/cloudsignal-websocket
Claude will ask for your auth provider (Clerk, Supabase, Auth0, Firebase), organization ID, and topic namespace, then generate:
mqtt-context.tsx— Full React context provider with auth integrationcloudsignal.d.ts— TypeScript declarations for@cloudsignal/mqtt-client
Invoke the skill in Claude Code:
/cloudsignal-rest
Claude will ask for your topic namespace, message types, and Python framework, then generate:
cloudsignal.py— Async REST publisher module with retry and throttling
Frontend (WebSocket) CloudSignal Backend (REST)
+-------------------+ +------------------+ +------------------+
| React App |--JWT-->| Token Service | | Python Worker |
| mqtt-context.tsx | | MQTT Broker |<-HTTP--| cloudsignal.py |
| |<--WSS--| REST Publisher | | |
+-------------------+ +------------------+ +------------------+
- Frontend connects via WebSocket using auth-provider JWT tokens
- Backend publishes via HTTP REST API — no persistent connections needed
- Both use the same topic namespace for end-to-end real-time messaging
- A CloudSignal organization — Create one at dashboard.cloudsignal.app
- An External Auth Provider integration configured (for frontend)
- A REST Publisher API key (
sk_xxx) (for backend)
To test skills during development without installing:
claude --add-dir ./skills/cloudsignal-websocket
claude --add-dir ./skills/cloudsignal-restMIT