scheduled-task

name: scheduled-task description: Create scheduled tasks for recurring or one-time automated execution. Use when users want to set up tasks that run automatically at specified times (daily, weekly, monthly, cron, or one-time).

Scheduled Task Skill

Usage Scenarios

Use this skill when users want to:

• Set up tasks that run on a schedule (daily, weekly, monthly, custom cron)
• Create one-time tasks that run at a specific time
• Schedule automated checks, report generation, code backups, etc.
• Set up periodic monitoring or reminders

Creating Scheduled Tasks

Step 1: Gather Information

Confirm the following with the user (if not provided):

1. Task name (required) — Short description
2. Execution content (required) — The prompt/instructions Claude receives when the task runs
3. Execution frequency (required) — One-time, daily, weekly, monthly, or custom cron
4. Working directory (optional) — Defaults to current session working directory
5. Notification platforms (optional) — Send notifications after task completion

Step 2: Build JSON and Execute API Call

Schedule Types

One-time execution (at):

{ "type": "at", "datetime": "2026-03-15T09:00:00" }

Cron expression (cron) — 5-field format: minute hour day month weekday

{ "type": "cron", "expression": "0 9 * * *" }

Common cron examples:

Create Task via API

Use the backend API to create scheduled tasks. The API endpoint should support the following payload structure:

{
  "name": "Task name",
  "schedule": { "type": "cron", "expression": "0 9 * * *" },
  "prompt": "Detailed instructions Claude will execute when task runs...",
  "workingDirectory": "/path/to/project",
  "description": "Optional detailed description",
  "systemPrompt": "Optional custom system prompt",
  "executionMode": "auto",
  "expiresAt": "2026-12-31",
  "notifyPlatforms": ["dingtalk", "feishu", "telegram", "discord"],
  "enabled": true
}

Field Descriptions

Step 3: Confirm Results

API returns JSON response:

• Success: { "success": true, "task": { "id": "...", "name": "...", ... } }
• Failure: { "success": false, "error": "error message" }

Confirm the following with the user:

• ✅ Task name and ID
• ⏰ Execution frequency (human-readable format, e.g., "Every day at 9:00 AM")
• 📋 Execution content summary
• 💡 Remind user they can manage tasks in Settings → Scheduled Tasks

Important Notes

• Relative time handling: When users specify relative times like "in X minutes / tomorrow at 9 AM / this afternoon", first get the current local time using a system command, then calculate the target time. Don't guess the current time or use UTC.
• Creation timing: For short-delay one-time tasks (e.g., "in 1 minute"), create the task immediately before performing any time-consuming operations. Don't fetch data or summarize content before creating the task.
• Prompt boundaries: The prompt should describe "what to do when the task triggers", not pre-execute the task and embed static results. Example: write "Fetch yesterday's AI news and send summary" instead of fetching news first and embedding the list in the prompt.
• Get current time (cross-platform):

  node -e 'const d=new Date();const p=n=>String(n).padStart(2,"0");console.log(`${d.getFullYear()}-${p(d.getMonth()+1)}-${p(d.getDate())}T${p(d.getHours())}:${p(d.getMinutes())}:${p(d.getSeconds())}`)'
  

• Auto-execution: Scheduled tasks run with auto-approve enabled for all tool calls (no manual approval needed)
• Independent execution: The prompt is the only instruction Claude receives when the task runs independently, so write it clearly and completely
• Auto-disable: Tasks that fail 5 consecutive times are automatically disabled
• One-time tasks: Tasks with type: "at" are automatically disabled after execution
• Execution sessions: Each execution creates a new session (with "[Scheduled]" prefix in title), viewable in the session list