跳到正文
cccskills
免费在 GitHub 公开

nurture-sequence-build-and-readout

Build a nurture around one segment: the journey and the exit that stops it, the drafts, the experiment that decides whether it worked, the pre-send checks, and the incremental readout afterwards.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Nurture sequence build and readout

Use this when someone wants a sequence, a lifecycle journey or a re-engagement series for a specific segment. If a lifecycle map already says which emails should exist, build inside it; if none exists, name the stages you are assuming in one line so the owner can correct them before anything is written.

Map the journey before you write

Name the stage this segment sits in, the one action that moves them out of it, and the touches that earn it:

  • Three to five for a short run at a warm segment.
  • Six to eight for a cold one.
  • A twelve-week program for ongoing warm nurture.

Then name the exit in one line: what stops the sequence for someone who converts. A sequence with no exit does not ship.

Segment tight

One sequence per segment and stage. A blast wearing a nurture costume is still a blast. Write who is in and who is out, one line each, and say how you know which is which.

Draft each email

One goal, one ask, a subject under 50 characters, a first line that does real work. Every claim carries a number or a source or it gets cut. Missing facts stay marked in the draft rather than getting filled in.

Set the experiment before anything sends

  • The control against the variant, changing one thing.
  • The single metric that decides it.
  • A holdout when the list is big enough to afford one.
  • The sample you need and how long to wait for it.

Decide this first. An experiment designed after the results is a story.

Check the build, then the domain

Links, names, dates, the unsubscribe line and the reply-to address. Read every draft back once looking for the segment's name in the wrong place. Then the domain side: Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM) and Domain-based Message Authentication (DMARC) all passing, spam-score and rendering previews clean, and bounce and complaint watch switched on before the first send rather than after it.

Launch on a yes, then report incrementally

Delivered, bounced, clicked, replied, converted, meetings booked, and the lift against the holdout or the prior baseline. Opens are a deliverability health check only — mail privacy features preload images and inflate them, so nothing gets scored on opens. Judge rates against benchmarks for the send type: cold, warm and customer sends never share a target. Name the send time and frequency behind each touch. Label every line FACT, INFERENCE or UNKNOWN.

What not to do

Never send, schedule or upload a list without a yes. Never invent an open rate, a click rate or a conversion to fill a readout. Never re-send to an address that has bounced twice — suppress it.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

查看 Significant-Gravitas 的全部技能

报告此技能的问题