What problem does it solve?
This Skill solves the operational chaos of running multiple Hermes agent teams on the same server by giving each team isolated profiles, state, credentials, and process management. It reduces context leakage, duplicate work, identity confusion, and deployment mistakes across teams.
Core Features & Use Cases
- Profile isolation: Separate each agent’s HERMES_HOME so sessions, memory, skills, and runtime state do not collide.
- Multi-number WhatsApp setup: Run distinct WhatsApp bridges per team or anchor agent with separate ports and session paths.
- Process orchestration: Deploy agents through PM2 or systemd with startup, restart, logging, and hardening guidance.
- Operational troubleshooting: Handle common pitfalls like token masking, memory contamination, path confusion, and timeout mismatches.
- Use case: A team lead can provision a second Hermes team on the same server, connect one agent to WhatsApp, delegate work to Slack-only specialists, and keep the environments separated.
Quick Start
Ask for a step-by-step plan to create an isolated Hermes team with separate profiles, WhatsApp bridging, and systemd or PM2 deployment.