routine-creatorlisted
Install: claude install-skill Shadysmetools/claude-skills
# Routine Creator
A routine is a headless `claude -p "<prompt>"` run on a schedule by your OS. LOCAL routines are the
default because they can see your sessions, worktrees, folders and local state. Offer a cloud
scheduler (for example the built-in `schedule` skill) ONLY when the task needs no local access
(e.g. pure GitHub or tracker watching).
## Paths (configurable)
| Thing | Default |
|---|---|
| Routine home `ROUTINES_HOME` | `~/.claude/ops-manager` |
| Wrapper | `$ROUTINES_HOME/routines/run-<slug>.cmd` (Windows) or `run-<slug>.sh` (macOS/Linux) |
| Log | `$ROUTINES_HOME/logs/<slug>.log` |
| Registry | `$ROUTINES_HOME/routines.jsonl` |
| Task name prefix `ROUTINE_PREFIX` | `Claude` (task name = `"<prefix> <Name>"`) |
| Claude binary | `claude` on PATH (use the absolute path if the scheduler's PATH lacks it) |
## Create (from args, or ask briefly: name, cadence, prompt, working dir)
1. **Derive** the slug, task name, wrapper path, log path and working dir (default: current project).
2. **Wrapper** (write the file, exact pattern):
Windows `run-<slug>.cmd`:
```bat
@echo off
cd /d "<workdir>"
call claude -p "<prompt>" >> "<log>" 2>&1
```
macOS/Linux `run-<slug>.sh` (then `chmod +x`):
```sh
#!/bin/sh
cd "<workdir>" && claude -p "<prompt>" >> "<log>" 2>&1
```
The prompt is usually a slash-skill invocation (`/some-skill args`) so the logic lives in a skill,
not in the wrapper. If the routine needs a new skill, create `~/.claude/skills