Newsletter Creation & Curation Skill

新闻通讯创建与策划Skill

Use this skill to create B2B newsletters that match business context, not generic content templates.

Deep strategic guidance is in

PLAYBOOK.md

. Use this file as the executable operating manual.

使用该Skill创建贴合业务场景的B2B新闻通讯，而非通用内容模板。

深度战略指引请查看

PLAYBOOK.md

。请将此文件作为可执行操作手册使用。

Mode

Detect from context or ask: "Outline only, full edition, or full edition + calendar?"

Mode	What you get	Best for
`quick`	Edition outline + 3 lead story angles, no writing	Planning, editorial direction
`standard`	Full newsletter edition, all sections written	Publishing this week
`deep`	Full edition + 4-week content calendar + audience segmentation recommendations	Launching or systematizing a newsletter

Default:
standard
— use

quick

if they're still deciding what to write. Use

deep

if they're building a newsletter from scratch or scaling.

根据上下文判断或询问："仅大纲、完整刊期，还是完整刊期+日历？"

Mode	输出内容	适用场景
`quick`	刊期大纲 + 3个头条故事方向，不撰写内容	规划、编辑方向确定
`standard`	完整新闻通讯刊期，所有版块已撰写完成	本周发布
`deep`	完整刊期 + 4周内容日历 + 受众细分建议	启动或系统化新闻通讯项目

默认模式：
standard
— 若用户仍在确定写作内容，使用

quick

模式；若用户从零搭建或规模化新闻通讯，使用

deep

模式。

Context Loading Gates

Before generating any newsletter content, collect:

Company context: What product/service? Who is the ICP?
Newsletter goal: Lead gen / thought leadership / personal brand / category ownership
Industry vertical: Sales Tech / HR Tech / Fintech / Operations Tech
Company stage: Series A / Series B / Series C+
Role: Founder / VP-Director / PMM-Content / Enterprise employee
Geography: US-first / India-first
Prior issues: Any existing issues to maintain consistency and voice?
Approval constraints: Does this need legal/brand/manager review?

Structured intake — answer all 5 dimensions before proceeding:

Goal: [lead_gen | thought_leadership | personal_brand | category_ownership]
Industry: [sales_tech | hr_tech | fintech | ops_tech]
Stage: [series_a | series_b | series_c_plus]
Role: [founder | vp_director | pmm_content | enterprise_employee]
Geography: [us_first | india_first]

生成任何新闻通讯内容前，请收集以下信息：

企业背景： 提供何种产品/服务？理想客户画像（ICP）是谁？
新闻通讯目标： 获客（Lead gen）/ 思想领导力打造 / 个人品牌建设 / 品类主导权抢占
行业垂直领域： Sales Tech / HR Tech / Fintech / Operations Tech
企业阶段： Series A / Series B / Series C+
角色： Founder / VP-Director / PMM-Content / 企业员工
地域侧重： US-first / India-first
过往刊期： 是否有已发布的刊期以保持内容一致性和风格？
审批限制： 是否需要法务/品牌/经理审核？

结构化信息收集 — 完成以下5个维度的回答后再继续：

Goal: [lead_gen | thought_leadership | personal_brand | category_ownership]
Industry: [sales_tech | hr_tech | fintech | ops_tech]
Stage: [series_a | series_b | series_c_plus]
Role: [founder | vp_director | pmm_content | enterprise_employee]
Geography: [us_first | india_first]

Phase 1: Context Analysis

Phase 1：背景分析

Before drafting, reason through:

Template match: Which industry template best fits? (Sales Tech = data-heavy; HR Tech = research-led; Fintech = compliance-aware; Ops Tech = practical)
Cadence match: Series A = weekly/bi-weekly for simplicity; Series B = weekly with process; Series C+ = media-grade weekly with pillars
Role constraints: Founder = direct POV allowed; Employee = approval checkpoint required before final draft
Geography adjustments: India-first = IST timing + local examples; US-first = EST/PST + US benchmarks
Goal-content alignment: Lead gen needs a clear conversion CTA; thought leadership needs original insight, not general content

Output one-line strategy statement:

For [ICP], we publish [cadence] to achieve [goal] with [format].

开始撰写前，请梳理以下内容：

模板匹配： 哪种行业模板最适配？（Sales Tech = 重数据；HR Tech = 研究导向；Fintech = 合规优先；Ops Tech = 实用导向）
发布频次匹配： Series A阶段 = 每周/双周，保持简洁；Series B阶段 = 每周发布，具备流程化内容；Series C+阶段 = 媒体级每周发布，拥有固定栏目
角色限制： Founder = 可使用直接观点；员工 = 终稿前需经过审批节点
地域调整： India-first = 采用IST时区 + 本地案例；US-first = 采用EST/PST时区 + 美国行业基准
目标-内容对齐： 获客目标需要明确的转化CTA；思想领导力打造需要原创见解，而非通用内容

输出一句话战略声明：

For [ICP], we publish [cadence] to achieve [goal] with [format].

Phase 2: Issue Blueprint

Phase 2：刊期蓝图

Before writing full draft, produce an issue blueprint:

markdown

undefined

撰写完整草稿前，请生成刊期蓝图：

markdown

undefined

Issue Blueprint

Strategy: For [ICP], [cadence] to achieve [goal]. Industry tone: [tactical/research-led/compliance-aware/practical] Approval required: [yes/no — who]

Sections:

Subject lines (3 options) — [~words each]
Hook — [target ~75 words]
Core insight — [target ~200 words]
Actionable playbook — [target ~150 words, 3-5 steps]
CTA — [1 sentence, singular action]


Get confirmation or proceed to draft.

---

Strategy: For [ICP], [cadence] to achieve [goal]. Industry tone: [tactical/research-led/compliance-aware/practical] Approval required: [yes/no — who]

Sections:

Subject lines (3 options) — [~words each]
Hook — [target ~75 words]
Core insight — [target ~200 words]
Actionable playbook — [target ~150 words, 3-5 steps]
CTA — [1 sentence, singular action]


获得确认后再开始撰写草稿。

---

Phase 3: Full Issue Draft

Phase 3：完整刊期草稿

Generate complete publish-ready draft. Required structure — every issue:

生成可直接发布的完整草稿。每期必须包含以下结构：

Subject Line Options (3 required)

主题选项（需提供3个）

Produce 3 distinct angles:

A: Curiosity/open loop ("The metric most [ICP] ignore")
B: Specific + benefit ("How [Company type] achieves [X] in [timeframe]")
C: Contrarian/bold ("Stop [common behavior]. Do this instead.")

提供3种不同角度：

A: 好奇心/开放式（"The metric most [ICP] ignore"）
B: 具体+利益导向（"How [Company type] achieves [X] in [timeframe]"）
C: 反常识/大胆式（"Stop [common behavior]. Do this instead."）

Hook

开篇钩子

First 2 sentences must earn the read
Lead with the problem + stakes
Target: busy reader can extract the point in 60 seconds

前两句话必须抓住读者注意力
以问题+影响开篇
目标：忙碌的读者能在60秒内get核心要点

Core Insight

核心见解

One primary takeaway per issue — not three
Support with: data, framework, or named pattern
Include specific numbers or named examples wherever possible

每期仅一个核心结论，而非三个
需辅以：数据、框架或知名模式
尽可能包含具体数字或知名案例

Actionable Playbook

可执行操作指南

3-5 steps or checklist items
Each step must be implementable, not just conceptual
Series A = simpler steps; Series C+ = more sophisticated process

3-5个步骤或清单项
每个步骤必须可落地，而非仅停留在概念层面
Series A阶段 = 步骤更简单；Series C+阶段 = 流程更复杂精细

CTA

CTA（行动号召）

ONE measurable action only
Options: reply with [X], click [link], share [asset], book [demo]
Never use vague CTAs ("Learn more")

仅包含一个可衡量的行动
可选行动：回复[X]、点击[链接]、分享[资产]、预约[演示]
切勿使用模糊的CTA（如“了解更多”）

Phase 4: Refinement Checklist

Phase 4：优化检查清单

Run before delivering:

```
Clarity
```
: Can a busy reader extract value in 60 seconds?
```
Specificity
```
: Does each section include concrete guidance or evidence?
```
Relevance
```
: Does tone match industry and role constraints?
```
Compliance
```
: For fintech/employee-led, is a legal/manager review step included?
```
Consistency
```
: Does voice align with prior issues (if any were provided)?
```
CTA
```
: Is there exactly ONE measurable CTA — not two, not zero?

交付前需完成以下检查：

```
Clarity
```
: 忙碌的读者能否在60秒内获取价值？
```
Specificity
```
: 每个版块是否包含具体指导或证据？
```
Relevance
```
: 风格是否符合行业和角色限制？
```
Compliance
```
: 针对Fintech/员工主导的内容，是否包含法务/经理审核步骤？
```
Consistency
```
: 风格是否与过往刊期（如有）保持一致？
```
CTA
```
: 是否仅包含一个可衡量的行动号召，不多不少？

Phase 5: Self-Critique Pass (REQUIRED)

Phase 5：自我审核环节（必填）

After completing the draft, evaluate:

Does the subject line A option create genuine curiosity without being clickbait?
Does the hook deliver a problem + stakes in the first 2 sentences?
Is the core insight something subscribers couldn't get from a generic AI prompt?
Does the playbook have steps that are specific to this audience, not generic "tips"?
Is the CTA actually measurable — i.e., can they track whether it worked?
For fintech/employee contexts: is there an explicit approval checkpoint?

Flag any issue: "The playbook steps are too generic for a Series B SaaS audience — they read as beginner content. Revised to assume existing process maturity."

完成草稿后，需评估以下内容：

主题选项A是否能真正引发好奇心，而非标题党？
开篇钩子是否在前两句话中呈现了问题+影响？
核心见解是否是订阅者无法通过通用AI提示词获得的内容？
操作指南的步骤是否针对该受众定制，而非通用“小贴士”？
CTA是否真正可衡量——即能否追踪其效果？
针对Fintech/员工场景：是否包含明确的审批节点？

标记任何问题："The playbook steps are too generic for a Series B SaaS audience — they read as beginner content. Revised to assume existing process maturity."

Iteration Protocol

迭代流程

After delivering the draft:

Ask: "Does the hook earn the read? Does the playbook feel actionable for your audience?"
If hook is weak → rewrite using a different angle (data-led, story-led, or contrarian)
If playbook is too generic → ask for a specific example from their own experience to ground it
For next issue: "Want me to save these content themes so the next issue builds on this one?"

交付草稿后：

询问："开篇钩子是否能抓住读者注意力？操作指南对您的受众来说是否具备可执行性？"
若钩子吸引力不足 → 改用其他角度重写（数据导向、故事导向或反常识）
若操作指南过于通用 → 请用户提供自身经历中的具体案例，以内容更贴合实际
针对下一期："需要我保存这些内容主题，以便下一期在此基础上拓展吗？"

Output Structure

输出结构

markdown

undefined

markdown

undefined

Newsletter Issue: [Name] — Issue #[X] — [Date]

Strategy: For [ICP], [cadence] to achieve [goal].

Subject Line Options

A) [Curiosity/open loop] B) [Specific + benefit]
C) [Contrarian/bold] Recommended: [A/B/C] — [reason]

Hook

[2-3 sentences — problem + stakes]

Core Insight

[200-300 words — data, framework, or named pattern]

Actionable Playbook

[Step]
[Step]
[Step]

[Step]
[Step]
[Step]

CTA

[Single measurable action]

Distribution Plan

Send time: [Day, Time, Timezone]
LinkedIn amplification: [Post angle / hook]
Secondary channel: [Platform + angle]

Send time: [Day, Time, Timezone]
LinkedIn amplification: [Post angle / hook]
Secondary channel: [Platform + angle]

KPI Targets

Open rate goal: [%]
CTR goal: [%]
Primary metric: [SQLs / subscribers / replies]

Open rate goal: [%]
CTR goal: [%]
Primary metric: [SQLs / subscribers / replies]

Approval Required

[Yes — [who] | No]

Self-Critique Notes

[Issues flagged + revisions made]

---

[Issues flagged + revisions made]

---

Playbook Map (Deep Dives in

PLAYBOOK.md

)

操作手册地图（深度内容请查看

PLAYBOOK.md

）

Sales Tech strategy:
```
SECTION A
```
HR Tech strategy:
```
SECTION B
```
Fintech strategy:
```
SECTION C
```
Operations Tech strategy:
```
SECTION D
```
Role approvals and geography tactics:
```
CROSS-CUTTING: UNIVERSAL FRAMEWORKS
```

Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com

Sales Tech策略:
```
SECTION A
```
HR Tech策略:
```
SECTION B
```
Fintech策略:
```
SECTION C
```
Operations Tech策略:
```
SECTION D
```
角色审批与地域策略:
```
CROSS-CUTTING: UNIVERSAL FRAMEWORKS
```

Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com

newsletter-creation-curation

Original

Translation

Newsletter Creation & Curation Skill

新闻通讯创建与策划Skill

Mode

Mode

Context Loading Gates

Context Loading Gates

Phase 1: Context Analysis

Phase 1：背景分析

Phase 2: Issue Blueprint

Phase 2：刊期蓝图

Issue Blueprint

Issue Blueprint

Phase 3: Full Issue Draft

Phase 3：完整刊期草稿

Subject Line Options (3 required)

主题选项（需提供3个）

Hook

开篇钩子

Core Insight

核心见解

Actionable Playbook

可执行操作指南

CTA

CTA（行动号召）

Phase 4: Refinement Checklist

Phase 4：优化检查清单

Phase 5: Self-Critique Pass (REQUIRED)

Phase 5：自我审核环节（必填）

Iteration Protocol

迭代流程

Output Structure

输出结构

Newsletter Issue: [Name] — Issue #[X] — [Date]

Newsletter Issue: [Name] — Issue #[X] — [Date]

Subject Line Options

Subject Line Options

Hook

Hook

Core Insight

Core Insight

Actionable Playbook

Actionable Playbook

CTA

CTA

Distribution Plan

Distribution Plan

KPI Targets

KPI Targets

Approval Required

Approval Required

Self-Critique Notes

Self-Critique Notes

Playbook Map (Deep Dives in PLAYBOOK.md)

操作手册地图（深度内容请查看PLAYBOOK.md）

Playbook Map (Deep Dives in
`PLAYBOOK.md`
)

操作手册地图（深度内容请查看
`PLAYBOOK.md`
）