agent-synclisted

# Driving agent-sync The user keeps one canonical library of skills and MCP servers, versioned in git, and agent-sync projects it into every agent on every device they own. This skill covers running it. To *create* things, use `agent-sync-create-skill` or `agent-sync-add-mcp`. Every command takes `--json` and returns a stable, versioned envelope. Prefer it — branch on the data, not on prose. ## Exit codes are the contract | Code | Meaning | What to do | |---|---|---| | 0 | done | report it | | 1 | error | read the message; do not retry blindly | | 2 | done, with warnings | report the warnings — something could not be fully honoured | | 3 | needs a decision | **ask the user**; never choose for them | ## Where things stand ``` agent-sync status --json ``` A matrix of every artifact against every agent. `synced` is converged, `outdated` means the library moved on, `drifted` means the deployed copy was edited by hand, `conflicted` means both sides changed, `collision` means something unmanaged is already sitting in that spot, `excluded` means routing deliberately sends it elsewhere, and `missing` means it should be there and is not. An asterisk in the human output means one copy is serving several agents that read the same directory — that is intended, not a bug. `agent-sync status --why` explains which rule produced each deployment, which is the answer to "why does Cursor not have this?". ## The daily loop ``` agent-sync sync ``` Pull, apply, push. Run it when the use