m4-mac-team-clone-sync

Clone and synchronize a Hermes agent team from OVH to a local Mac.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill m4-mac-team-clone-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m4-mac-team-clone-sync
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/m4-mac-team-clone-sync
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill m4-mac-team-clone-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about m4-mac-team-clone-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clone a Hermes agent team from a remote server to a local Mac?

To clone a Hermes agent team to a local Mac, you copy the profile layout, configure sandbox paths, and set up launchctl plists. This process mirrors the OVH server stack while preserving configuration and shared knowledge on Apple Silicon.

What's the best way to sync Obsidian vault content and Hermes configuration across machines?

The best way to sync Hermes configuration and Obsidian vaults is using bidirectional git and rsync workflows. This keeps shared knowledge aligned across machines while excluding volatile session state like sessions/state.db to prevent sync conflicts.

Can I use rsync to transfer Hermes profiles without breaking SSH transfers?

Yes, you can use rsync to transfer Hermes profiles, but you must configure exclusions carefully. Applying operational guardrails prevents breaking SSH transfers with oversized caches and avoids using invalid HERMES_HOME paths during synchronization.

How do I set up Slack coordination for a multi-agent Hermes team?

To set up Slack coordination for a Hermes team, you provision Slack app manifests, configure channels, and define bot scopes. This enables cross-team and war-room coordination for agents operating across different machines.

What should I exclude when synchronizing Hermes state between OVH and a local Mac?

When synchronizing Hermes state between OVH and a Mac, you should exclude volatile session state like sessions/state.db. This prevents local deployment issues and ensures only configuration and git-backed knowledge are synced.