Feature: Plugin & Complex Skill Synchronization

[Q00]

Summary

Enable centralized synchronization of plugins and complex skill configurations across team members, so admins can push curated skill sets and plugin configurations to users without manual setup.

Motivation

As teams scale, keeping everyone's Claude Code environment consistent becomes a real challenge:

• New team members need to manually discover and configure skills/plugins
• Skill configurations (custom prompts, MCP server settings, hook definitions) drift across team members
• Admins have no way to push updates or deprecate outdated skills org-wide
• Complex skills with multi-file definitions are especially painful to distribute manually

Current State

• Admin can manage skills via /admin/skills (CRUD operations)
• Skill suggestion system exists (/api/skill-suggest, /api/skill-suggestions)
• Hook management exists at /admin/hooks with distribution to agents
• No mechanism for syncing local .claude/ skill files or plugin configs from a central source

Proposed Solution

1. Skill Registry & Version Management

• Central skill registry in Zeude storing skill definitions with versions
• Each skill has: name, version, content (markdown/config), dependencies, changelog
• Admin can publish new versions; users receive update notifications

2. Sync Protocol

• Push model: Admin publishes a skill → Zeude notifies agents at next check-in → agent pulls and applies
• Pull model: Agent periodically checks for updates via /api/skill-sync/check
• API endpoints:
  • GET /api/skill-sync/check — returns list of skills with available updates
  • GET /api/skill-sync/pull/:skillId — returns the latest skill definition
  • POST /api/admin/skill-sync/publish — admin publishes a new skill version

3. Skill Bundles

• Group related skills into "bundles" (e.g., "Backend Developer Kit", "QA Toolkit")
• Assign bundles to teams or roles
• New team members automatically receive their team's bundle on first sync

4. Plugin Configuration Sync

• Extend sync to MCP server configurations
• Store plugin configs centrally; distribute via the same sync protocol
• Handle sensitive config (API keys) separately with per-user secret injection

Design Considerations

• Conflict resolution: user-modified skills vs. centrally pushed updates (user override wins? prompt to merge?)
• Backward compatibility: agents running older versions should degrade gracefully
• Offline support: sync should work on next connection, not require always-on

Acceptance Criteria

• Admin can publish and version skill definitions from the dashboard
• Agents receive and apply skill updates automatically or on user approval
• Skill bundles can be assigned to teams
• Plugin/MCP configurations can be synced centrally
• Conflict resolution strategy is documented and implemented