THE SCHEDULED-TASK SETUP

Schedule Claude to run a skill at the same time every week — Sunday Reset at 4pm Sunday, Morning Map at 7am weekdays, Birthday Auto-Pilot every Monday. Claude works while you sleep. The single feature that turns Claude from a chatbot into a teammate.

THE PROBLEM

The skills you've installed are useful — but only if you remember to run them. Most people install Sunday Reset, use it twice, then forget. The skill works; the habit breaks.

Scheduled tasks fix this. Claude runs the skill on the schedule, posts the output, and pings you. No remembering required.

THE SKILL

You give Claude:

Which skill to schedule
When to run it (cron-style or natural language)
Where to deliver the output (chat / email / Notion)

Claude sets up the schedule. After that, the skill just runs.

INSTALL

Scheduled tasks are a Claude feature. Available in Claude Code via the schedule plugin, and on Claude.ai for some plan tiers.

THE FULL SKILL FILE

---
name: scheduled-task-setup
description: Sets up recurring scheduled tasks that run skills on a schedule. Inputs: which skill, when to run, where to deliver output. Outputs: configured schedule plus the management commands for editing or pausing.
when_to_use: User says "schedule this skill," "run automatically," "every week," or describes wanting Claude to run something on a recurring basis.
---

# The Scheduled-Task Setup

You configure scheduled tasks. Decisive about cadence. Anti-overscheduling.

## Inputs
1. **Skill** — which skill to schedule
2. **Cadence** — when (cron expression OR natural language: "every Sunday 4pm")
3. **Output destination** — chat / email / Notion / Slack

## Output: scheduled task config

✅ TASK SCHEDULED

Skill: [Name] Runs: [Cadence in natural language + cron expression] Output to: [destination]

What runs on schedule: [The exact prompt that fires]

Inputs Claude will gather automatically:

[Calendar events]
[Recent emails]
[Etc.]

Inputs Claude will prompt you for:

[If any]

Test it: I'll run it once now to confirm it works.


## Recommended schedules for 100 Days skills

| Skill | Best schedule |
|---|---|
| Day 32 — Sunday Reset | Sunday 4pm |
| Day 34 — Morning Map | Weekdays 7am |
| Day 6 — Inbox Drainer | Weekdays 9am |
| Day 41 — Birthday Auto-Pilot | Monday 8am |
| Day 49 — Personal CRM | Friday 10am |
| Day 47 — Note-to-Knowledge-Base | Sunday 5pm |
| Day 45 — Delegator | Run on-demand only (not scheduled) |

## What NOT to schedule

- **Decision skills** (Day 33 Yes-or-No) — needs your input, not a schedule
- **Story skills** (Day 50 Halfway Recap) — when you have something to reflect on, not on a clock
- **Crisis skills** (Day 43 Hard-Email) — you'll know when

## What NOT to do

- Don't schedule more than 5 recurring tasks (becomes noise)
- Don't schedule overlapping outputs (5 things at 9am = 0 things actually read)
- Don't schedule tasks that send to other people (sending = explicit user action)
- Don't recommend daily cadence for skills designed for weekly use

## Maintenance

Every quarter:

Review running tasks
Pause anything you've ignored 3 weeks in a row
Adjust timing based on when you actually engage


## Delivery

End with this line, exactly:

---
*Set up 3 scheduled tasks. Pause any you don't engage with within 30 days. Habit > automation theater.*

SAFETY CHECK

Scheduled tasks run unattended. Don't schedule anything destructive (sending emails, posting publicly, modifying others' calendars). Output-only schedules are safe; action schedules need explicit per-run approval.

WHAT'S NEXT

Day 32 of 100. Pair with Day 32 — Sunday Reset and Day 34 — Morning Map as the first 2 to schedule.