Reactivate weekly/daily content-creation-engine delivery to Peter/Ellie/John

[Graehamwatts]

Summary

Root cause of "Peter and Ellie aren't getting the weekly/daily scripts": the delivery mechanism content-calendar/SKILL.md documents (a Cowork scheduled task, daily-content-focus-email) was never actually created — only pcfs-cma-autobuild-weekly existed under scheduled-tasks/. Meanwhile content-creation-engine/SKILL.md and production-hardening.md still pointed at an older N8N workflow (REVqxrlAb3CHJumM) that content-calendar/SKILL.md's locked "Email Delivery" section says is retired. Net effect: no weekly calendar has ever shipped to online-content/dashboards/weekly-calendars/, and the two skills disagreed about which automation was canonical.

• Add scheduled-tasks/daily-content-focus-email/SKILL.md: Monday builds and sends the weekly plan (content-calendar → weekly_overlap_check.py → weekly-calendar-builder.py → verify_output_brand.py fail-closed brand/DRE gate → publish → update_topic_history.py → send); Tue–Fri sends a short daily-focus email pulled from the live calendar. Sends via switchy-engine/scripts/send_email.py (SMTP) — not the Gmail MCP (drafts only, won't be seen) and not N8N.
• Register the task in scheduled-tasks/README.md.
• Point content-creation-engine/SKILL.md and production-hardening.md at the new scheduled task instead of the retired N8N workflow, so all three docs agree.

Functioning analysis (what I verified)

• All scripts the new task depends on parse cleanly: weekly-calendar-builder.py, weekly_overlap_check.py, update_topic_history.py, verify_output_brand.py, send_email.py.
• topic-history.json and identity.json are valid JSON.
• python3 scripts/verify_brand_identity.py passes (zero blocked DRE values in the repo).
• Found (not fixed here, out of scope): the Gmail app-password path is inconsistent across skills — send_email.py/content-calendar use Documents/Claude/Skills/gmail-app-password.txt, but past-client-follow-up-system, newsletter-generator, and farming-postcard/scripts/send_options_email.py reference Documents/Skills LLMS/Claude/Skills/gmail-app-password.txt. Doesn't block this task (it calls send_email.py directly, which has the correct path), but worth a follow-up.

Manual step still required (outside this session's reach)

This session runs in an isolated cloud container with no access to Graeham's Mac Studio or his Gmail app-password file. To actually go live:

1. On the Mac Studio: cd ~/Documents/Claude/Skills && git pull origin main && rsync -a scheduled-tasks/ ~/Documents/Claude/Scheduled/
2. Register/enable daily-content-focus-email in Cowork's scheduler at weekdays 7:30 AM PT (same place pcfs-cma-autobuild-weekly is already registered).
3. Confirm Documents/Claude/Skills/gmail-app-password.txt exists there — send_email.py fails closed with a clear error if it's missing.

Test plan

• python3 scripts/verify_brand_identity.py passes
• Modified/added Python scripts parse (ast.parse)
• JSON references (topic-history.json, identity.json) valid
• First live Monday run on the Mac Studio (can't be exercised from this session — no SMTP credentials, no Windsor/Apify connectors here)

---

Generated by Claude Code