shane9coy Telegram Skill
Auto-activate for Telegram message sending, daemon control, or bot configuration.
Daemon Control
| What | Command |
|---|---|
| Start listener | /telegram start |
| Stop listener | /telegram stop |
| Status + PID | /telegram status |
| Sleep (alerts only) | /telegram sleep |
| Wake (full response) | /telegram wake |
| View logs | /telegram logs |
Send Messages
/telegram send "Your message here"
/telegram brief # Send morning briefing now
/telegram alert "msg" # System alert notification
Architecture
Two-tier — daemon is standalone Python, cannot call Claude MCP directly:
| Tier | Mechanism | Commands |
|---|---|---|
| Direct | Pure Python + Supabase + API calls | tasks, goals, habits, weather, oracle vibe, pulse status |
| Subprocess | Shell to agent_orchestrator.py |
pulse send, newsletter gen |
| Queue | Write to /tmp/telegram_agent_queue.json |
order, book, vibe activity queries |
Key Files
Python scripts for the telegram listener are located in this skill's scripts/ directory: .claude/skills/telegram/scripts/
| Script | Description |
|---|---|
telegram_listener.py |
Main daemon script - always-listening bot |
telegram_helpers.py |
Helper functions for commands and responses |
telegram_send.py |
Standalone script to send messages |
| File | Description |
|---|---|
| Scripts | .claude/skills/telegram/scripts/ |
- Session:
~/mcp-servers/telegram-mcp/katana_bot.session - PID:
/tmp/telegram_listener.pid - State:
/tmp/telegram_listener_state.json - Logs:
logs/telegram_listener.log - Queue:
/tmp/telegram_agent_queue.json
Config (user_profile.json → telegram)
{ "chat_id": null, "notifications_enabled": true, "morning_brief": true,
"task_reminders": true, "goal_checkin_time": "20:00", "always_listening": true }
→ Full bot command reference: .claude/commands/telegram.md