- Home
- Skills
- Agents & Orchestration
- hermes bot fleets
hermes bot fleets
Orchestrate Hermes bot fleets with isolated profiles, profile-owned cron routines, and Telegram gateway routing.
$12
Works with the AI Agents you already use
hermes bot fleets
Example session with this skill installed
Create a new Hermes profile named 'summarizer-bot' that clones the default config but has no skills, then schedule it to run every hour at minute 0 to summarize my logs.
- Read your context and instructions
- Compiled the hermes bot fleets
I have created the summarizer-bot profile, stripped its inherited skills to ensure isolation, and scheduled the hourly routine.
Profile and Routine Setup
| Component | Status | Details |
|---|---|---|
| Profile | Created | summarizer-bot (cloned from default) |
| Skill Audit | Cleaned | Non-role skills moved to .archive/ |
| Cron Job ID | crn_8829_x | Scheduled: 0 * * * * |
| Workdir | ~/hermes/logs | Target for summary processing |
| Delivery | bot-chat | Reports directed to summarizer-bot's chat |
# Verification commands executed:
hermes profile list
hermes -p summarizer-bot config get platform_toolsets.cli
hermes -p summarizer-bot cron status
I have verified that the SOUL.md is initialized with a summarization persona. The job is currently
paused as per safety rules.
Next steps
- Review the generated
SOUL.mdin thesummarizer-botdirectory to confirm summary formatting rules. - Run
hermes -p summarizer-bot cron resume crn_8829_xto activate the schedule. - Check the
bot-chatin 60 minutes for the first automated report.
Connects securely to your tools. The creator never sees your data.
About this skill
Managing a fleet of Hermes bots and routines manually is a recipe for silent failures and memory collisions. This skill provides a scriptable framework for orchestrating multiple profiles, ensuring each agent owns its specific job, schedule, and state without polluting the main conversation or leaking credentials.
What it does
- Multi-profile orchestration manages the creation, cloning, and auditing of isolated Hermes bot profiles.
- Routine scheduling configures profile-owned cron jobs with specific workdirs, delivery targets, and delivery grammars.
- Telegram gateway routing handles complex messaging layouts, including shared bot accounts or dedicated private chats via
gateway.profile_routes. - State persistence implements deterministic JSON or SQLite state tracking to maintain workflow progress across memoryless cron turns.
- Fleet auditing performs read-only inspections of prompts versus real schedules, model routing, and inherited skill bloat.
How it works
- Discovery involves running
hermes profile listand inspectinggateway.profile_routesto map the current bot environment. - Construction uses
hermes profile createwith specific flags to clone configurations while stripping unnecessary inherited skills and credentials. - Configuration applies role-specific rules via
SOUL.mdand restricts toolsets at the surface level to enforce least privilege. - Validation executes background cron runs and verifies results through independent file-system or database checks rather than relying on agent self-reporting.
Frameworks & tools
The skill operates via the Hermes CLI and manages profile environments on Linux and macOS. It interacts with state.db via SQLite and configures platform settings through hermes_cli Python modules.
Why this beats prompting it yourself
Generic prompts often fail to account for the specific CLI exit codes and positional argument quirks of the Hermes cron system. This skill ensures that bot routines are registered in the correct profile stores rather than the default store, preventing roles from running without their intended SOUL rules.
Use cases
- Deploying a watchdog bot that audits production logs and reports to a shared Telegram thread.
- Setting up a specialized research agent with its own persistent state file and isolated toolset.
- Pausing all active fleet workflows and saving a resume manifest before a system update.
- Troubleshooting Telegram routing failures where messages aren't reaching the intended profile.
Known limitations
Requires Hermes CLI installed on Linux or macOS. Telegram pairing involves a 30-minute expiry window for deep links. Cron jobs on suspended hardware fire immediately upon wake.
Requires Hermes CLI on Linux/macOS. 30-minute expiry on Telegram pairing links. Cron jobs fire immediately upon hardware wake. Does not support raw JSON edits for cron pausing.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 7 days ago
Requires