hermes bot fleets

    1

    Orchestrate Hermes bot fleets with isolated profiles, profile-owned cron routines, and Telegram gateway routing.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    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

    ComponentStatusDetails
    ProfileCreatedsummarizer-bot (cloned from default)
    Skill AuditCleanedNon-role skills moved to .archive/
    Cron Job IDcrn_8829_xScheduled: 0 * * * *
    Workdir~/hermes/logsTarget for summary processing
    Deliverybot-chatReports 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

    1. Review the generated SOUL.md in the summarizer-bot directory to confirm summary formatting rules.
    2. Run hermes -p summarizer-bot cron resume crn_8829_x to activate the schedule.
    3. Check the bot-chat in 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

    1. Discovery involves running hermes profile list and inspecting gateway.profile_routes to map the current bot environment.
    2. Construction uses hermes profile create with specific flags to clone configurations while stripping unnecessary inherited skills and credentials.
    3. Configuration applies role-specific rules via SOUL.md and restricts toolsets at the surface level to enforce least privilege.
    4. 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.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.

    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. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    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

    Software
    Git

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files
    Environment Variables
    Listed7 days ago

    What's inside

    Frequently Asked Questions

    It automates the orchestration of multiple Hermes profiles, preventing memory collisions and 'silent failures' by ensuring every bot has its own isolated environment, cron schedule, and state tracking.

    This skill is designed for environments running the Hermes CLI on Linux or macOS, and it specifically integrates with Telegram via the hermes_cli Python modules and gateway routing.

    You receive a scriptable framework for profile management, specialized cron configuration tools, Telegram gateway routing templates, and deterministic state-tracking modules.

    Yes, the skill includes tools to audit prompts against real schedules and perform read-only inspections of model routing to identify inherited 'skill bloat' across your fleet.

    Unlike manual prompting, this skill accounts for Hermes-specific CLI exit codes and positional arguments, ensuring routines are registered to the correct profile stores rather than the default store.

    Telegram pairing via the gateway involves a 30-minute expiry window for deep links, and cron jobs on suspended hardware will trigger immediately upon the system waking up.

    New in Agents & Orchestration