Jelly Skill Sync
Synchronizes Claude Code skills bidirectionally between local project repositories and the global user directory using automated conflict detection and timestamp analysis.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Bidirectional synchronization between project repositories and ~/.claude/skills/
- Prefix-based safety filtering to manage specific skill sets without affecting system defaults
- Selective synchronization for individual skills or full directory batch updates
- Timestamp-based conflict detection to identify newer versions in both locations
- Dry-run sync analysis with detailed status reporting and action previews
Use cases
- Synchronizing skill updates and bug fixes across different development workstations
- Deploying newly developed skills from a version-controlled repository to the global Claude environment
- Backing up manually modified global skills into a project repository for git tracking
FAQ
What is the Jelly Skill Sync Claude Code skill?
Jelly Skill Sync is a specialized tool for Claude Code that synchronizes custom AI skills between your local project's repository and the global Claude skills directory (~/.claude/skills/). It ensures your custom capabilities are available across all environments.
How does it handle version conflicts during synchronization?
The skill uses timestamp-based analysis to identify which version of a skill is newer. It provides a detailed dry-run preview, showing you exactly which files will be pushed to the global directory or pulled back into your project before any changes occur.
Can I synchronize a single specific skill instead of everything?
Absolutely. Jelly Skill Sync supports selective synchronization, allowing you to target a single directory. This is ideal for testing updates on a specific capability without affecting your entire skill library.
Is it safe to use with my default Claude Code skills?
Yes. Jelly Skill Sync is designed with a safety-first approach, specifically targeting skills with the 'jelly-*' prefix. This ensures it won't interfere with or accidentally overwrite your system-default Claude skills or other third-party integrations.
When should I use the 'push' vs. 'pull' commands?
Use 'push' when you have developed or improved a skill within a specific project and want to make it globally available to Claude. Use 'pull' when you have modified a skill in your global directory and want to save those updates back into your project's version control.