New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lifecycle Messaging

by cbrock84 in cbrock84/headcount

Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them.

MITAuto-check passedMarketing & SEO

Install Lifecycle Messaging

skills CLI
$ npx skills add cbrock84/headcount --skill lifecycle-messaging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount lifecycle-messaging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/demand-generation/skills/lifecycle-messaging .claude/skills/lifecycle-messaging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lifecycle-messaging
GitHub stars
2k
Token cost
~1.2k tokens
SKILL.md length
676 words
Files
2 (incl. references)
Skills in repo
175
Repo updated
First seen
Licence
MIT

At a glance

Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them.

  • Works in 3 steps: Immediate — deliver whatever was… → Within days — the fastest route to first… → After that — the use case most people…
  • Tasks that involve Email marketing
  • SKILL.md covers Map the lifecycle before…, The welcome sequence, Timing and cadence and SMS is a different medium, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lifecycle Messaging is an agent skill from cbrock84/headcount. Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Marketing & SEO, covering Email marketing. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Email marketing

Example prompts

  • “Use the lifecycle-messaging skill to design automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement…”
  • “/lifecycle-messaging”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Immediate — deliver whatever was promised, plus the single next action.
  2. Within days — the fastest route to first value, one step.
  3. After that — the use case most people miss, or the objection most people have.

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lifecycle Messaging loads about 1.2k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 676 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~94
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 676 words, ~1,217 tokens.

Download SKILL.mdSave it as .claude/skills/lifecycle-messaging/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lifecycle-messaging
description
Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when.

Lifecycle messaging

Map the lifecycle before writing any message

For each stage, name what the person is trying to do and what would move them forward. Messages written without that answer become announcements, and announcements get unsubscribed from.

The stages that matter: just signed up, activated but not habitual, habitual, at risk, lapsed. Most programs over-invest in the first and neglect at-risk entirely, which is where the money is.

The welcome sequence

The highest-engagement messages you will ever send. Do not waste them on company history.

  1. Immediate — deliver whatever was promised, plus the single next action.
  2. Within days — the fastest route to first value, one step.
  3. After that — the use case most people miss, or the objection most people have.

Set expectations early: what you send, how often. It reduces unsubscribes more than any subject-line technique.

Timing and cadence

Trigger on behavior, not the calendar, wherever possible. A message sent because someone did something is many times more relevant than one sent because it is Tuesday.

Cadence sustainable at your worst week. Every message should be one the recipient would miss.

SMS is a different medium

Higher consent bar, higher intrusion, higher cost. Reserve it for time-sensitive and transactional messages — delivery, appointment, security, an expiring window. Marketing SMS at any volume trains people to opt out.

Explicit opt-in, honored opt-out, sending hours respected in the recipient's timezone. These are legal requirements in most jurisdictions, not preferences.

SMS compliance is not optional

Consult qualified counsel before launching an SMS program. The exposure here is statutory damages per message, which is how these become class actions.

In the US, marketing SMS requires express written consent obtained before sending — implied consent, an existing customer relationship, or a phone number collected for another purpose does not qualify. The consent record must show what the person agreed to receive and when, and it must be retained.

The operational requirements that follow:

  • Disclose program purpose, frequency, and that message rates may apply, at the point of consent.
  • Honor opt-out immediately, on every standard keyword, with a single confirmation message and nothing after it.
  • Respect quiet hours in the recipient's timezone, not yours.
  • Keep consent and opt-out records for as long as the retention rules require — these records are the entire defense if challenged.
  • Never buy or rent SMS lists. Purchased consent is not consent.

Other jurisdictions impose their own rules, and several are stricter. Determine which apply by where recipients are, not where you are.

Show full SKILL.md (264 more words)Show less

Subject lines and preview text

They are one unit and get read together. A subject line that works with the preview repeating it wastes the second-most-read text in the message — use the preview to extend the subject, not echo it, and never leave it to default to the first line of the body.

Diagnosing

  • Low open — subject line, sender reputation, or list quality. Check deliverability before rewriting subject lines; a reputation problem looks exactly like a copy problem.
  • Open but no click — the message did not deliver on the subject, or has no single clear action.
  • Click but no conversion — the destination, not the email.
  • Rising unsubscribes — frequency or relevance. Usually frequency.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Tooling

Lifecycle automation: Customer.io, Braze, Iterable, Klaviyo for commerce, HubSpot or Marketo for B2B, and similar.

Transactional sending is a separate job with separate reputation: Postmark, SendGrid, Resend, and similar. Keep it off the marketing domain.

In-product messaging: Intercom, Appcues, Pendo, and similar. An email that should have been an in-app prompt reaches half the audience at best.

Never

  • Send to a list that did not opt in.
  • Bury the unsubscribe.
  • Run a re-engagement program without a plan to actually remove the people who do not re-engage. An unengaged list damages delivery for everyone else.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/demand-generation/skills/lifecycle-messaging of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Lifecycle Messaging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lifecycle Messaging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lifecycle Messaging this skillcbrock84/headcount2k—~1.2kAutomated safety check: PassMIT
Email Sequencefreekmurze/dotfiles1k19 repos~2kAutomated safety check: PassNone
Emailscoreyhaines31/marketingskills54k1 repos~2.6kAutomated safety check: PassMIT
Onboarding Crofreekmurze/dotfiles1k16 repos~1.6kAutomated safety check: PassNone
Email SequenceLeoYeAI/openclaw-marketing-skills1k2 repos~2.1kAutomated safety check: PassCustom licence
Marketing OsYuzzyuk/marketing-os536—~2.5kAutomated safety check: PassMIT

Similar skills

  • Email Sequence

    freekmurze/dotfiles

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    1k GitHub starsUsed in 19 repos~2k tokens
    Marketing & SEOAuto-check passed

  • Emails

    coreyhaines31/marketingskills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    54k GitHub starsUsed in 1 repo~2.6k tokens
    Marketing & SEOAuto-check passed

  • Onboarding Cro

    freekmurze/dotfiles

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    1k GitHub starsUsed in 16 repos~1.6k tokens
    Marketing & SEOAuto-check passed

  • Email Sequence

    LeoYeAI/openclaw-marketing-skills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    1k GitHub starsUsed in 2 repos~2.1k tokens
    Marketing & SEOAuto-check passed

  • Marketing Os

    Yuzzyuk/marketing-os

    A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.

    536 GitHub stars~2.5k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Onboarding

    Nexus-JPF/note-companion

    When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

    870 GitHub starsUsed in 4 repos~1.6k tokens
    Marketing & SEOAuto-check passed

More from cbrock84/headcount

All 175 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 20 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 20 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 20 days ago
    Auto-check passed

  • AI Search Optimization

    cbrock84/headcount

    Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf.

    2k GitHub stars~829 tokensUpdated 20 days ago
    Auto-check passed

Categories

Questions about Lifecycle Messaging

What does Lifecycle Messaging do?

Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Lifecycle Messaging is an agent skill from cbrock84/headcount. Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them.

When should I use Lifecycle Messaging?

Lifecycle Messaging fits situations like: tasks that involve Email marketing.

How do I install Lifecycle Messaging in Claude Code?

Run `npx skills add cbrock84/headcount --skill lifecycle-messaging -a claude-code`. Or copy the skill folder (plugins/demand-generation/skills/lifecycle-messaging in cbrock84/headcount) into .claude/skills/lifecycle-messaging in your project. Claude Code loads it when a task matches its description.

How do I install Lifecycle Messaging in Codex?

Run `npx skills add cbrock84/headcount --skill lifecycle-messaging -a codex`. Or copy the skill folder (plugins/demand-generation/skills/lifecycle-messaging in cbrock84/headcount) into .agents/skills/lifecycle-messaging in your project. Codex loads it when a task matches its description.

Can I use Lifecycle Messaging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill lifecycle-messaging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lifecycle-messaging, .gemini/skills/lifecycle-messaging, .github/skills/lifecycle-messaging and .opencode/skills/lifecycle-messaging in your project.

What does Lifecycle Messaging need to run?

SKILL.md names no scripts, command-line tools or credentials: Lifecycle Messaging is instructions for the agent only.

Does Lifecycle Messaging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Lifecycle Messaging safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lifecycle Messaging use?

Lifecycle Messaging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lifecycle Messaging use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 505 tokens, read only when the agent opens those files.

What are the alternatives to Lifecycle Messaging?

Skills that share tags, products or a category with Lifecycle Messaging: Email Sequence (freekmurze/dotfiles, 1k stars), Emails (coreyhaines31/marketingskills, 54k stars), Onboarding Cro (freekmurze/dotfiles, 1k stars) and Email Sequence (LeoYeAI/openclaw-marketing-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lifecycle Messaging?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,007 GitHub stars. The repository holds 175 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.