Four Failures That Made a Weekly launchd Job Actually Run
Every skill my AI setup learns lives in one folder on my laptop — and none of it reaches the repo I created yesterday. That gap is why I built a weekly job that pushes my accumulated skills into every project on the machine. This is what it does, and the four failures I hit getting it to run unattended. Why this mechanism works Claude Code's ~/.claude/skills/auto/ is essentially a personal…
Every skill my AI setup learns resides in a single folder on my laptop, and none of it reaches the new projects I create. That discrepancy led me to build a weekly job that distributes my accumulated skills across every project on the machine. This job, named com.shun.autoskills-sync, runs automatically every Sunday morning using launchd, a macOS job scheduler.
The script scans all git repositories, copies the skills from ~/.claude/skills/auto/, and distributes them to the respective projects. This process eliminates the need for manual copying and ensures that newly opened projects have the latest skills at their disposal.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
