manage-routines
Skill18 starsChanged 3 months agoMITView on GitHub
View, add, edit, or disable scheduled routines in an agent's schedules.json. Use when the user says "add routine", "schedule something", "manage routines", "list schedules", "disable routine", "change cron", "change schedule" — anything about an agent's recurring jobs.
- Reads credentials
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- create-agentSkill
- doctorSkill
- logsSkill
- manage-known-usersSkill
- manage-work-hoursSkill
- setupSkill
- setup-watcherSkill
- update-frameworkSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 32
If the user named the agent, use it.
- Very specific: line 36
Default to listing first if intent is unclear.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Manage Routines
Each agent's recurring routines live in agents/<n>/schedules.json. The listener watches that file and reloads schedules automatically — no PM2 restart needed.
Schedules use standard cron syntax: minute hour day-of-month month day-of-week. Times are interpreted in the listener-wide TZ env var (default UTC).
Schema
{
"schedules": [
{
"id": "daily-report",
"cron": "0 9 * * *",
"message": "Run your daily routine.",
"description": "Daily 09:00 report",
"enabled": true
}
]
}id is required and must be unique within the agent. enabled: false disables without deletion.
Step 1 — Pick the agent
If the user named the agent, use it. Otherwise list agents/*/ and ask. Confirm before continuing.
Step 2 — Decide: list, add, edit, disable, enable, remove?
Default to listing first if intent is unclear. Show the current schedules.json contents in a table:
| id | cron | description | enabled |
Then ask what they want to do.
Step 3 — Add
Ask:
- Cron expression — accept friendly forms like "every weekday at 9am" and convert. Validate with a quick sanity check (5 fields, ranges valid).
- Message — what the agent should do when the routine fires. This becomes the agent's input prompt at fire time. Be specific.
- Description — one short line for human readers (shows in
pm2 logs). - id — suggest a slug derived from the description. Confirm.
Cron tips for the user:
0 9 * * *— every day at 09:000 9 * * 1-5— weekdays at 09:00*/15 * * * *— every 15 minutes0 8 * * 1— Monday at 08:00
Append to the agent's schedules.json using jq:
jq '.schedules += [{...}]' "agents/<n>/schedules.json" > /tmp/s.json && mv /tmp/s.json "agents/<n>/schedules.json"Step 4 — Edit
Show the existing entry. Ask which field to change. Use jq to update in place. Don't change the id — if the user wants a different id, treat it as remove + add (otherwise you might orphan running schedule references).
Step 5 — Disable / enable
Toggle the enabled field:
jq '(.schedules[] | select(.id == "ID").enabled) = false' "agents/<n>/schedules.json" > /tmp/s.json && mv /tmp/s.json "agents/<n>/schedules.json"Disabled schedules stay in the file (safer than removing — preserves the cron expression in case it's wanted again).
Step 6 — Remove
Confirm first. Then:
jq 'del(.schedules[] | select(.id == "ID"))' "agents/<n>/schedules.json" > /tmp/s.json && mv /tmp/s.json "agents/<n>/schedules.json"Step 7 — Verify
The listener auto-reloads. Watch the log to confirm:
pm2 logs ginnie-agents-listener --lines 10 --nostream | grep "<agent_name>"You should see lines like [scheduler] <agent>: loaded "<id>" @ <cron> <TZ> for active entries. If a line is missing, check the user's cron syntax or the watched-file change detection (try touching the file: touch agents/<n>/schedules.json).
Common gotchas
- Cron in the wrong TZ: the cron is interpreted in the listener's
TZenv (default UTC). If the user says "9am their time", make sure the.env'sTZmatches their local zone. - Routines firing during off-hours: scheduled routines fire regardless of
work_hoursconfig — that's intentional. If the user wants a routine that only runs during work hours, they need to encode it in the cron expression directly. - Duplicate ids: the listener silently ignores invalid entries; if a routine doesn't fire, look for
[scheduler] <agent>: skipping invalid entryin the 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.

