Automated summary
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
How this analysis is madeExamples
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/bidirectional-sync-mm5t8apw/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/bidirectional-sync-mm5t8apw' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/bidirectional-sync-mm5t8apw/download' --output '.skill-downloads/bidirectional-sync-mm5t8apw/SKILL.md.part' && mv '.skill-downloads/bidirectional-sync-mm5t8apw/SKILL.md.part' '.skill-downloads/bidirectional-sync-mm5t8apw/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/bidirectional-sync-mm5t8apw/SKILL.md' && test -s '.skill-downloads/bidirectional-sync-mm5t8apw/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/sync' && cp -R '.skill-downloads/bidirectional-sync-mm5t8apw' '.claude/skills/sync'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/bidirectional-sync-mm5t8apw'openskills read 'bidirectional-sync-mm5t8apw'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/bidirectional-sync-mm5t8apw/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.