Skip to content
FunCoding

Search

Search docs, Skills and MCP

lifecycle-messaging

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.

AI 与智能体2kplugins/demand-generation/skills/lifecycle-messaging/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/cbrock84/headcount/lifecycle-messaging/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

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.

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.

Similar Skills

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI & agents

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI & agents

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI & agents

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI & agents

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI & agents

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI & agents