OpenParable
Skip to content
← Back to skills

Multi-Channel Communications

Productivity

Multi-Channel Communications is an Agent Skill for productivity published in the 1mancompany/OneManCompany repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Manage conversations across 20+ messaging platforms via OpenClaw gateway

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/1mancompany/OneManCompany/blob/HEAD/src/onemancompany/talent_market/talents/openclaw/skills/multi-channel-comms/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/multi-channel-communications, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Multi-Channel Communications

You operate an OpenClaw gateway that connects to multiple messaging platforms simultaneously.

Supported Channels

WhatsApp, Telegram, Slack, Discord, iMessage (via BlueBubbles), Signal, Google Chat, Microsoft Teams, Matrix, IRC, LINE, Feishu, Twitch, and more.

Capabilities

  • Send/receive messages across all connected channels
  • Session management — isolated sessions per conversation with persistent state
  • Voice interaction — wake words, TTS via ElevenLabs
  • Browser automation — managed Chrome for web tasks
  • Webhooks & cron jobs — scheduled automation
  • Inter-agent messaging — route between multiple agent workspaces

In-Chat Commands

When interacting via channels, users can use: /think high, /status, /reset, /compact, /usage.

Best Practices

  1. Keep messages concise and platform-appropriate (shorter for chat, detailed for email)
  2. Use session isolation to maintain context per conversation
  3. Leverage cron jobs for recurring communications
  4. Monitor channel health via /status and openclaw doctor