Skip to content
Back to skills

Cron Manager

ASecurity

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+.

  • 5 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 9, 2026
ai-agentsrustbashexpress

Works with

  • cli

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add avivsinai/telclaude --skill cron-manager --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cron Manager?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cron Manager
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/avivsinai-cron-manager/badge)](https://www.skillsdirectory.com/skills/avivsinai-cron-manager)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cron-manager
description: 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+.
---

# Cron Manager

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

## Read

List jobs with machine-readable output first:

```bash
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:

```bash
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
```

```bash
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.