Step of the email-lifecycle playbook: builds the month's send calendar and writes this week's email and SMS broadcasts against the approved cadence and segments. Run email-lifecycle instead; not for direct use.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/marketing/email-lifecycle-broadcast-planner/SKILL.mdReads: make-content's next newsletter issue if any; ../email-lifecycle/references/segments-cadence-offers.md, ../email-lifecycle/references/copy-craft.md, ../email-lifecycle/references/sms-push-whatsapp.md, ../email-lifecycle/references/modes-and-incidents.md (seasonal); the approved cadence and segments from lifecycle/program.md; the brand's promotional calendar and launch dates (brain or asked); campaign records with an email/SMS leg via gooseworks:campaign_read; last week's results from the latest reports/performance/*.md; stock for every product it will feature (asked if the brain does not hold it).
Does:
content/newsletter/<date>.md) with segment, send time and exclusions; this atom does not write the issue.Writes: lifecycle/calendar/<YYYY-MM>.md and lifecycle/broadcasts/<YYYY-MM-DD>.md (week starting date), plus the same in chat.
gooseworks-ai/goose-skills
885edb5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.