Agent skill
telegram-bot-management
Telegram bot management and monitoring. TRIGGERS - telegram bot, claude-orchestrator, bot status, bot restart.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/telegram-bot-management
SKILL.md
Telegram Bot Management
Overview
Multi-workspace Telegram bot workflow orchestration with full supervision (launchd + watchexec). Manages the claude-orchestrator Telegram bot for headless Claude Code interactions.
When to Use This Skill
- Check bot status, restart, or troubleshoot issues
- Monitor bot health and resource usage
- View bot logs and debug problems
- Manage bot lifecycle (start/stop/restart)
Production Mode
As of v5.8.0, production mode is the only operational mode.
Bot Management Commands
Check Status
bot-service.sh status
# Or use alias
bot status
Shows:
- launchd supervision status
- watchexec process (PID, uptime, memory)
- Bot process (PID, uptime, memory)
- Full process tree
- Recent log activity
View Logs
bot-service.sh logs
# Or use alias
bot logs
Tails all logs:
- Launchd logs (supervision layer)
- Bot logs (application layer)
Restart Bot
bot-service.sh restart
# Or use alias
bot restart
Rarely needed due to automatic code reload via watchexec.
Stop Bot
bot-service.sh stop
# Or use alias
bot stop
Reference Documentation
For detailed information, see:
- Operational Commands - Status, restart, logs, monitoring commands
- Troubleshooting - Common issues and diagnostic steps
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?