agentleFS
Sign inStart free
rohithzrrohithzr/claudebase/skills/sync-config/SKILL.md

sync-config

Skill26 starsChanged 8 months agoMITView on GitHub

Use when the user wants to view or change claudebase settings like global sync, agent skills sync, auto-push, or machine ID. Trigger with /sync-config.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Nirusan/claude-config★ 7same name
    2. ztrange/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the documented script and check its result.

    line 27
  2. Distinctive:

    Run the config manager script with the appropriate action:

    line 29
  3. Very specific:

    If setup is missing, direct the user to /sync-setup.

    line 63
  4. Distinctive:

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

    line 74
  5. Distinctive:

    Read the privacy policy for backup storage and credential handling.

    line 75
  6. Distinctive:

    Read the changelog for changes affecting installed versions.

    line 76

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

Overview

Inspect and customize the saved configuration used by Claudebase. Use this skill to control global settings sync, agent skill lock-file sync, automatic pushes, and machine identity without editing plugin state by hand.

Prerequisites

Claudebase must be installed and initialized with /sync-setup. The configuration script requires Bash and jq. Read the current setting before changing it so the user can see the effect of the requested change.

Instructions

  1. Parse the requested arguments and select the appropriate options below.
  2. Run the documented script and check its result.

Run the config manager script with the appropriate action:

bash ${CLAUDE_PLUGIN_ROOT}/scripts/config-manager.sh ACTION [KEY] [VALUE]

Actions

  • show (default) — Display all current settings
  • set <key> <value> — Change a setting
  • get <key> — Read a single setting
  • reset <key> — Remove a setting (revert to default)

Configurable keys

KeyValuesDescription
include_globaltrue/falseSync ~/.claude/settings.json on push/pull
sync_agent_skillstrue/falseSync skills-lock.json (lock file only; prints install commands on pull)
auto_pushtrue/falseAuto-push config when a Claude Code session ends
machine_idany stringIdentifier for this machine (used in multi-machine warnings)

Common actions

  • /sync-config — show all settings
  • /sync-config set include_global true — enable global settings sync
  • /sync-config set auto_push false — disable auto-push

Output

For show, report the repository, active profile, settings, and state locations. For get, return the selected value. For set and reset, report the affected key and the script result; verify changes with the corresponding get action.

Error Handling

If setup is missing, direct the user to /sync-setup. Troubleshoot unknown keys or invalid boolean values using the supported-key table. Boolean settings accept only true or false. Reset supports the three boolean keys; it does not reset machine_id.

Examples

/sync-config get auto_push
/sync-config set auto_push false

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.

Check your setup, free