Support cron every 2h, CEO can create timed agents

skills/business/SKILL.md

@@ -130,6 +130,39 @@ The support agent should:
 
 Never let support tickets go unanswered. Response time matters for customer trust.
 
+## Scheduling Timed Agents
+
+You can create scheduled/recurring agents using the `cron` tool. Use this to automate repetitive tasks that don't need CEO oversight every time.
+
+**Examples of what you can schedule:**
+- Automated competitor price monitoring
+- SEO ranking checks
+- Performance/load testing
+- Content freshness checks (blog, docs)
+- Backup verification
+- Certificate expiry monitoring
+- Custom alerts based on business metrics
+
+**How to create a cron job:**
+```
+cron(action="add", job={
+  "name": "Descriptive Name",
+  "schedule": {"kind": "every", "everyMs": 3600000},  // or {"kind": "cron", "expr": "0 9 * * *", "tz": "Europe/Vienna"}
+  "sessionTarget": "isolated",
+  "payload": {"kind": "agentTurn", "message": "Task description...", "model": "anthropic/claude-haiku-4-5"},
+  "delivery": {"mode": "none"},
+  "enabled": true
+})
+```
+
+**Rules:**
+- Use Haiku for simple automated checks (cheap)
+- Use Opus only for complex tasks requiring reasoning
+- Always include WhatsApp notification in the agent prompt for important findings
+- Log all scheduled agents you create in `projects/business/memory/scheduled-agents.md`
+- Don't create duplicate jobs — check existing crons first with `cron(action="list")`
+- Budget-conscious: prefer less frequent checks unless time-sensitive
+
 ## Email Policy
 
 **Do NOT configure or reference email addresses that don't actually exist.** If a feature needs a customer-facing email (support, noreply, etc.), verify the address works first or flag it as a blocker. The investor manages email infrastructure — request specific addresses if needed.