cron-manager

Cron Manager Skill

Trigger

This skill activates when the user wants to create, edit, delete, enable, disable, or list scheduled cron jobs.

Data File

All cron jobs are stored in ~/.jinn/cron/jobs.json as a JSON array of job objects. If the file does not exist, create it with an empty array [].

CronJob Schema

{
  "id": "uuid-v4",
  "name": "daily-standup-summary",
  "enabled": true,
  "schedule": "0 9 * * 1-5",
  "timezone": "America/New_York",
  "engine": "claude",
  "model": "sonnet",
  "employee": "project-manager",
  "prompt": "Review all department boards and summarize progress since yesterday. Highlight blockers and upcoming deadlines.",
  "delivery": {
    "connector": "slack",
    "channel": "#engineering-standup"
  }
}

Field details:

• id - UUID v4, generated when creating the job
• name - kebab-case human-readable identifier, must be unique across all jobs
• enabled - boolean, whether the job is active
• schedule - standard cron expression (minute hour day month weekday)
• timezone - IANA timezone string (e.g., America/New_York, Europe/London, UTC)
• engine - AI engine to run the job: claude or codex
• model - model identifier (e.g., sonnet, opus, o3)
• employee - optional, the employee persona to use (must match an employee name in the org)
• prompt - the instruction to execute when the job fires
• delivery - optional object specifying where to send output
  • connector - the connector to use (e.g., slack, discord)
  • channel - the target channel or destination

Operations

Creating a Job

1. Read the current ~/.jinn/cron/jobs.json (or initialize as [] if missing).
2. Ask the user for the required fields: name, schedule, engine, model, and prompt.
3. Ask about the timezone. Default to UTC if not specified.
4. Ask about the employee persona to use. This is optional.
5. Always ask the user about the delivery channel if they did not specify one. Explain that without delivery, the output will only be logged.
6. Delegation check: If the job has delivery configured AND targets a non-{{portalSlug}} employee, warn the user. The correct pattern for reporting/analytical jobs is: target {{portalSlug}}, and include delegation instructions in the prompt (e.g. "Delegate to @employee-name: ..."). {{portalName}} reviews and filters the output before it reaches the delivery channel. Only simple, no-review tasks (e.g. health checks) should target employees directly with delivery.
7. Generate a UUID for the id field.
8. Set enabled to true by default.
9. Append the new job object to the array.
10. Write the updated array back to ~/.jinn/cron/jobs.json.
11. Confirm the creation and summarize the schedule in plain English.