What problem does it solve?
This Skill solves the operational gap between a Hermes team running on an OVH server and a cloned team running locally on a Mac, preserving knowledge, configuration, and coordination without syncing volatile session state.
Core Features & Use Cases
- Mac Team Bootstrap: Clone a multi-agent Hermes team onto Apple Silicon Macs with the correct profile layout, sandbox paths, and launchctl setup.
- Bidirectional Knowledge Sync: Keep Obsidian vault content and Hermes configuration synchronized through git and rsync-based workflows.
- Slack Coordination Setup: Provision Slack app manifests, channels, and bot scopes for cross-team and war-room coordination.
- Operational Guardrails: Prevent common failure modes such as syncing sessions/state.db, using invalid HERMES_HOME paths, or breaking SSH transfers with oversized caches.
- Use Case: A team lead wants to recreate the OVH agent stack on a MacBook M4, keep docs and config aligned, and avoid the permission and sync issues that typically break local Hermes deployments.
Quick Start
Ask for a Mac team clone plan that copies the OVH Hermes setup, configures safe bidirectional sync, and prepares the required Slack and launchctl environment.