daily-sync
Skill2 starsChanged 13 days agoMITView on GitHub
Sets up and checks the daily run of the Claude Code config sync (~/.claude-sync), so each computer picks up what the others left (reminders, handoffs, config) every morning, even with no session open. Use when the user says "sync every morning", "daily sync", "schedule the sync", "change the sync time", "is the morning sync on?", "stop the daily sync", or when another skill (reminders) needs the morning run.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- seco/declawtheir own version, first seen Apr 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- seco/declaw★ 1same 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- capability-builderSkill
- ci-reviewSkill
- handoffSkill
- insta360-montageSkill
- kbSkill
- pr-watchSkill
- remindersSkill
- reopen-sessionsSkill
- sprint-demoSkill
- tech-watchSkill
- test-evidenceSkill
- video-montageSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 36
Before turning it on for the first time on a computer, propose it to the user with the time you'd pick and why, and wait for their yes.
- Very specific: line 42
If a step failed, the log is ~/.claude-sync/.state/log (and morning.log on macOS).
- Very specific: line 46
Put a morning.sh at the root of the skill's folder.
≈ “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.
Files
Daily sync
The sync engine (~/.claude-sync/sync.sh, see ~/.claude-sync/README.md) does two things each day:
- Every session start: a full sync runs in the background, so the session starts at once. A skill that needs the result waits for it in the background with
sync.sh fresh(it returns once a full sync has succeeded today); the reminders skill does that, then notifies what came in and hands it to the session with the user's next message. - Every morning at a set time (default 09:00): the computer's own scheduler runs
sync.sh morning, which syncs and then runs themorning.shof each installed skill (copied in~/.claude/skills/or installed as a plugin). That's how the reminders skill notifies the user even when no session is open. - At login: the same scheduler syncs once, so a handoff left to run on this computer starts with no session open.
After every sync (these, the session ones and the pane's one-minute poll), the engine runs in the background the on-sync.sh of each installed skill: that's how the handoff skill starts the runs due on this computer and tells the sender when one changed status.
The scheduled run needs the sync engine installed on the computer. It doesn't need Claude Code to be open.
Turn it on, change the time, turn it off
Scripts are in this skill's base directory (~/.claude/skills/daily-sync/ when installed by install.sh; $SK below).
bash $SK/schedule.sh status: whether the daily run is on, at what time, whether the login sync is on, and the day of the last daily sync.bash $SK/schedule.sh on [HH:MM]: every day at that time (24 h, default09:00), and at login. Running it again replaces the time; on a computer set up before the login sync existed, run it again with the same time to add it.bash $SK/schedule.sh off: both.
What it creates:
| System | Scheduler | Missed run (computer asleep or off) | At login |
| macOS | LaunchAgent ~/Library/LaunchAgents/com.claude-sync.morning.plist | runs on wake | LaunchAgent com.claude-sync.login (runs at load) |
| Linux | a crontab line ending in # claude-sync-morning | skipped; the first session of the day still syncs | an @reboot line ending in # claude-sync-login (at boot) |
| Windows (Git Bash) | Task Scheduler task claude-sync-morning | runs as soon as the computer is back | task claude-sync-login (at logon) |
On Windows a console window opens for a few seconds while the task runs; that's expected.
Before turning it on for the first time on a computer, propose it to the user with the time you'd pick and why, and wait for their yes. Then tell them which time you used.
Check that it works
bash ~/.claude-sync/sync.sh morning, thenbash ~/.claude-sync/sync.sh status: the last log lines show the sync and eachmorning:step.bash $SK/schedule.sh statusshows the time.- If a step failed, the log is
~/.claude-sync/.state/log(andmorning.logon macOS).
Add a morning step to another skill
Put a morning.sh at the root of the skill's folder. It runs after the morning sync, with no terminal and no Claude session, so it must be quick, need no input and write nothing to stdout that matters (stdout goes to the sync log).
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
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.