Skip to content
Skills Library
Personal productivity · Automation

agentsync

/agentsync

Set up and run AgentSync syncs for the user — copy files, folders, skills, MCP configs or instruction files (AGENTS.md, CLAUDE.md, GEMINI.md) to several places and computers, subscribe to shared repositories, and resolve sync conflicts. Use when the user asks to sync, share, copy or keep in sync agent configuration or any files between folders or PCs, or mentions AgentSync.

Repository
Agent-Sync ↗
Licence
MIT
Last repository change
10.11.2026

Assessment and security

98/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene13 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Set up and run AgentSync syncs for the user — copy files, folders, skills, MCP configs or instruction files (AGENTS.md, CLAUDE.md, GEMINI.md) to several places and computers, subscribe to shared repositories, and resolve sync conflicts. Use when the user asks to sync, share, copy or keep in sync agent configuration or any files between folders or PCs, or mentions AgentSync.

Original author description

Set up and run AgentSync syncs for the user — copy files, folders, skills, MCP configs or instruction files (AGENTS.md, CLAUDE.md, GEMINI.md) to several places and computers, subscribe to shared repositories, and resolve sync conflicts. Use when the user asks to sync, share, copy or keep in sync agent configuration or any files between folders or PCs, or mentions AgentSync.

How it works

  1. Concepts
  2. Edit existing configuration
  3. Workflow
  4. Examples
  5. Backups
  6. Safety
  7. Setup (if the tools are missing)
Original SKILL.md headings · 136 lines, 1,289 words
SKILL.md preview
---
name: agentsync
description: Set up and run AgentSync syncs for the user — copy files, folders, skills, MCP configs or instruction files (AGENTS.md, CLAUDE.md, GEMINI.md) to several places and computers, subscribe to shared repositories, and resolve sync conflicts. Use when the user asks to sync, share, copy or keep in sync agent configuration or any files between folders or PCs, or mentions AgentSync.
---

# AgentSync

AgentSync keeps files in sync from one source (a git repository, a folder on this PC or a
subscribed repository) to many destinations, each with its own name. Work through its **MCP
server** (tools such as `status`, `add_rule`, `sync`) when it is connected; otherwise use the
**CLI** `agentsync-cli` with `--json`. Both use the same configuration as the desktop app.

## Concepts

- **Rule**: one source → one or more destinations. Each destination has a location, a path or
  final name (`CLAUDE.md`, `GEMINI.md`, `skills/review`) and a mode:
  `two_way` (default, edits flow both ways), `one_way` (source wins) or `create_only`.
- **Source origin**: `repo` (path relative to the repository root, shared with every PC),
  `local` (absolute path on this PC, rule stored locally) or `subscription` (local clone of a shared repo; edits are never pushed).
- **Selection**: a folder source plus `include` (list of files relative to it) syncs only those
  files. Use `sourcePath: "."` for files at the repository root.
- **Location**: alias for a folder on this PC (`claude` → `C:\Users\me\.claude`). Rules use aliases so
  they work on every computer. `home` initially points to the user folder and can be removed or remapped.
- **Transform**: `json_merge:<key>` / `toml_merge:<key>` merges only AgentSync's MCP entries into an
  agent config file and keeps the rest.

Rules support `categoryId`; categories organize presentation and do not change sync behavior.
Use `list_categories` / `save_category` / `suggest_category` (CLI `categories list/save/suggest`) to
manage them. `delete_category` and `migrate_categories` require user approval and `confirm:true`.
Older AgentSync clients can remove category fields when rewriting rules files, so use a current client
when modifying categorized rules.

## Edit existing configuration

- Keep IDs and sync baselines: use `update_rule {ruleId,patch}` and
  `update_destination {ruleId,destinationId,patch}` instead of deleting/recreating. CLI:
  `rules update ID --input FILE|-` / `destinations update RULE DEST --input FILE|-`; input is only the patch.
  Omitted/null fields preserve values; `false` disables, `[]` clears lists. Rule patches accept
  `scope`, `name`, `categoryId`, `enabled`, `origin`, `subscription`, `sourcePath`, `include`, `kind`, `exclude`.
  Destination patches accept `location`, `path`, `mode`, `enabled`, `ignore`, `transform`, `clearTransform`.
  To remove a transform use `clearTransform:true` without `transform`; the mode stays unchanged.
- Read configured files with `list_file_roots`, `list_file_directory`, `read_file`. To `save_file`,
  pass the exact `hash` and `absolutePath` from the read as `expectedHash` and `expectedPath`.
  A stale file/root is refused; reread and ask about competing edits. CLI: `files roots/list/read/save`.
- `list_rule_source_files`, `read_rule_source_file`, `save_rule_source_file` work within a rule's
  selected sources. Saves require `expectedHash`; subscription rule sources are read-only.
  CLI: `rules files/read-file/save-file`. Local subscription clone edits are explicit browser saves.
- `import_into_repo` (CLI `repo import SOURCE --dir REL`) copies a source without creating a rule or
  overwriting existing targets. `subscription_file_diff` (CLI `subscriptions diff ID PATH`) previews
  the last fetched update; call `check_subscription` first for fresh data.

## Workflow

1. **Check state** — `status` (CLI: `agentsync-cli status --json`). If no root is set, ask the user
   for their configuration repository folder and call `set_root`.
2. **Locations** — `list_locations`. If a needed alias is missing, ask for the folder (or propose the
   usual one, e.g. `%USERPROFILE%\.claude`) and call `set_location`.
3. **Understand the source** — `detect_source` and, per destination, `suggest_placement`. AgentSync
   recognizes skills, MCP configs and instruction files and proposes the right path and name.
   Omit a destination `path` to accept the suggestion.
4. **Create the rule** — `add_rule` with the source and destinations. Report any `collisions` in the
   result: colliding destinations are paused until the user changes a path or disables one.
5. **Apply** — `sync_rules` writes rule destinations only (backups first). For a full sync with git
   (pull, commit, push) call `plan_sync`, show the user the plan, then `sync` with its `fingerprint`.
   If the plan lists `conflicts` (a repository file edited here and on the remote), ask which version
   to keep and pass `resolutions` `{path, resolution: keep_repo | keep_local}` (CLI:
   `--resolve PATH=keep_repo|keep_local`); the discarded or set-aside local version is backed up.
6. **Review** — `list_rules` / `get_rule` show per-file status; use `rule_diff` and
   `resolve_rule_file` for conflicts after asking the user which version to keep.

## Examples

| User says | Do |
|---|---|
| "Use my AGENTS.md as CLAUDE.md and GEMINI.md" | `add_rule` source `AGENTS.md`, destinations `claude:CLAUDE.md`, `gemini:GEMINI.md`; then `sync_rules` |
| "Share the review skill with Claude and Codex" | `add_rule` source `skills/review`, destinations `claude`, `codex` (no path → suggested); `sync_rules` |
| "Copy only these 3 notes to my Obsidian vault" | `set_location obsidian <vault>`; `add_rule` source `notes` + `include: [a.md, b.md, c.md]`, origin as needed |
| "Subscribe to github.com/acme/skills and take its pdf skill" | `add_subscription`; `list_subscription_tree`; `add_rule` origin `subscription`, source `skills/pdf` |
| "What does this subscription suggest?" | `list_subscription_suggestions`; show each source and target path; after the user accepts, `apply_subscription_suggestions` (`confirm: true`, `locations` for unmapped aliases), then `sync_rules` |
| "Publish my subscription rules as suggestions" | `export_subscription_suggestions` (CLI: `suggestions export --subscription ID --output agentsync.suggestions.json`) |
| "What is pending?" | `status`, then `list_repo_changes` / `repo_file_diff` |

CLI equivalents:

```bash
agentsync-cli locations set claude "$USERPROFILE/.claude" --json
agentsync-cli rules add --source skills/review --to claude --to codex --json
agentsync-cli rules add --source notes --include a.md --include b.md --to obsidian:inbox --json
agentsync-cli sync --rules-only --json
agentsync-cli suggestions list --subscription s_abc --json
agentsync-cli suggestions apply --subscription s_abc --id 3f9a1c2b7d10 --map codex="$USERPROFILE/.codex" --json
```

## Backups

Sync overwrites/deletions, discards and restores are backed up first. Direct editor saves use
concurrency checks, not backup snapshots. To recover a file, `list_backups` (CLI `backups list`)
shows them newest first with the rule, destination, date, reason and files; `restore_backup` (CLI
`backups restore <id> [--file F]... --yes`) puts all or some files back after the user agrees. The
current files are backed up first (`undoBackupId`), so a restore can itself be undone. A restored
destination file differs from its source, so it appears in `status` / `list_rules` as a difference to
review (`untracked_diff`): `sync_rules` skips it until the user resolves it with `resolve_rule_file`.

## Safety

- Subscription updates are blocked by local changes; removal is blocked by local files, commits or
  stashes. Preserve those changes outside the clone before cleaning it.

- Suggested rules come from the repository owner (a third party). Never apply them unasked: list
  them, show the user each source and the resolved target path, apply only the ones they accept, and
  confirm folders for unmapped locations with them. Applying creates rules only; a sync copies files.
- Destructive tools (`delete_rule`, `remove_destination`, `remove_subscription`,
  `discard_repo_file`, `save_gitignore`, `restore_backup`) require `confirm: true` (CLI: `--yes`). Ask the user first,
  in plain words, and only then confirm.
- Never put secrets in a synced source. Secret files (`.env`, `*.pem`, `auth.json`, ...) are always
  excluded; use `exclude_repo_path` to keep other files out of the repository.
- Prefer `sync_rules` for local changes; only run a full `sync` (which pushes) when the user asked to
  share or upload.
- `add_remote` also pushes the current branch and requires `confirm: true` (CLI `repo add-remote --yes`).
  Use `connect_remote` instead when attaching a remote while preserving local differences for review.
- `get_settings` / `update_settings` (CLI `settings show` / `settings update --input FILE|-`) read and
  partially update operational preferences. Omitted values are preserved. Do not send desktop-only
  tray/startup/theme fields. There is no headless periodic scheduler: automatic subscription checks
  require the desktop app, and a changed check interval takes effect after restarting it.
- Errors start with a stable code, e.g. `[location_unmapped] {"alias":"codex"}`: fix the cause
  (here, `set_location codex …`) instead of retrying.

## Setup (if the tools are missing)

Download `agentsync-cli.exe` from the AgentSync releases and register it as an MCP server:

```bash
claude mcp add --scope user agentsync -- C:\Tools\agentsync-cli.exe mcp
```

Codex (`~/.codex/config.toml`): `[mcp_servers.agentsync]` with `command` and `args = ["mcp"]`.
Gemini CLI (`~/.gemini/settings.json`): `mcpServers.agentsync` with the same command and args.

Rules may share a destination folder when they manage different files. MCP merge rules may share a configuration file when their managed entry names are distinct; overlapping entries remain blocked.

Versions

The database has no other skills named agentsync.

Database snapshot: 13.11.2026 · package version e0804c6b197f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100foragent-call
    Connect two AI agents by private phone number so they can talk to each other and share files across computers or teammates. Use when the user asks to call another agent, let two Claude Code or Codex sessions talk directly, share a file between agents on different machines, or…
  • 95onboard
    Use when setting up an AI workspace in Claude Cowork, running guided onboarding, or building a personal workspace (AGENTS.md instructions, a CLAUDE.md pointer, context files, and working folders that match the person's job) for a connected folder
  • 100resolve-conflicts
    Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration),…
  • 100setup-shared-folder
    Set up a private GitHub repo for syncing files between GhostClaw (Mac mini) and user's main machine (MacBook Air, etc). Use when user wants to share files across machines without Dropbox/iCloud.
  • 100port-to-codex
    Ports a project's Claude Code setup (CLAUDE.md, skills, agents, MCP, hooks) to Codex: AGENTS.md becomes the shared instruction file with CLAUDE.md as a symlink to it, and Codex's .agents/skills/ and .codex/ are generated from .claude/ and .mcp.json with rulesync. Use when the…
  • 90writing-for-agents
    Use when creating or editing skills, or modifying AGENTS.md or other agent instruction files.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.