Email Lifecycle Broadcast Planner logo

Email Lifecycle Broadcast Planner

OrganizationPopular
gooseworks-ai
email-lifecycle-broadcast-planner

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.

Overview

Publishergooseworks-ai
Repositorygoose-skills
Skill nameemail-lifecycle-broadcast-planner
Stars
1.3K
Forks
219
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by gooseworks-ai on GitHub. Read the source before you install it.

Installation

Install the Email Lifecycle Broadcast Planner AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/gooseworks-ai/goose-skills/tree/main/skills/marketing/email-lifecycle-broadcast-planner
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/gooseworks-ai/goose-skills.git /tmp/goose-skills
mkdir -p .claude/skills
cp -r /tmp/goose-skills/skills/marketing/email-lifecycle-broadcast-planner .claude/skills/email-lifecycle-broadcast-planner
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Email Lifecycle Broadcast Planner in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Email Lifecycle Broadcast Planner on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Email Lifecycle Broadcast Planner is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

broadcast-planner

Reads: 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:

  1. The month's calendar. One row per planned send: date, segment, type (value / promotional / launch / newsletter), the one idea, offer if any (from the ladder only), channel. Campaign moments come from plan-campaign's brief; the rest are filled to the approved cadence with roughly 60–70% useful sends in non-sale weeks; a pull-back week after any tentpole. Flags blackout dates and shipping cut-offs. Totals the month's sends (sequences built as broadcasts + broadcasts + newsletter, after exits) against the plan's monthly send limit; spreads the sends or proposes the upgrade.
  2. This week's sends, finished. Per send: segment and exclusions (recent purchasers, people mid-checkout flow, unengaged), send time and time-zone basis, subject + 2 alternates, preview, body, CTA with tracked URL, plain text, the test (subject, send time or offer; winner on clicks or orders; test slice size), stock confirmed for each featured product. Newsletter: slot make-content's issue (content/newsletter/<date>.md) with segment, send time and exclusions; this atom does not write the issue.
  3. SMS only for high-intent moments with SMS consent, with brand name, STOP language, quiet hours, segment count.
  4. Margin box from offer-math beside every discount.

Writes: lifecycle/calendar/<YYYY-MM>.md and lifecycle/broadcasts/<YYYY-MM-DD>.md (week starting date), plus the same in chat.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Email Lifecycle Broadcast Planner AI skill do?

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.

Why use Email Lifecycle Broadcast Planner on TypingMind?

Because you install it once and use it with any model. Email Lifecycle Broadcast Planner is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Email Lifecycle Broadcast Planner in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/gooseworks-ai/goose-skills/tree/main/skills/marketing/email-lifecycle-broadcast-planner. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Email Lifecycle Broadcast Planner?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Email Lifecycle Broadcast Planner?

As many as you like. As long as a model supports skills, you can use Email Lifecycle Broadcast Planner with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Email Lifecycle Broadcast Planner AI skill free?

Yes. It is published on GitHub by gooseworks-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇