Stop Manually Copying Skills: A Unified Management Solution for Multi‑Agent Environments

Current AI coding tools are diverse; developers often run several agents such as Codex, Claude Code, Cursor, Qoder, etc. Each agent keeps its own copy of a Skill, so the same Skill ends up in multiple locations and quickly becomes inconsistent.

Community attempts like Git submodule, monorepo, Syncthing, or Prompt‑management platforms either require heavy commit/push/pull workflows or cannot understand Skill semantics, leaving the core problem of automatic distribution unsolved.

Nacos Skill Sync fills this gap by converging all Skills into a single central repository and distributing them to agents on demand. It provides two operating modes:

Registry mode : Uses Nacos AI Registry as a unified entry point, offering visual management, version governance (draft, review, publish, rollback, label), cross‑device sharing, and bidirectional flow.

Local mode : A lightweight alternative that builds a local central repository and links each agent’s Skill directory via symlinks (or copy mode when symlinks are unavailable), requiring no server setup.

The core workflow is:

Maintain one central repository for all Skill content and sync status.

Default to symlinks so a change in one place instantly affects every linked agent; switch to copy mode if the environment does not support symlinks.

Sync status is always visible, showing whether the remote Registry has updates, whether there are local modifications, and whether conflicts exist.

Registry mode adds concrete capabilities:

Visual browsing, searching, and viewing of Skills in the Nacos console.

Version governance with drafts, reviews, publishing, rollback, and labeling, enabling individuals to track Skill states and teams to stabilize high‑frequency Skills.

Cross‑device synchronization so a Skill added on a home computer automatically appears on a work computer.

Bidirectional flow: remote changes can be pulled locally, and local refinements can be pushed back to the Registry.

Local mode focuses on simplicity. It discovers agents such as Codex, Claude, Qoder, Cursor, Kiro, Lingma, etc., and aggregates their Skill directories (e.g., ~/.agents/skills or ~/.skills) into the central repo. When the same Skill exists in multiple agents, Local mode collapses them into a single source of truth, ensuring that editing the Skill in one agent propagates to all others.

CLI commands illustrate both modes. Adding a Skill: skill-sync add <skill> Adding all existing Skills: skill-sync add --all Removing a Skill: skill-sync remove <skill> Removing all syncs: skill-sync remove --all Registry mode setup (profile‑based):

# Install CLI
curl -fsSL https://nacos.io/nacos-installer.sh | bash -s -- --cli
# Or use npx
npx @nacos-group/cli@latest skill-sync --help

# Configure profile
npx @nacos-group/cli@latest profile edit test

# Add Skill and start sync
npx @nacos-group/cli@latest --profile test skill-sync add pdf
npx @nacos-group/cli@latest --profile test skill-sync start
npx @nacos-group/cli@latest --profile test skill-sync status

Local mode (no profile needed):

npx @nacos-group/cli skill-sync add pdf
npx @nacos-group/cli skill-sync start
npx @nacos-group/cli skill-sync status

Two concrete use cases demonstrate the workflow. Case 1 – Work‑Report Skill : A developer records daily tasks in various agents, then aggregates them into a weekly report. By placing the biweekly-work-report Skill in Local mode, all agents share the same source. Updating the Skill in Codex instantly updates Claude, Cursor, and others, and the final report remains consistent. Case 2 – Document‑Format Skill : Teams often produce API docs, design specs, and post‑mortems with divergent templates. Storing the doc-format Skill in Registry mode lets the whole team edit a single version, synchronizing the format across all devices and agents. Daily maintenance reduces to checking a concise status table, for example:

Mode: nacos
Profile: team
Sync daemon: running (pid: 12345)
SKILL   STATUS        AGENTS                NEXT
pdf     Synced        codex,claude,qoder    -
review  Local changes codex,claude,qoder    auto‑upload pending
draft   Uploaded      codex,claude,qoder    waiting publish
block   Upload blocked codex,claude,qoder   Nacos draft exists; review/clear it, auto‑upload will retry
triage  Conflict      codex,claude,qoder    skill‑sync resolve triage

The table explains each Skill’s state, which agents are affected, and the next action. Conflict resolution is handled conservatively via the resolve command, letting the user explicitly choose the source (remote Registry, central repo, or a specific agent). In summary, whether starting with the lightweight Local mode or moving to the collaborative Registry mode, the goal is the same: give each Skill a trustworthy, single source so that agents can be swapped without scattering the Skill definitions. Images illustrating the architecture and UI are retained below:

Related links: Nacos source code (github.com/alibaba/nacos), Nacos CLI (https://github.com/nacos-group/nacos-cli), and the Nacos Skill Sync documentation (https://nacos.io/skill-sync/SKILL.md).