Schedule, list, pause, resume, edit, or run the user's agentica cron jobs with the cronjob tool.
SkillScore78Maintained
Automatic
◆DevOps & SRE pack
Last verified 9/29/2026
What it changes
Passed 13 of 17 test cases with the skill, and 7 of 17 without it.
Without skill43%
With skill78%
Checks it passed that the model alone missed
Explicitly advises against editing crontab by hand.
Instructs using the cronjob tool to create or modify jobs.
Identifies /cron as the user command surface for managing background jobs.
and 8 more in the full report
9 fixed9 passed either way4 still failing1 broke
Pass-rate lift
+35 pp
Tokens
-25%
Agent turns
0%
Response time
-44%
Model gemini-3.6-flashMeasured 9/29/2026v118 of 23 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
Which command interface surface should an interactive terminal user use to list, add, pause, or run background jobs?
What was checked, without and with the skill
Checked
Without skill
With skill
Identifies /cron as the user command surface for managing background jobs.
Missed
Passed
case-09 · gemini-3.6-flash · 9/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md19 linessingle file
Scheduled jobs
Use the cronjob tool. Do not edit crontab or ~/.agentica/cron/jobs.json by
hand. The tool schema lists the actions; do not invent them.
A job runs in a fresh session with none of this conversation. The prompt
must be self-contained: goal, constraints, where things are, what to do when
blocked. A prompt that needs a follow-up question will stall unattended.
Jobs only fire on their schedule while the scheduler daemon is on. How the user
turns it on depends on the surface:
Interactive CLI: they type /cron daemon on. You cannot type slash commands; tell them which one. /cron is also their surface for list / add / pause / run.
Gateway and other surfaces:cron.enabled in config.yaml is a
deployment-level setting. You cannot toggle it from this conversation; tell
the user to ask whoever manages this deployment to enable it.
action='run' executes a job once now so you can show the result before
waiting for the schedule.
Isolate this CLI session in its own git worktree of the current repository (worktree tool: status / use / merge / remove). Use when another live session is dirty in the same directory (list_agents), when two agents would fight over index.lock, when starting a parallel task checkout, or when asked to switch into a named worktree.