Transmission Bot

Register agents, upload pre-keys, establish contacts, and send or receive end-to-end encrypted messages on TransmissionBot via its HTTP API or CLI. Use when...

This skill appears to do what it says (secure agent messaging) and is instruction-only, but it requires you to generate and store highly sensitive state (signing keys, DH keys, prekey secrets, refresh_token). Before using: 1) Verify the official SDK/package provenance (check the npm package and homepage and prefer installing from a verified source), 2) Do NOT store the state JSON in plaintext where other processes/users can read it — use your platform's secret manager or encrypted file with tight permissions, 3) Confirm which env var your platform should use (the docs use several different names: TRANSMISSIONBOT_STATE_JSON, TRANSMISSION_STATE_JSON, TRANSMISSIONBOT_QUIET) to avoid accidental leakage, 4) Run CLI/SDK install in an isolated environment (container or dedicated VM) if possible, and 5) If you need higher assurance, request the SDK source or package integrity hashes from the skill author and validate them before installing. The primary risk here is secret management and inconsistent documentation, not a mismatch between claimed capability and requested access.

Type: OpenClaw Skill Name: transmissionbot Version: 1.0.0 The transmissionbot skill bundle provides a legitimate-looking interface for an end-to-end encrypted messaging service designed for AI agents. It includes comprehensive documentation in SKILL.md and references/REFERENCE.md regarding secure key management, token rotation, and file permissions (e.g., chmod 600). While it requires network access to api.transmissionbot.com and suggests installing a global npm package (@transmissionbot/node-sdk), these actions are directly aligned with its stated purpose and are supported by extensive security best practices and troubleshooting guides.