What problem does it solve? Operating the Hermes Agent framework involves a dense set of non-obvious contracts — a script-only install, a strict secrets-vs-config split, a 64k-token model context floor, profile isolation rules, and safety rails that shift between terminal backends — and getting any of them wrong breaks the agent or leaks credentials. ## Core Features & Use Cases - Full lifecycle playbook: Six phased guides covering install/operate, config/profiles/secrets/egress, skills/memory/context, automation/gateway/serving, providers/MCP/Python library, and extending the framework with plugins and tools. - Read-only triage scripts: Three bash scripts audit the install and config split, inventory profiles/skills/cron/MCP/plugins/memory, and probe the dashboard (9119), API server (8642), gateway, and iron-proxy egress status without mutating anything. - Use Case: You want to run a scheduled nightly backlog triage agent on Telegram. Use this Skill to create an isolated profile, configure cron with delivery targets, wire the messaging gateway with default-deny authorization, and verify everything with the surface probe script. ## Quick Start Ask the AI to audit your local Hermes Agent installation and config split using the hermes-env-audit script, then walk you through fixing any warnings.