---
name: shibing624-cron
description: "Schedule, list, pause, resume, edit, or run the user's agentica cron jobs with the cronjob tool. Use when asked to remind, schedule a recurring or one-shot task, try a job now, or manage jobs that fire unattended."
license: "Apache-2.0"
metadata:
  decimalai-skill-id: "555dcb08-ab3a-4bae-92b0-343aac8dc4ad"
  decimalai-version-id: "50a47d6a-4600-476f-ba68-3f148390b0f5"
  decimalai-version: "1"
  decimalai-body-sha256: "7715eafd536f6829cf82d4026e236198221e57c599271f9222bd4a2937747f64"
  decimalai-name: "shibing624/cron"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "agent-tooling"
  decimalai-source: "https://app.decimal.ai/s/shibing624-cron@1/SKILL.md"
---
# 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.