본문으로 건너뛰기
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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고