Manage local cron-backed jobs with cronctl. Use for scheduling, running, debugging, syncing, importing, exporting, and inspecting jobs and logs.
Use this skill when the user needs local cron automation managed through cronctl.
Do not use this skill for remote schedulers, workflow orchestrators like Airflow or Prefect, or one-shot delayed commands better handled by at.
cronctl is connected as an MCP server, prefer:
cronctl_list_jobscronctl_create_jobcronctl_delete_jobcronctl_update_jobcronctl_run_jobcronctl_get_logscronctl_system_statuscronctl is installed as a CLI, prefer cronctl --json ... for structured output.uv run python -m cronctl --json ....cronctl is not installed, run , then , then ../scripts/bootstrap.shuv run python -m cronctl --json doctoruv run python -m cronctl init --non-interactivecronctl --json doctor or the source-checkout equivalent and confirm ready == true.CRONCTL_CRONTAB_BIN with a fake backend and a temporary --home /tmp/....~/.cronctl/scripts/ when that convention is useful.cronctl add or cronctl edit.cronctl exec <job_id> before trusting the schedule.cronctl --json logs <job_id> --last=1 after changes.cronctl --json status.cronctl --json logs <job_id> --last=5.status, exit_code, stderr, and timeout patterns.cronctl exec <job_id> again.cronctl export.cronctl import jobs.yaml.cronctl sync after manual cleanup if the crontab fence needs regeneration.add, edit, enable, disable, remove, or sync.--set key=value assignments when values contain spaces.cronctl exec instead of manually re-running the raw command when you need the same timeout, retry, logging, and notification path cron uses.