agentleFS
rohithzrrohithzr/claudebase/skills/sync-profiles/SKILL.md

sync-profiles

Skill26 starsChanged 8 months agoMITView on GitHub

Use when the user wants to list, create, switch, delete, compare, or inspect config sync profiles. Trigger with /sync-profiles.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the appropriate command above and check its result.

    line 70
  2. Very specific:

    If the user says "switch" to a profile, use the pull script with --profile rather than the profile-manager (since switching = pulling a …

    line 72
  3. Very specific:

    If no action is specified, default to list.

    line 74
  4. Distinctive:

    Read the README for installation, shared layers, and supported configuration paths.

    line 93
  5. Distinctive:

    Read the privacy policy for backup storage and credential handling.

    line 94
  6. Distinctive:

    Read the changelog for changes affecting installed versions.

    line 95

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Config Sync Profiles

Overview

Manage separate work, personal, and team configurations in the same private GitHub backup repository. Use profiles to inspect or compare saved setups, create a starting configuration, or restore a different profile onto this machine.

Prerequisites

Install and initialize Claudebase first. Bash, jq, Git, and an authenticated GitHub CLI are required. The requested profile must exist for inspection or switching. Review local changes before switching because a switch applies the selected profile to this machine.

Available actions

List profiles

bash ${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh list

Shows all profiles with file counts, last push time, and which is active.

Create a profile

# Empty profile
bash ${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh create NAME

# Clone from existing profile
bash ${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh create NAME --from EXISTING

Creates a new profile. Use --from to clone an existing profile as a starting point.

Switch to a profile

Switching means pulling a different profile's config:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/sync-pull.sh --profile NAME

This backs up current config, then applies the target profile. The active profile is updated automatically.

Delete a profile

bash ${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh delete NAME

Cannot delete the active profile. Switch to a different one first.

Compare two profiles

bash ${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh diff NAME1 NAME2

Shows files that exist in only one profile or differ between them.

Profile info

bash ${CLAUDE_PLUGIN_ROOT}/scripts/profile-manager.sh info NAME

Shows metadata and contents of a specific profile.

Instructions

  1. Parse the user's action from $ARGUMENTS and identify the target profile.
  2. Run the appropriate command above and check its result.

If the user says "switch" to a profile, use the pull script with --profile rather than the profile-manager (since switching = pulling a different profile).

If no action is specified, default to list.

Output

Report profile names and the active profile for listing. Creation and deletion return the script result. Comparison identifies differing or missing files. Switching reports the applied profile, file counts, backup location, and validation warnings returned by the pull script.

Error Handling

Troubleshoot missing profiles with list before retrying. The active profile cannot be deleted; switch to another profile first. If GitHub authentication or repository access fails, report that failure and ask the user to restore access before repeating the operation.

Examples

/sync-profiles list
/sync-profiles create work --from default

Resources

  • 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.