Our review
Bidirectionally synchronizes project and template configurations by running template-updater then project-updater.
Strengths
- Maintains consistency between projects and templates
- Prevents loss of local improvements through correct order
- Automates file copies and commits
Limitations
- Relies on template-updater and project-updater sub-skills
- Depends on 'but' tool for commits
- Does not handle merge conflicts automatically
Use at session start or after improving shared skills/rules to keep project and template aligned.
Avoid if working alone without need for centralized template synchronization.
Security analysis
CautionThe skill orchestrates a bidirectional sync workflow using Bash and other skills that involve file operations and version control. While the tools are powerful, the instructions themselves do not perform destructive actions or exfiltration. The risk is managed by requiring user interaction (AskUserQuestion) and relying on documented skill scripts. Caution is warranted due to the use of Bash, but the skill appears legitimate.
No concerns found
Examples
Run sync skill to get latest template updates into my project.I've updated some shared rules in my project, run sync to push them to the template.name: sync description: > Synchronize project and template configurations bidirectionally. Runs template-updater then project-updater in correct order. Use when syncing changes between project .claude/ and ~/.claude/template/. allowed-tools: [Bash, Read, Write, AskUserQuestion]
Sync
Bidirectional sync between project .claude/ and ~/.claude/template/.
Why Order Matters
- template-updater first - Push local improvements to template
- project-updater second - Pull template updates to project
Running in wrong order would overwrite local improvements before they're pushed.
Workflow
- Use the Skill tool to invoke
/template-updater- this loads the skill with the correct script path - Handle any file copies needed
- Use the Skill tool to invoke
/project-updater- this loads the skill with the correct script path - Handle any file copies needed
- Summarize what changed
Do NOT guess script paths. Each skill's SKILL.md documents its own script.
After Sync
If any files were copied, commit the changes:
Project changes:
but status
but commit <branch> --only -m "chore: sync claude config from template"
Template changes:
cd ~/.claude && but status
but commit <branch> --only -m "chore: update template from project"
When to Use
- At session start (get latest template updates)
- After improving shared skills/rules (push to template)
- Periodically to keep project and template aligned
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.