How do I install the Hermes Telegram Bot System skill?

Run npx skillmds@latest add loopyluci/hermes-telegram-bot-system in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Hermes Telegram Bot System skill do?

Use when managing the Hermes Telegram Bot control system. It is listed under Coding & Dev Tools on SkillMD.

Is Hermes Telegram Bot System safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hermes Telegram Bot System?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hermes Telegram Bot System free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hermes Telegram Bot System?

LoopyLuci (@loopyluci) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hermes Telegram Bot System by loopyluci

Name: Hermes Telegram Bot System
Rating: 4.5 (4 reviews)
Author: LoopyLuci

File contents

Hermes Telegram Bot Control System

A next-generation Telegram bot control system purpose-built for AI agent use. Located at D:\Projects\Bots\hermes-telegram-bot.

Architecture

Telegram Bot (ptb) ─┐
MCP Server (FastMCP)─┤── Core Engine ──┬── Telemetry Collector
Web Dashboard (FastAPI)─┘               ├── Service Manager
CLI / Watchdog                          ├── State Store (SQLite)
                                        └── Config Manager (YAML)

Components

File	Role
`main.py`	Entry point — orchestrates all components
`bot.py`	Enhanced Telegram bot with inline keyboard UI
`mcp_server.py`	MCP control server exposing 50+ tools
`dashboard.py`	Real-time web dashboard with live charts
`telemetry.py`	System/bot metrics collection (CPU, mem, latency, rates)
`service_manager.py`	Process lifecycle orchestration with auto-restart
`state.py`	SQLite-backed persistent state (users, services, messages, alerts)
`config.py`	YAML configuration with dotenv auto-loading
`models.py`	Shared data models (TelemetrySnapshot, Service, BotUser, AlertRule)
`watchdog.py`	Cron-friendly keepalive script (no_agent mode)

Running

# Full system (bot + dashboard + MCP)
cd D:\Projects\Bots\hermes-telegram-bot
python main.py

# Skip Telegram bot (dashboard + MCP only — for headless)
python main.py --no-bot

# Skip dashboard
python main.py --no-dashboard

# Skip MCP server
python main.py --no-mcp

Persistent startup via watchdog + Hermes cron:

Watchdog script: ~/.hermes/scripts/hermes-telegram-bot-watchdog.py
Cron job: "Telegram Bot Watchdog" — runs every 5 minutes, no_agent mode
Uses subprocess.DETACHED_PROCESS on Windows to survive terminal closure

Ports

Service	Port
Dashboard	9876
MCP Server	9877

MCP Tool Surface (50+ tools)

Bot Control: bot_status, bot_start, bot_stop, bot_restart, bot_config_get/set, bot_switch_mode

Service Management: service_list, service_get, service_register/unregister, service_start/stop/restart/kill, service_set_autorestart, service_logs, service_bulk_action

Telemetry: telemetry_snapshot, telemetry_history, telemetry_history_db, telemetry_latency_stats, telemetry_message_rate, telemetry_alert_create/list/delete/toggle

User Management: user_list, user_get, user_add/remove, user_set_role, user_toggle_active, pairing_list/approve/revoke

Analytics: message_stats, session_stats, daily_report

System: health_check, system_info, log_tail, gateway_log_tail, dashboard_status/start/stop, hermes_gateway_status/start/stop

Hermes MCP Integration

Configured in ~/.hermes/config.yaml:

mcp_servers:
  hermes-telegram-bot:
    url: http://127.0.0.1:9877/mcp
    timeout: 180
    connect_timeout: 60

Tools are prefixed mcp_hermes_telegram_bot_bot_status etc.

Telegram Bot UI (Inline Keyboards)

Main Menu — status, telemetry, services, analytics, quick actions
Service control — start/stop/restart/toggle auto-restart per service
Pagination — services list paginated 5 per page
Confirmation dialogs — destructive actions require confirm
Pairing flow — unknown users get a pairing code for admin approval

---name: hermes-telegram-bot-systemdescription: Use when managing the Hermes Telegram Bot control system.---# Hermes Telegram Bot Control SystemA next-generation Telegram bot control system purpose-built for AI agent use. Located at `D:\Projects\Bots\hermes-telegram-bot`.## Architecture```Telegram Bot (ptb) ─┐MCP Server (FastMCP)─┤── Core Engine ──┬── Telemetry CollectorWeb Dashboard (FastAPI)─┘ ├── Service ManagerCLI / Watchdog ├── State Store (SQLite) └── Config Manager (YAML)```## Components| File | Role ||------|------|| `main.py` | Entry point — orchestrates all components || `bot.py` | Enhanced Telegram bot with inline keyboard UI || `mcp_server.py` | MCP control server exposing 50+ tools || `dashboard.py` | Real-time web dashboard with live charts || `telemetry.py` | System/bot metrics collection (CPU, mem, latency, rates) || `service_manager.py` | Process lifecycle orchestration with auto-restart || `state.py` | SQLite-backed persistent state (users, services, messages, alerts) || `config.py` | YAML configuration with dotenv auto-loading || `models.py` | Shared data models (TelemetrySnapshot, Service, BotUser, AlertRule) || `watchdog.py` | Cron-friendly keepalive script (no_agent mode) |## Running```bash# Full system (bot + dashboard + MCP)cd D:\Projects\Bots\hermes-telegram-botpython main.py# Skip Telegram bot (dashboard + MCP only — for headless)python main.py --no-bot# Skip dashboardpython main.py --no-dashboard# Skip MCP serverpython main.py --no-mcp```Persistent startup via watchdog + Hermes cron:- Watchdog script: `~/.hermes/scripts/hermes-telegram-bot-watchdog.py`- Cron job: "Telegram Bot Watchdog" — runs every 5 minutes, no_agent mode- Uses `subprocess.DETACHED_PROCESS` on Windows to survive terminal closure## Ports| Service | Port ||---------|------|| Dashboard | 9876 || MCP Server | 9877 |## MCP Tool Surface (50+ tools)**Bot Control:** `bot_status`, `bot_start`, `bot_stop`, `bot_restart`, `bot_config_get/set`, `bot_switch_mode`**Service Management:** `service_list`, `service_get`, `service_register/unregister`, `service_start/stop/restart/kill`, `service_set_autorestart`, `service_logs`, `service_bulk_action`**Telemetry:** `telemetry_snapshot`, `telemetry_history`, `telemetry_history_db`, `telemetry_latency_stats`, `telemetry_message_rate`, `telemetry_alert_create/list/delete/toggle`**User Management:** `user_list`, `user_get`, `user_add/remove`, `user_set_role`, `user_toggle_active`, `pairing_list/approve/revoke`**Analytics:** `message_stats`, `session_stats`, `daily_report`**System:** `health_check`, `system_info`, `log_tail`, `gateway_log_tail`, `dashboard_status/start/stop`, `hermes_gateway_status/start/stop`## Hermes MCP IntegrationConfigured in `~/.hermes/config.yaml`:```yamlmcp_servers: hermes-telegram-bot: url: http://127.0.0.1:9877/mcp timeout: 180 connect_timeout: 60```Tools are prefixed `mcp_hermes_telegram_bot_bot_status` etc.## Telegram Bot UI (Inline Keyboards)- **Main Menu** — status, telemetry, services, analytics, quick actions- **Service control** — start/stop/restart/toggle auto-restart per service- **Pagination** — services list paginated 5 per page- **Confirmation dialogs** — destructive actions require confirm- **Pairing flow** — unknown users get a pairing code for admin approval

Frequently asked questions

Hermes Telegram Bot System