content-newsletter-draft · diff
git:20260609.fb3d951 to git:20260616.fca2023
7 added, 7 removed. Audit A to A.
---
name: content-newsletter-draft
sheetId: "1.06"
description: >-
- Drafts Peter's weekly Chinese newsletter from the user's article outline or topic idea, shaping it into a structured handoff for the /write-article pipeline. Use this skill whenever Peter says "幫我寫電子報", "來寫電子報", "寫newsletter", "電子報大綱", or shares a topic/outline and wants it shaped into a newsletter. Trigger even if Peter only gives a rough idea — the skill will structure it into a full outline.
+ Drafts Peter's weekly Chinese newsletter from the user's article outline or topic idea, shaping it into a structured handoff for the /zynkr-content-writer pipeline. Use this skill whenever Peter says "幫我寫電子報", "來寫電子報", "寫newsletter", "電子報大綱", or shares a topic/outline and wants it shaped into a newsletter. Trigger even if Peter only gives a rough idea — the skill will structure it into a full outline.
category: brand-marketing
project: content-newsletter-draft
platform: claude
status: Done
author: Peter Tu
input: "Peter's article outline, topic, or rough idea for the weekly newsletter"
- process: "Shape the outline/topic into a structured weekly-newsletter outline and hand it off to the /write-article pipeline"
- output: "A structured newsletter outline ready for the /write-article drafting pipeline"
+ process: "Shape the outline/topic into a structured weekly-newsletter outline and hand it off to the /zynkr-content-writer pipeline"
+ output: "A structured newsletter outline ready for the /zynkr-content-writer drafting pipeline"
synergy: []
---
# Write Newsletter
Peter writes a weekly Chinese newsletter for career professionals and AI practitioners. The newsletter's strength is that Peter doesn't just theorize — he shows real things he's been building and learning.
The single ingredient is the **central theme** — Peter's outline or topic idea.
---
## Step 1: Get the article outline
If Peter has already shared an outline or topic in this conversation, extract it now.
If not, ask: "你這週想寫什麼主題？給我一個大綱或幾個關鍵想法就好。"
---
## Step 2: Shape the outline
Before writing, develop the topic into a structured outline:
- What's the core insight or argument of this issue?
- What concrete example or story makes it land for readers?
- What should readers do or take away by the end?
A clear through-line is what makes the newsletter feel alive rather than generic.
---
- ## Step 3: Hand off to /write-article
+ ## Step 3: Hand off to /zynkr-content-writer
- At this point we have a structured outline with key points per section. This is exactly **Stage 2** entry point for the `/write-article` pipeline.
+ At this point we have a structured outline with key points per section. This is exactly **Stage 2** entry point for the `/zynkr-content-writer` pipeline.
- Package the outline into a handoff summary in this format, then invoke `/write-article`:
+ Package the outline into a handoff summary in this format, then invoke `/zynkr-content-writer`:
```
## Newsletter Handoff Summary
**Central theme:** [one sentence]
**Confirmed structure:** [structure name, e.g. Problem → Insight → Application → CTA]
**Section key points:**
1. [Section title] — [2–3 bullet points]
2. [Section title] — [2–3 bullet points]
3. [Section title] — [2–3 bullet points]
4. CTA — [3 specific actions]
```
- Then say: "我已經整理好大綱，交給 /write-article 開始撰寫。" and invoke `/write-article` with the handoff summary as the argument — it will enter at Stage 2 (content-draft) and run the full writing pipeline from there.
+ Then say: "我已經整理好大綱，交給 /zynkr-content-writer 開始撰寫。" and invoke `/zynkr-content-writer` with the handoff summary as the argument — it will enter at Stage 2 (content-draft) and run the full writing pipeline from there.