chatops-session-ops
Operational SOP for debugging, repairing, and maintaining Telegram-to-OpenCode bridge bots and persisted sessions.
skill install https://www.promptspace.in/skills/chatops-session-opsAutomated Incident Response for Telegram ChatOps
Monitoring and maintaining Telegram-to-CLI bridge bots often involves complex state management across persisted sessions, cron jobs, and file uploads. This skill provides a specialized operational framework for debugging and repairing remote-control bot workflows when they experience connectivity issues or state corruption.
What it does
This skill acts as an automated Site Reliability Engineer (SRE) for your ChatOps infrastructure. It systematically inspects configuration files, persists session states, and monitors bridge health to identify the root cause of failures. Instead of broad resets that lose data, it applies the surgical, smallest-safe-fix approach to restore functionality.
- Session Management: Debugs stuck, missing, or invalid Telegram sessions through upstream verification.
- Cron Operations: Identifies and resolves duplicate, idle, or malformed cron job cycles.
- Upload Handling: Cleans up pending uploads and manages temporary file state to fix upload failures.
- Connectivity Triage: Differentiates between token issues, server reachability problems, and bridge-to-CLI disconnects.
Why use this skill
Manually prompting an AI to fix a bot often leads to dangerous "shotgun debugging" where broader-than-necessary resets cause data loss or security leaks. This skill enforces strict guardrails: it protects sensitive bot tokens, favors evidence-based triage over assumptions, and provides clear reporting on verified versus inferred recovery states. It ensures your bot operations remain stable, secure, and highly available.
Use cases
- Restore stale Telegram-to-OpenCode sessions via CLI state injection
- Repair corrupted session metadata to re-establish bridge connectivity
- Automate cron job health checks for persistent bot background tasks
- Validate file upload integrity between remote bots and bridge servers
- Debug bridge latency using real-time packet trace and log analysis
Example
Prompt
Output
Identified 2 orphaned .session files and a malformed cron entry in config.json. Action: Archived stale sessions, reconciled cron timing, and triggered HUP signal. Recovery: Verified via /status check. Status: Restored. Residual Risk: None.
Known limitations
- Cannot bypass Telegram API-side rate limits or revoked bot tokens. - Requires local file-system access to the bot's configuration and state directory.