plugins/bridgey-deploy/skills/sync/SKILL.md
Sync agent files between local and remote server. Use when the user says "sync", "push to remote", "pull from remote", "sync agent", or runs /sync.
npx skillsauth add kickinrad/bridgey syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Bidirectional rsync between local agent and remote deployment. Connection details are read from bridgey-deploy.config.json in the agent's root directory.
Read bridgey-deploy.config.json to get:
tailscale_host — the Tailscale hostname of the remote serverremote_path — the path on the remote server (e.g., /opt/bridgey/personas/{name})container_name — the Docker container nameIf bridgey-deploy.config.json doesn't exist, ask the user for the Tailscale hostname and remote path.
/sync push — local -> remote (config, skills, CLAUDE.md changes)/sync pull — remote -> local (memory, outputs, learnings)/sync — bidirectional (push then pull)Push local config/skills/rules to the remote server. Excludes runtime data.
rsync -avz --delete \
--exclude='.git/' \
--exclude='.mcp.json' \
--exclude='*.log' \
--exclude='*.db' \
--exclude='*.db-journal' \
--exclude='user/memory/' \
~/.personas/{name}/ {tailscale_host}:{remote_path}/
After pushing, restart the container to pick up changes:
ssh {tailscale_host} "cd $(dirname {remote_path}) && docker compose restart {container_name}"
Pull memory and outputs from the remote server. Only syncs user/memory/.
rsync -avz \
{tailscale_host}:{remote_path}/user/memory/ \
~/.personas/{name}/user/memory/
Run push then pull in sequence.
.mcp.json is NEVER synced (contains API keys, differs per environment).git/ is never synceduser/memory/ (remote writes there, local pulls it)testing
This skill should be used when the user asks to "set up bridgey", "configure bridgey", "initialize bridgey", "bridgey setup", "check bridgey status", "show bridgey agents", "is bridgey running", "bridgey health", "show connected agents", "add a bridgey agent", "connect to another agent", "register a remote agent", "add remote agent", "configure tailscale for bridgey", "scan tailnet for bridgey", or runs `/bridgey:setup`, `/bridgey:status`, `/bridgey:add-agent`, `/bridgey:tailscale-setup`, `/bridgey:tailscale-scan`. Lifecycle surface for the bridgey A2A daemon — first-time setup, health dashboard, remote-agent registration, and Tailscale mesh discovery.
data-ai
First-time Tailscale mesh network configuration for bridgey. Updates daemon binding for tailnet access and runs initial peer scan.
data-ai
Manually scan the Tailscale network for bridgey agents. Shows discovered, new, and removed agents.
testing
This skill should be used when the user asks to "check bridgey status", "show bridgey agents", "is bridgey running", "bridgey health", "show connected agents", runs "/bridgey:status", or wants to see the state of the bridgey daemon and connected agents.