sync-private-skills

To reconcile private skills drift, you need a controlled sync process that compares directories like ~/.claude/skills and ~/.gemini/config/skills/, shows file diffs, and applies changes only after explicit user confirmation.

The safest way to sync configuration files across multiple agent directories is a manual-controlled merge that displays a diff of proposed changes and requires explicit confirmation before copying any files to prevent unwanted overwrites.

A last-sync manifest records the state of synchronized files at the time of the last merge, providing a baseline snapshot to compare against during future audits to quickly identify new configuration drift.

No, this synchronization process requires explicit user confirmation before any cross-home copy occurs, ensuring you review the proposed diff and maintain manual control over all merges to prevent accidental data loss.

You need to synchronize skill folders when you detect drift between your authored skills in separate homes, which happens when files in ~/.claude/skills, ~/.agents/skills, or ~/.gemini/config/skills/ are edited independently.

The best way to audit skills and resolve drift is to first run an audit process to identify the discrepancies, then review the proposed synchronization plan and confirm the diffs before executing the file copy.