Cron specs for the recurring marketer skills. Wire each via the bridge /schedule skill — do not invent a separate scheduler.
- When: Monday–Friday, 08:00 ET (
0 13 * * 1-5in UTC) - Action: invoke
daily-briefingskill in this harness - Destination: post to
#marketer(general — informational) - Stub behavior (v0): writes to
assets/outbox/{YYYY-MM-DD}-daily-briefing.mduntil Slack auth is wired
- When: Friday, 16:00 ET (
0 21 * * 5in UTC) - Action: invoke
week-in-reviewskill in this harness - Destination: post to
#marketer-approve(gated — owner reviews before any external sharing) - Stub behavior (v0): writes to
assets/outbox/{YYYY-WNN}-week-in-review.mduntil Slack auth is wired
- When: every other Tuesday, 10:00 ET — commented out until v1, costs cycles to keep noisy
- Action: invoke
competitor-scanskill - Destination: post battlecards diff to
#marketer-approve
From the bridge root, invoke the bridge's /schedule skill with each spec above. The skill creates a remote agent that fires on cron and runs the named routine.
Each routine should pass:
- the working directory (
modules/marketer/) - the skill name to invoke
- the destination channel for the output
When auth is missing, routines should still produce drafts to assets/outbox/ and log a note: integration not wired — output is local draft only line in the file header. Don't fail loud; degrade gracefully.
A health check belongs in the Friday week-in-review output: which routines fired, which produced output, which silently failed. If a routine has been missing for 3+ days, surface it.
Nathanael Wolfe. Schedule changes (timing, destination, frequency) require owner approval — post to #marketer-approve with the proposed change before editing this file.