Make Your Employee Proactive
In the Bronze tier, your employee waited for you to send a message before doing anything. Every real employee you have ever worked with eventually learned to anticipate — checking things before you ask, flagging problems before they become urgent, preparing information you will need before you need it.
This is the difference between an assistant and an employee. An assistant responds. An employee monitors, anticipates, and acts. The shift from reactive to proactive is what makes your AI employee genuinely useful rather than merely convenient.
Your challenge is to identify the single recurring task that would save you the most time if it happened automatically, then make your employee do it on a schedule.
The Challenge
Design and deploy at least one scheduled task that runs on a recurring basis (daily, weekly, or custom interval), produces domain-relevant output, and delivers it through one of your configured channels.
Acceptance Criteria
- At least one scheduled task is running and fires at the configured interval
- The task produces output that is genuinely relevant to your professional domain — not placeholder text or generic summaries
- The output uses real data from your work context (files, sources, or domain knowledge from your skill)
- You can explain why you chose this specific schedule interval and how it fits your actual work rhythm
Deliverable
Create a scheduler-config.md file in your repo documenting:
- What the task monitors or produces
- The schedule interval and why you chose it
- A sample output from at least one execution
- Your assessment of whether this output would actually save you time
Use Case Gallery
| Profession | Scheduled Task | Interval | What It Delivers |
|---|---|---|---|
| Accountant | Scan expense folder for new receipts | Daily, 8 AM | List of new items with amounts, flagging anything over $500 for manual review |
| Teacher | Compile lesson prep status for the week | Monday, 7 AM | Summary of which lessons are ready, which have gaps, and suggested priorities |
| Consultant | Summarize client project progress | Friday, 5 PM | Per-client status with hours spent, milestones hit, and overdue items highlighted |
| Doctor | Check patient follow-up schedule | Daily, 7 AM | List of patients due for follow-up, sorted by urgency, with days since last contact |
The best scheduled task is one you currently do manually on a regular basis. If you find yourself checking the same thing every morning or preparing the same report every Friday, that is your candidate.
Hints
Level 1: Where to Look
NanoClaw supports scheduled tasks through its task management system. Check the /setup documentation and the NanoClaw repository for how to configure recurring jobs. Look at how existing scheduled tasks are defined — the pattern is: specify WHAT to do, WHEN to do it, and WHERE to send the output.
Level 2: Ask Your AI
Send this to Claude or your AI employee:
"What recurring task would save me the most time if automated? I'm a [your profession]. Consider my work rhythm — when during the day or week do I most need information delivered proactively? What data source would this task need to monitor?"
Use the answer to narrow your choice before building.
Level 3: Design Framework
Break your scheduled task into four decisions:
- WHAT to monitor: The data source or condition your employee checks (a folder, a calendar, a list, a status)
- WHEN to check: The interval that matches your work rhythm (daily at 8 AM? Monday mornings? Every Friday evening?)
- WHAT to report: The output format — what information and how it is structured (bullet list? table? prioritized flags?)
- WHERE to deliver: Which channel receives the output (WhatsApp? Slack? Gmail? The channel from Connect Your Employee to the World?)
Configure the task in NanoClaw using its scheduling capabilities. Start with a short interval for testing (every few minutes), verify the output looks right, then switch to the production schedule.