Menu
Manage scheduled cron jobs — add, list, edit, enable/disable, remove jobs and view run history.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Search and manage Merlin's notes — knowledge base (Zettelkasten), daily logs, and user facts. Use this to recall past conversations, add knowledge, or look up stored information.
Understand your own architecture, source code, configuration, and runtime behavior. Use when you need to inspect how you work, review your logs, debug your own behavior, or answer questions about your capabilities.
Send messages, reply to messages, and react to messages in Discord. Use this skill whenever you need to communicate back to the user via Discord.
Give the user the link to the monitoring dashboard. Use this when the user asks for the dashboard URL or wants to see the dashboard.
Capture screenshots of web pages at multiple viewports for visual validation. Use this skill when you need to verify responsive layout or take before/after screenshots of UI changes.
| name | cron |
| description | Manage scheduled cron jobs — add, list, edit, enable/disable, remove jobs and view run history. |
| user-invocable | false |
| allowed-tools | Bash |
Manage scheduled tasks using the merlin cron command. All operations use
this command for validation and consistent formatting. It works from any
directory.
IMPORTANT: Never read or write cron-jobs/*.json files directly. Always
use the merlin cron commands below. The command handles path resolution,
validation, and formatting. Reading files directly wastes cycles on path
guessing; writing directly bypasses validation and can create broken jobs.
merlin cron list
merlin cron get <job-id>
Conversational flow:
Preview with dry-run:
merlin cron add \
--schedule "0 9 * * *" \
--prompt "Check for new Python releases" \
--description "Daily Python check" \
--report-mode silent \
--dry-run
Show the user a summary and ask for confirmation. After confirmation, run without --dry-run:
merlin cron add \
--schedule "0 9 * * *" \
--prompt "Check for new Python releases" \
--description "Daily Python check" \
--report-mode silent
Important: The prompt should describe the task, not how to deliver results. The engine returns text output and the notification system handles delivery. Never include "send to Discord" or similar in prompts.
Options:
--schedule — Cron expression (required)--prompt — Task for the engine to execute (required)For all other flags (report mode, max turns, description, explicit id,
channel routing) run merlin cron add --help; never restate them from
memory.
merlin cron enable <job-id>
merlin cron disable <job-id>
Confirm the action to the user after running.
Always confirm before removing:
merlin cron remove <job-id>
Run a job immediately, bypassing the schedule:
merlin cron trigger <job-id>
This executes the job exactly like the scheduler would — same logging, history tracking, and session handling. Useful for:
merlin cron history <job-id>
Or for all jobs:
merlin cron history
| Schedule | Expression |
|---|---|
| Every minute | * * * * * |
| Every hour | 0 * * * * |
| Daily at 9:00 | 0 9 * * * |
| Monday at 9:00 | 0 9 * * 1 |
| Weekdays at 8:00 | 0 8 * * 1-5 |
| Twice daily (9:00, 18:00) | 0 9,18 * * * |
| Every 2 hours | 0 */2 * * * |
| First of month | 0 0 1 * * |
| Sunday at midnight | 0 0 * * 0 |
Format: minute hour day-of-month month day-of-week
Translations:
0 9 * * *0 * * * *0 9,18 * * *0 9 * * 10 8 * * 1-5--dry-run to preview job creation before confirmingalways (digests, reports), silent (errors only, good
for monitoring jobs), off (no notifications); see merlin cron add --help