agentleFS
tonydzitonydzi/second-brain-starter-kit/skills/sync-check/SKILL.md

sync-check

Skill6 starsChanged 2 months agoMITView on GitHub

Report this machine's file-synchronization state with the whole fleet: peers connected, per-share state and files still needed, folder errors, and how many sync-conflict files piled up, which is the silent sign two machines are fighting over a file. Read-only and zero tokens. Triggers: "/sync-check", "is sync alive", "sync status".

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    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
  1. Distinctive:

    BEFORE relying on a fresh file from another machine ("not found" ≠ "does not exist" — it may still be in transit.

    line 35
  2. Distinctive:

    AFTER a sync incident (like the nested-folder D2 case of 2026-06-24/25) — to confirm the bridge is back.

    line 36
  3. Distinctive:

    Read-only: it fixes nothing and moves nothing.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

/sync-check — is the sync between my machines healthy

One command answers "did it arrive / are we syncing right now" across ALL Syncthing folders of this machine, without poking the REST API by hand. READ-ONLY, 0 tokens, portable (the API key is read from the local config → it works on any machine of the fleet).

Engine: $IMPORTS_ROOT/sync_check/sync_check.ps1 (git-backed in _imports, synced through claude-imports). It now also includes Device ID drift detection (live myID vs machines.json → RED on a mismatch — it would have caught the 2026-06-25 incident).

Cleaning up sync-conflict files (when the report says "WARN sync-conflict files: N"): python $IMPORTS_ROOT/sync_check/resolve_conflicts.py (dry-run) → for each conflict it compares against the live file: --quarantine SAFELY moves conflicts of the live tree into _sync-conflict-archive\<date>\ (a move, not a delete → recoverable; orphans with no live twin are left alone), --apply deletes only proven subsets. Already-archived files and .stversions are excluded. Canon: the sync-loss incident runbook, §6.

Run

powershell -NoProfile -ExecutionPolicy Bypass -File "$IMPORTS_ROOT/sync_check\sync_check.ps1"

How to read the output

  • PEERS — how many peers are connected. 0 connected = sync is DEAD (the machine slept / Syncthing is stuck) → start the watchdog syncthing_watchdog.ps1 (see the migration runbook, the on-wake task SyncthingWatchdogOnWake).
  • per folder OK / WARN / RED:
    • OK + NEED=0 = the folder is in sync, everything arrived.
    • WARN + NEED>0 = still downloading (fine briefly; if it is stuck, look at the peers).
    • RED = state=error or folder errors → investigate (permissions / disk / conflict).
  • sync-conflict files — a separate WARN (it does not turn the report RED). Their growth means two machines are editing the same file (e.g. settings.json) → decide "fresher beats older" (the operator decides) and clean up *.sync-conflict-*.
  • EXIT 0 = all green; EXIT 2 = something is RED.

When to call it

  • The operator asks "did it reach the hub / the Mac?", "is sync alive?".
  • BEFORE relying on a fresh file from another machine ("not found" ≠ "does not exist" — it may still be in transit; memory deterministic-script-gotchas).
  • AFTER a sync incident (like the nested-folder D2 case of 2026-06-24/25) — to confirm the bridge is back.
  • Each machine runs its own check (the report is local); to compare the whole fleet, ask every machine via /inbox or the bus.

Boundaries

  • Read-only: it fixes nothing and moves nothing. Healing a stuck sync is the watchdog's job (separate).
  • It only sees what the local Syncthing daemon knows; if the daemon is not running it says so (RED).

<!--kit-footer-->

Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.

Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).

Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_

Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.

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.