
from claude-to-im-skill2,490
Bridge a Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so you can chat with the agent from your phone. Supports setup, start/sto
Provides a managed bridge that forwards a running Claude Code or Codex session to instant messaging platforms (Telegram, Discord, Feishu/Lark, QQ, WeChat). It exposes subcommands to set up channel credentials, start/stop the background daemon, view status and logs, reconfigure credentials, and run diagnostics (doctor). The bridge stores runtime config and data under ~/.claude-to-im and includes platform-specific setup flows such as WeChat QR login and Feishu two-phase permission steps.
Use this skill when you want to interact with a Claude/Codex coding agent from mobile messaging apps, need to forward agent replies to a chat, or when you must manage the bridge lifecycle (setup, start, stop). Also use it to diagnose connectivity or permission issues with IM platforms. Do NOT use it for building standalone bots or custom SDK integrations — those are regular development tasks.
This skill targets Claude Code and Codex runtime environments (detects AskUserQuestion availability to determine interactive vs non-interactive flows). It expects a shell/Bash-capable agent and familiarity with node/npm helpers for Weixin login.
Claude-to-IM Bridge bridges Claude Code/Codex sessions to Telegram, Discord, Feishu, QQ, and WeChat. SKILL.md is exceptionally detailed with clear subcommand routing, interactive setup wizard, and platform-specific guidance. Scripts are well-structured bash with proper error handling and platform detection. Daemon management uses launchd (macOS), setsid/nohup (Linux), and WinSW/NSSM (Windows). Scripts failed in temp dir as expected — they source relative sibling scripts and check for local files.
Well-crafted skill with strong security practices: secrets masked in output, config.env chmod 600 enforced, token validation built in. No exfiltration risks, no remote code execution patterns. Minor shell quoting concerns in daemon.sh env handling.