sync-setup
Skill26 starsChanged 8 months agoMITView on GitHub
Use when the user wants to set up config sync for the first time, connect to GitHub, or re-initialize the backup repo. Trigger with /sync-setup.
- Installs packages
In this repository5 other files it gives its agents.
- sync-configSkill
- sync-profilesSkill
- sync-pullSkill
- sync-pushSkill
- sync-statusSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Run the documented script and check its result.
- Distinctive: line 36
Run the setup script. Parse user arguments for custom repo name and profile:
- Distinctive: line 58
Run the first push automatically:
- Distinctive: line 83
Read the README for installation, shared layers, and supported configuration paths.
- Distinctive: line 84
Read the privacy policy for backup storage and credential handling.
- Distinctive: line 85
Read the changelog for changes affecting installed versions.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Config Sync Setup
Overview
Initialize a private GitHub repository for backing up Claude Code configuration and perform the first push. Use this skill for a new installation or an existing backup repository. A successful setup gives later push, pull, status, and profile commands their saved repository context.
Prerequisites
Install Claudebase, Bash, jq, Git, and GitHub CLI. Authenticate GitHub CLI before repository creation. The account needs permission to create the requested private repository or access an existing one. Choose the project directory whose configuration should be backed up.
Setup sequence
- Verifies
ghCLI is installed and authenticated - Creates a private GitHub repo for config storage (or connects to existing)
- Initializes the repo structure with a default profile
- Performs the first push of your current Claude Code config
Instructions
- Parse the requested arguments and select the appropriate options below.
- Run the documented script and check its result.
Run the setup script. Parse user arguments for custom repo name and profile:
- First argument (if provided): repo name (default:
claude-config) - Second argument (if provided): initial profile name (default:
default)
bash ${CLAUDE_PLUGIN_ROOT}/scripts/ensure-repo.sh REPO_NAME PROFILE_NAMEReplace REPO_NAME and PROFILE_NAME with the user's values or defaults.
If gh is not installed
Guide the user to install it:
- macOS:
brew install gh - Linux:
sudo apt install ghorsudo dnf install gh - Windows:
winget install --id GitHub.cli
Then authenticate: gh auth login
After setup succeeds
Run the first push automatically:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/sync-push.sh --profile PROFILE_NAMETell the user what was synced and show all available commands: /sync-push, /sync-pull, /sync-status, /sync-profiles, /sync-config.
Output
Report the repository selected or created, the initial profile, and the first push result. Verify setup succeeded before starting the first push. If setup succeeds but the push fails, distinguish those outcomes and explain how to retry the backup with /sync-push.
Error Handling
Troubleshoot missing GitHub CLI with the installation commands in Instructions, and follow its authentication guidance when access fails. Report repository creation or clone errors rather than claiming setup completed. If the first push flags secrets, identify the files for review without including secret values.
Examples
/sync-setup
/sync-setup claude-config workResources
- Read the README for installation, shared layers, and supported configuration paths.
- Read the privacy policy for backup storage and credential handling.
- Read the changelog for changes affecting installed versions.
User Arguments
Interpret the following input as arguments for the documented operation:
$ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

