Manage scheduled jobs using natural language, including creation, inspection, and removal of cron tasks.

Install

mkdir -p .claude/skills/cron-manager && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19165" && unzip -o skill.zip -d .claude/skills/cron-manager && rm skill.zip

Installs to .claude/skills/cron-manager

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when the user wants to create, inspect, update, or remove telclaude scheduled jobs, especially natural-language schedules like "every weekday at 9am". Prefer this skill for cron CRUD behind WRITE_LOCAL+.
207 chars✓ has a “when” trigger
Intermediate

Key capabilities

  • List scheduled jobs with machine-readable output
  • Create new scheduled jobs with various schedule types
  • Define actions for scheduled jobs, including social, private, or prompt-based
  • Specify delivery targets for job output
  • Enable or disable existing scheduled jobs
  • Remove scheduled jobs

How it works

The skill interacts with the telclaude maintenance cron CLI to perform CRUD operations on scheduled jobs, allowing users to define schedules, actions, and delivery targets.

Inputs & outputs

You give it
User request to create, inspect, update, or remove a scheduled job
You get back
A scheduled job created, updated, or removed, or a list of existing jobs

When to use cron-manager

  • Schedule daily tasks
  • List active cron jobs
  • Remove scheduled routines

About this skill

Cron Manager

Use the telclaude maintenance cron CLI for scheduled-job CRUD.

Read

List jobs with machine-readable output first:

pnpm dev maintenance cron list --all --json

Use pnpm dev maintenance cron status --json when you need scheduler state or next-run data.

Create

Choose exactly one schedule flag:

  • --at <iso>
  • --every <duration>
  • --cron "<minute hour day month weekday>"

Choose exactly one action:

  • --social [serviceId]
  • --private
  • --prompt "<user-facing task>"

Prompt options:

  • --skill <name> can be repeated to restrict scheduled skill use. Use --skill for unattended routines that need tools; passing no --skill preserves the default private-agent skill policy.
  • --preprocess-command <path-or-executable> runs an executable before the prompt, with optional repeated --preprocess-arg <value>, --preprocess-cwd <path>, --preprocess-timeout-ms <ms>, and --preprocess-max-stdout-bytes <bytes>.
  • Preprocessors receive JSON on stdin and non-empty stdout is injected as untrusted read-only data. Empty stdout runs the agent without preprocess context; [IDLE] or [SILENT] skips the agent run.
  • Scheduled agent output containing [IDLE] or [SILENT] is treated as successful no-delivery output.

Delivery targets:

  • --delivery origin
  • --delivery home --owner <ownerId>
  • --delivery chat --chat-id <chatId> [--thread-id <threadId>]

Examples:

pnpm dev maintenance cron add \
  --name "weekday-hn" \
  --cron "0 9 * * 1-5" \
  --prompt "Check Hacker News and post a short summary here." \
  --delivery home \
  --owner admin \
  --json
pnpm dev maintenance cron add \
  --name "team-digest" \
  --cron "30 14 * * 1-5" \
  --prompt "Summarize open background jobs for the team." \
  --delivery chat \
  --chat-id 123456789 \
  --thread-id 42 \
  --json

Update / Delete

  • Enable: pnpm dev maintenance cron enable <id>
  • Disable: pnpm dev maintenance cron disable <id>
  • Remove: pnpm dev maintenance cron remove <id>
  • Run now: pnpm dev maintenance cron run <id>

Telegram-specific notes

  • /sethome persists the delivery destination for --delivery home.
  • If the system prompt includes identity: <localUserId> (linked), use that as --owner.
  • If the chat is unlinked, use tg:<chatId> as the owner id.
  • Cron expressions are UTC. Be explicit about that when translating natural-language schedules.

When not to use it

  • When managing cron jobs outside of telclaude
  • When direct file system access for cron configuration is preferred
  • When not using WRITE_LOCAL+ for cron CRUD operations

Limitations

  • Requires the telclaude maintenance cron CLI
  • Only one schedule flag can be chosen per job creation
  • Only one action can be chosen per job creation

How it compares

This skill provides a structured command-line interface for managing scheduled jobs with natural language schedule interpretation, unlike direct cron table editing.

Compared to similar skills

cron-manager side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
cron-manager (this skill)01moReviewIntermediate
setup121moNo flagsBeginner
tmux202moReviewIntermediate
macos-cleaner161moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry