Menu
Use when the user says "cron job", "cron", or asks to "schedule" a task — they mean the in-session CronCreate tool firing locally on their own running computer, with standing consent; just set it up.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when starting any session of relatively extensive or large-scale autonomous work — above all any large-scale population of queue.md with created tasks — to run the three local-cron productivity playbook (work-loop, auto-flush, status-report).
Replicate the methods of "Neural Computers" (arXiv:2604.06425) and produce a runnable artifact, a published findings report, and a downloadable replication package.
Reproduce results from the Sutra paper — build the compiler, run the 10-program smoke test, run the rotation-vs-Hadamard capacity tables (LLM + ESM-2 protein-LM substrates), the chained-bind crosstalk experiment, plus the loop function decl + codebook test suites.
Use at the start of a session in a cleanvibe-scaffolded project, at most weekly — fetch cleanvibe's updates page and refresh this repo's .claude/skills/ to the latest shipped versions.
Use when the user sends a continuous series of "stop" messages (e.g. "stop stop stop") or otherwise very explicitly demands an immediate halt — kill all running processes, background jobs, and GitHub Actions runs for this repo, then take no further actions.
Use when doing any multi-step or planning work in a cleanvibe-scaffolded project — enforces plan-into-queue.md-first, the todo.md→queue.md→devlog.md flow, delete-don't-check completion, task-tool mirroring, and tests/CI discipline.
| name | cron-is-local |
| description | Use when the user says "cron job", "cron", or asks to "schedule" a task — they mean the in-session CronCreate tool firing locally on their own running computer, with standing consent; just set it up. |
When the user says "cron job", "cron", or asks to "schedule" a task, they mean the in-session CronCreate tool — a prompt scheduled to fire locally, inside this Claude Code session, on the user's own running computer. This is the default and the assumption. Do NOT interpret it as anything else unless the user explicitly names a different mechanism.
CronCreate tool. A generic "cron" request is NOT an OS crontab, NOT a GitHub Actions / CI schedule: trigger, and NOT a cloud scheduler. (A repo may also contain its own GitHub Actions cron schedules — those are a separate thing and are not what the user means when they ask you to set up a cron.) The user leaves the computer on and this session running so the scheduled prompt can execute.CronCreate requests are pre-authorized. Create the job immediately and locally, then report what was scheduled. Do not block on confirmation or follow-up questions.