Schedule management with staggering, quiet hours, and wake-up override. Validates schedules, prevents collisions, and gates delivery during quiet hours.
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./skills/cron-scheduler/SKILL.mdConvention: See
skills/conventions/test-before-bulk.md— test every cron job on 3-5 items first.
This skill guarantees:
reports/{job-name}/{YYYY-MM-DD-HHMM}.mdGBRAIN_HOME and keeps stderr and the exit code
(the wrapper)agentTurn. See skills/conventions/cron-via-minions.md for the rewrite pattern (PGLite uses --follow, Postgres uses fire-and-forget + --idempotency-key on the cycle slot). GBrain's v0.11.0 migration auto-rewrites entries for built-in handlers; host-specific handlers need a code-level registration per docs/guides/plugin-handlers.md.HOME and
environment than your shell, so a bare gbrain (or bun run src/cli.ts)
can find no database (every lookup silently empty) or act as a second host
(refresh_not_owner). Register gbrain-run <args>, the wrapper in
cron-schedule.md:
it sets GBRAIN_HOME (never HOME), loads the brain's env file and runs
the installed binary. Log stderr to a file, check the exit code, keep hook
output off stdout, and give each call a timeout of at least 10 s.
The lines below write gbrain-run; doctor prints the bare command.
gbrain doctor --only cron_gbrain_home warns about any crontab line or
script that runs src/cli.ts directly or calls gbrain without the brain's
GBRAIN_HOME.Every cron job MUST be idempotent:
Job configuration saved. Report: "Job '{name}' scheduled at {cron expression}. Next run: {time}."
sync --all, not per-source entriesWhen the brain has 2+ active sources (anything gbrain sources list shows
with a non-null local_path that isn't archived), use one consolidated
cron line instead of N per-source entries.
Preferred (multi-source):
*/5 * * * * gbrain-run sync --all --parallel 4 --workers 4 --skip-failed >> /tmp/gbrain-cron.log 2>&1This replaces N per-source lines AND auto-picks-up future sources without
a crontab edit. Concurrency budget: parallel × workers × 2 ≈ 32
connections during the wave (each per-file worker opens its own
2-connection pool). Stay under your Postgres max_connections setting.
Avoid (legacy): separate gbrain sync --source default and
gbrain sync --source zion-brain entries staggered by 5 minutes. They
require manual deconfliction every time a new source is added, and a
slow source can race a fast source on the legacy global gbrain-sync
lock (v0.40.3.0+ uses per-source gbrain-sync:<sourceId> locks but the
per-source cron pattern doesn't benefit from the parallelism that
--all --parallel actually delivers).
gbrain doctor surfaces the recommended line as a sync_consolidation
check whenever it detects 2+ active sources. Paste-ready from there.
A managed brain refuses the line above: managed sync needs --no-pull and
rejects --skip-failed (writer_coordinator_required). Check the mode first:
gbrain sources writer status --json reports "mode": "managed" or
"mode": "classic", and its bindings name each source's owner host.
On a managed brain, install this line instead, on the host that owns the sources:
*/15 * * * * gbrain-run sources git-reconcile >> /tmp/gbrain-cron.log 2>&1; gbrain-run sync --all --no-pull --hard-deadline 13m >> /tmp/gbrain-cron.log 2>&1gbrain sources git-reconcile brings every checkout on the host level with
its upstream; a managed checkout goes through gbrain sources refresh (a
fetch and git merge --ff-only, then a managed sync of its sources), the
only way it takes upstream commits. A level checkout costs one fetch, and
autopilot already runs it each tick. The ; is deliberate: the sync still
runs when a reconcile refuses.refresh_diverged: the checkout has commits its upstream lacks, so
something commits outside gbrain (usually a script that writes files and
runs git commit in the checkout). Fix that writer so it commits with
gbrain git commit-push -- <paths>, then reconcile as the refusal says
(gbrain git commit-push --push-only --keep-checkout, after the user
agrees); never force the checkout
(scripts and the managed checkout).--hard-deadline 13m stays under the 15-minute interval. Managed sync takes
no per-source lock, so a run that outlives the interval would overlap the
next tick. A run stopped at its deadline ends resumable and the next tick
continues it. Sources drain one at a time, so --parallel does not apply.owner_unavailable for a source: read its detail. unbound_source on a
classic Postgres brain is normal and does not stop classic sync; keep the
sync line. Any other detail means another host owns the source: install a
per-source line on that host (gbrain sync --source <id> --no-pull --hard-deadline 13m, plus its refresh) instead of claiming it here.gbrain sync --source <id> --no-pull … with the failed run's options; the
next sync retries what the last one recorded. Never add --skip-failed
(--retry-failed is a deprecated alias of the plain sync on a managed
brain).gbrain doctor prints this managed line in sync_consolidation on a managed
brain with 2+ active sources.
Follow the agent operator protocol for any gbrain error code, exit code, [AGENT] block or notice block. Specific to this skill:
gbrain sync hits sync_in_progress / lock_busy: an earlier tick still runs. Widen the interval or stagger the job; never add a second overlapping schedule.gbrain sources status <id> for held items or errors before changing the schedule again.checkpoint_validation_timeout in a sync log: run the retry command the error prints; do not cancel the request.writer_coordinator_required from a scheduled sync: the brain is managed. Replace the line with the managed brain recipe; never retry with --skip-failed or without --no-pull.sync_in_progress from gbrain sources refresh: a managed sync cursor is unfinished, and the refresh never waits on it. Run the gbrain sync --source <id> --no-pull … command the refusal prints; the next tick's refresh then runs.worktree_refreshing from a sync: a refresh is draining or merging that checkout. Leave it; the next tick syncs it. A page write answered pending (exit 10) during a refresh is waiting behind it: poll its receipt, never resubmit.no_brain or GBRAIN_DB_ACCESS no_url: the job runs without the brain's config. Call gbrain through the wrapper; an empty result from a job whose stderr went to /dev/null is not evidence of "no notes".refresh_not_owner from cron while the same refresh works by hand: the job resolves another gbrain home, so it is another host. The refusal names the identity file, HOME and GBRAIN_HOME it read; set the owner's GBRAIN_HOME in the wrapper. Never copy or delete a host.json.--json caller fails to parse gbrain's output: something the wrapper runs prints to stdout. Send that hook's output to a log file.gbrain write-request <request_id> before retrying or reporting it.gbrain or bun run src/cli.ts in a cron line, script or hook
instead of the wrapper; a wrapper that sets HOME instead of GBRAIN_HOME2>/dev/null on a gbrain call, or ignoring its exit codegit commit in a managed checkout
instead of gbrain git commit-push -- <paths>env or a process environment into a log or transcript while
debugging (it holds the database URL and keys)gbrain sync --source <id> cron entries when
gbrain sync --all --parallel N --workers N would replace them with
one line that auto-picks-up future sources.garrytan/gbrain
f4d1866
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.