Wrappers

Skill JonMcMillan/claude-sync-by-skill/wrappers/sync-notes

Directional, cross-platform, transport-agnostic sync for Claude Code env (settings, memory, plans, skills) driven by an in-Claude skill. up/down/status.

Install

npx -y skills add JonMcMillan/claude-sync-by-skill --skill sync-notes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Show all currently active cross-device reminder notes held in the sync folder (from every machine, including this one). Read-only. Use when the user types /sync-notes or asks to see their outstanding sync notes / what reminders are pending across their devices. To leave a new note use /sync-add-note; notes are surfaced and resolved during /sync-env-down.

SKILL.md

1.5 KB, 302 tokens by cl100k_base, as published. Nobody here has run it

sync-notes — list active cross-device notes

Read-only. Shows every active note across all the user's machines. The engine (sync_engine.py) lives in the sibling sync-envs skill folder.

How to run the engine

Windows: py -3 "<claudeSkillsDir>\sync-envs\sync_engine.py" --list-notes
macOS/Linux: python3 "<claudeSkillsDir>/sync-envs/sync_engine.py" --list-notes

Run it in the background (the Bash tool's run_in_background: true) — it reads the sync folder, usually a cloud drive; see the timing note in /sync-env-down if it stalls.

What to do

Run the engine with --list-notes and show the user the output. Each active note lists its id, text, origin machine, and age; notes from the current machine are marked (from this device).
Make no changes — this is read-only. Notes are surfaced for action (make a task / keep / resolve) during /sync-env-down; adding is /sync-add-note.
If there are none, say so plainly.
If the user wants to clear one from here, you can resolve it directly (confirm first — it clears on every machine): ... sync_engine.py --resolve-note "<id>".