← ClaudeAtlas

manage-desktop-routineslisted

Create, back up, and restore Claude Code Desktop local routines (scheduled tasks) so they survive a PC change. Use when the user wants to set up a recurring or one-off Desktop routine, back up their routines, or restore routines on a new machine.
atman-33/workhub · ★ 2 · API & Backend · score 81
Install: claude install-skill atman-33/workhub
Manage Claude Code Desktop routines: create a **local** routine, and keep a portable backup so it isn't lost when you move to a new machine. ## Local vs remote Desktop's Routines page creates two different things: - **Local** — a scheduled task stored at `~/.claude/scheduled-tasks/<taskId>/SKILL.md` (or under `CLAUDE_CONFIG_DIR`) on this machine only. It runs only while Desktop is open. Nothing about it is synced to the cloud, so it is lost on a fresh machine unless backed up. This skill manages **local** routines only. - **Remote** — a saved configuration in the user's claude.ai account, run on Anthropic-managed cloud infrastructure. It already survives a machine change on its own and needs no backup. If the task needs to run with the machine off, or fire on an API call or GitHub event, tell the user to create a **Remote** routine instead, from Desktop's **Routines → New routine → Remote** or [claude.ai/code/routines](https://claude.ai/code/routines) — this skill does not create those. Ask the user which they need only if it isn't obvious from the request; local file/tool access implies Local, "even when my laptop is off" or API/GitHub triggers imply Remote. ## Backup scope `list_scheduled_tasks` and `create_scheduled_task` expose `taskId`, `description`, `prompt`, `cronExpression`/`fireAt`, and `enabled`. They do **not** expose the working folder or model shown in Desktop's own routine form — those live outside this tool surface. A backup/restore cycle through this sk