agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/brave-automation/brave-sync-management/SKILL.md

brave-sync-management

Skill0 starsChanged 8 days agoMITView on GitHub

Manage Brave Sync chains and profile enrollment.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Use when synchronizing Brave profiles into a single shared Sync Chain, extracting sync mnemonic codes, joining profiles, or troubleshooting …

    line 12
  2. Very specific:

    Ensure Brave is launched without --disable-sync.

    line 17
  3. Very specific:

    If not enrolled, click Start a new Sync Chain -> Computer.

    line 21
  4. Very specific:

    If an invalid/deleted chain message appears ("It looks like the sync chain you are on was deleted or is no longer valid"), click Leave Sync …

    line 22
  5. Distinctive:

    Do not parse the outer dialog or widget wrapper text, as UI buttons and status labels pollute the mnemonic string.

    line 26
  6. Distinctive:

    Wait for the profile to complete sync initialization.

    line 32
  7. Very specific:

    Process Termination: Always terminate Brave instances cleanly before reading/modifying profile preferences.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Brave Sync Management

Manage Brave browser profile synchronization across multiple local profiles using the Brave Sync v2 protocol.

When to Use

Use when synchronizing Brave profiles into a single shared Sync Chain, extracting sync mnemonic codes, joining profiles, or troubleshooting sync enrollment and stale chain errors.

Workflow

  1. Verify Browser Flags:
    • Ensure Brave is launched without --disable-sync. If --disable-sync is present, brave://settings/braveSync renders blank and all sync RPCs fail.
  2. Source Profile Chain Setup:
    • Navigate source profile to brave://settings/braveSync/setup.
    • If not enrolled, click Start a new Sync Chain -> Computer.
    • If an invalid/deleted chain message appears ("It looks like the sync chain you are on was deleted or is no longer valid"), click Leave Sync Chain or Reset and re-join sync chain and confirm the dialog before re-attempting setup.
  3. Mnemonic Extraction:
    • In the "Sync Chain Code" dialog, extract the 24/25-word phrase directly from the Shadow DOM textarea.sync-code-text (or settings-brave-sync-code-dialog textarea).
    • Do not parse the outer dialog or widget wrapper text, as UI buttons and status labels pollute the mnemonic string.
  4. Target Profile Joining:
    • For each target profile, navigate to brave://settings/braveSync/setup.
    • Click I have a Sync Code.
    • Paste the extracted 24/25-word code into the input field and submit.
    • Wait for the profile to complete sync initialization.
  5. On-Disk Verification:
    • Read <profile_dir>/Preferences JSON.
    • Inspect brave_sync_v2.seed. All profiles successfully joined to the same Sync Chain share the exact same seed string.

Pitfalls & Lessons

  • Shadow DOM Extraction: Brave Settings uses Polymer Web Components. Document-level document.querySelector cannot pierce the dialog shadow roots; recursively traverse element.shadowRoot to find textarea.sync-code-text.
  • Stale Chain Lock: A profile with a broken sync seed must explicitly execute the "Leave Sync Chain" flow. Joining a new code while a stale seed is recorded in Preferences without clearing it first will fail.
  • Process Termination: Always terminate Brave instances cleanly before reading/modifying profile preferences. Use targeted PIDs or pkill -9 -x "brave" / pkill -9 -f "remote-debugging-port=" to avoid terminating caller scripts.
  • Strict Profile Roster: Prune residual Default / Personal profiles so only profiles in profile.csv remain registered in Local State.

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.