newsletter-voice
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseNewsletter Voice
新闻通讯写作风格
Prerequisites check
前置条件检查
The moment this skill is triggered, check the project root for voice.md and about-me.md.
If either file is missing, tell the user:
Newsletter voice sits on top of your general voice profile. Run voice-builder first (upload the skill or say "build my voice"), then come back here once about-me.md and voice.md are in the project.
Then stop. Do not continue until both files exist.
If both files exist, read them fully, then go straight to Step 1.
触发该技能后,立即检查项目根目录下是否存在voice.md和about-me.md文件。
若任一文件缺失,请告知用户:
新闻通讯写作风格基于你的通用风格档案构建。请先运行voice-builder(上传该技能或说出“构建我的风格”),待about-me.md和voice.md文件出现在项目中后再返回此处。
随后停止操作。需等两个文件均存在后再继续。
若两个文件均存在,请完整读取它们,然后直接进入步骤1。
Step 1. Check for samples
步骤1:检查样本
Ask the user in chat:
Do you have 2 to 3 past newsletter issues I can learn from?Yes: paste them here (one per message or all at once) No: type "archetype" and I will build from a template tuned to your voice
Wait for response.
If the user pastes 2 or more newsletters, go to Step 2a.
If the user types "archetype", go to Step 2b.
If the user pastes 1 newsletter, ask for at least one more. If they only have one, offer: "One sample is not enough for pattern detection. Want me to switch to archetype mode and use your one newsletter as a reference point?"
在聊天中询问用户:
你是否有2-3篇过往新闻通讯刊例可供我学习参考?是:在此粘贴(每条消息一篇或一次性全部粘贴) 否:输入“原型”,我将基于适配你风格的模板构建
等待用户回复。
若用户粘贴了2篇及以上新闻通讯,进入步骤2a。
若用户输入“原型”,进入步骤2b。
若用户仅粘贴了1篇新闻通讯,请要求至少再提供一篇。若用户只有一篇,可提议:“单一样本不足以进行模式检测。是否要切换到原型模式,并将你的这篇新闻通讯作为参考依据?”
Step 2a. Sample-based analysis
步骤2a:基于样本的分析
Read every newsletter fully. Look for patterns across issues, not one-off quirks. Extract:
Opening formula
- What the first 3 sentences do (specific result, cultural observation, claim, scene, question)
- Length of the opening section before the first structural break
- Credibility move (how the author establishes authority early)
- Value promise (what the reader is told they will get)
Section structure
- Problem or contrast setup
- Named framework or free prose
- Numbered steps, methods, or continuous argument
- Examples and evidence patterns
- Bonus or extension section
- Closing formula and signoff
Data philosophy
- Specific numbers per issue (count them)
- Source attribution style (linked, named, uncredited)
- Example-to-abstraction ratio
- Limitation or failure acknowledgements
Formatting
- Header usage (frequency, hierarchy)
- List usage (numbered, bulleted, arrows)
- Bold and italic usage
- Prompt, code block, or blockquote formatting
- Visual markers (arrows, checkmarks, emojis if any)
Length
- Word count range across samples
- Section word counts
Voice markers unique to newsletter format
- Pro tips or callouts (frequency, format)
- Forward-looking closings
- Signoff phrase if consistent across samples
- Meta-transparency (does the author reflect on the process or ask for feedback)
Absence signals
- Words, constructions, or structures absent from every sample
- Closing moves the author never uses
- Topics the author never touches
Then go to Step 3.
完整阅读每一篇新闻通讯。关注多篇刊例中的共性模式,而非个别特例。提取以下内容:
开篇范式
- 开头3句话的作用(具体成果、文化观察、主张、场景、提问)
- 首次结构分段前的开篇部分长度
- 可信度构建方式(作者如何在前期建立权威)
- 价值承诺(告知读者能获得什么)
板块结构
- 问题或反差设定
- 命名框架或自由散文形式
- 编号步骤、方法或连贯论证
- 案例与证据模式
- 附加或拓展板块
- 收尾范式与签名
数据理念
- 每篇刊例中的具体数据数量(统计)
- 来源引用风格(带链接、署名、无署名)
- 案例与抽象内容的比例
- 局限性或失败案例的提及情况
格式规范
- 标题使用(频率、层级)
- 列表使用(编号、项目符号、箭头)
- 粗体与斜体使用
- 提示、代码块或引用格式
- 视觉标记(箭头、勾选框、表情符号,若有)
篇幅
- 多篇样本的字数范围
- 各板块的字数
新闻通讯特有的风格标识
- 专业提示或标注(频率、格式)
- 前瞻性收尾
- 若样本中存在统一的签名语则提取(请勿自创)
- 元透明度(作者是否会反思写作过程或征求反馈)
规避特征
- 所有样本中均未出现的词汇、句式或结构
- 作者从未使用的收尾方式
- 作者从未涉及的主题
完成后进入步骤3。
Step 2b. Archetype selection
步骤2b:原型选择
Call the AskUserQuestion tool with a single question:
json
[
{
"question": "Which newsletter archetype fits what you want to write?",
"header": "Archetype",
"multiSelect": false,
"options": [
{"label": "Data tutorial", "description": "Numbers, frameworks, step-by-step methods with prompts"},
{"label": "Contrarian essay", "description": "Take a position, defend it, name the opposition"},
{"label": "Case study teardown", "description": "One subject per issue, unpacked in depth"},
{"label": "Curated digest", "description": "5 to 7 links with your commentary each week"},
{"label": "Personal essay", "description": "Reflection on a theme, story-first"},
{"label": "Interview or profile", "description": "One person per issue, Q and A or narrative"}
]
}
]After the user picks an archetype, load the matching defaults from inside this skill folder. Tune every field using voice.md and about-me.md before writing newsletter-voice.md. Flag inside the output file that archetype defaults were used and the file should be revisited after 5 published issues.
references/archetypes.md调用AskUserQuestion工具,传入以下单个问题:
json
[
{
"question": "Which newsletter archetype fits what you want to write?",
"header": "Archetype",
"multiSelect": false,
"options": [
{"label": "Data tutorial", "description": "Numbers, frameworks, step-by-step methods with prompts"},
{"label": "Contrarian essay", "description": "Take a position, defend it, name the opposition"},
{"label": "Case study teardown", "description": "One subject per issue, unpacked in depth"},
{"label": "Curated digest", "description": "5 to 7 links with your commentary each week"},
{"label": "Personal essay", "description": "Reflection on a theme, story-first"},
{"label": "Interview or profile", "description": "One person per issue, Q and A or narrative"}
]
}
]用户选定原型后,加载本技能文件夹内中的对应默认模板。在写入newsletter-voice.md前,使用voice.md和about-me.md对所有内容进行调校。在输出文件中注明:本文件基于原型默认模板构建,发布5篇刊例后需重新审视。
references/archetypes.mdStep 3. Write newsletter-voice.md
步骤3:撰写newsletter-voice.md
Create newsletter-voice.md in the project root. Single file, 800 to 1,200 words target. Use this structure:
undefined在项目根目录创建newsletter-voice.md文件。单文件,目标字数800-1200字。采用以下结构:
undefinedNewsletter Voice
Newsletter Voice
Source
Source
[Sample-based: analysed X newsletter issues] OR [Archetype-based: [archetype name] tuned to voice.md. Revisit after 5 published issues.]
[Sample-based: analysed X newsletter issues] OR [Archetype-based: [archetype name] tuned to voice.md. Revisit after 5 published issues.]
Audience and purpose
Audience and purpose
[Who reads this newsletter and what they get from it. Written from about-me.md and voice.md. 2 to 3 sentences.]
[Who reads this newsletter and what they get from it. Written from about-me.md and voice.md. 2 to 3 sentences.]
Voice principles
Voice principles
[3 to 5 core principles the writing always holds. Each one a short declarative sentence. Tuned to this user's voice.md.]
[3 to 5 core principles the writing always holds. Each one a short declarative sentence. Tuned to this user's voice.md.]
Opening formula
Opening formula
[How issues start. Include 2 concrete templates with bracketed placeholders, e.g. "[Specific result with number]. [Credibility marker]. [Value promise for this issue]." Target word count for the opening section.]
[How issues start. Include 2 concrete templates with bracketed placeholders, e.g. "[Specific result with number]. [Credibility marker]. [Value promise for this issue]." Target word count for the opening section.]
Section flow
Section flow
[Standard structure of an issue, section by section, 5 to 8 sections max. Brief notes on what each section does and how long it runs.]
[Standard structure of an issue, section by section, 5 to 8 sections max. Brief notes on what each section does and how long it runs.]
Data and evidence
Data and evidence
[How numbers and examples are used. Specific rules, e.g. "every claim needs a number", "sources linked inline", "example-to-abstraction ratio roughly 3:1".]
[How numbers and examples are used. Specific rules, e.g. "every claim needs a number", "sources linked inline", "example-to-abstraction ratio roughly 3:1".]
Formatting rules
Formatting rules
[Headers, lists, bold, italic, code blocks, visual markers. What to use, what to avoid. Drawn from samples or archetype defaults.]
[Headers, lists, bold, italic, code blocks, visual markers. What to use, what to avoid. Drawn from samples or archetype defaults.]
Closing and signoff
Closing and signoff
[How issues end. Forward-looking statement versus summary. Signoff phrase if a consistent one exists across samples (do not invent one).]
[How issues end. Forward-looking statement versus summary. Signoff phrase if a consistent one exists across samples (do not invent one).]
What this newsletter never does
What this newsletter never does
[1 short paragraph or 3 to 5 items. Drawn from absence patterns across samples or archetype defaults. Behaviours only, not a banned-words list.]
[1 short paragraph or 3 to 5 items. Drawn from absence patterns across samples or archetype defaults. Behaviours only, not a banned-words list.]
Length
Length
[Word count target for standard issues. Separate target for longer comprehensive guides if the user writes both formats.]
Fill every section from the samples (or tuned archetype defaults). No generic filler. If the samples do not cover something, say "no clear pattern across samples" rather than guessing.[Word count target for standard issues. Separate target for longer comprehensive guides if the user writes both formats.]
从样本(或调校后的原型默认模板)中提取内容填充每个板块。禁止使用通用套话。若样本未覆盖某部分内容,请注明“样本中未发现明确模式”,切勿猜测。Step 4. Confirm and hand off
步骤4:确认与交付
Tell the user:
Your newsletter voice is built. newsletter-voice.md is in your project root alongside about-me.md and voice.md. When you want to draft an issue, say "write a newsletter" and I will use all three files together.[If archetype mode: Remember this file was built from archetype defaults. After 5 or so published issues, re-run this skill with your real samples for a sharper profile.]
告知用户:
你的新闻通讯写作风格已构建完成。newsletter-voice.md文件已存放在项目根目录,与about-me.md和voice.md并列。当你想要撰写刊例时,说出“写一篇新闻通讯”,我将结合这三个文件进行创作。[若为原型模式:请注意本文件基于原型默认模板构建。发布约5篇刊例后,可上传真实样本重新运行该技能,以生成更精准的风格档案。]
What this skill produces
该技能产出
One file in the project root:
- newsletter-voice.md: newsletter-specific writing instructions covering audience, voice principles, opening formula, section flow, data philosophy, formatting, closing, absence patterns, and length targets
项目根目录下的一个文件:
- newsletter-voice.md:针对新闻通讯的写作指令,涵盖受众、风格原则、开篇范式、板块流程、数据理念、格式规范、收尾方式、规避特征及篇幅目标
Rules
规则
- Require voice.md and about-me.md in the project root before running. Stop and redirect to voice-builder if either is missing.
- Minimum 2 newsletter samples if the user chooses sample-based mode. Offer archetype mode if fewer.
- Keep newsletter-voice.md under 1,200 words. Tight beats exhaustive.
- Do not invent voice signals. Work only from samples or archetype defaults tuned to voice.md.
- Do not duplicate content from voice.md. Reference it where relevant. newsletter-voice.md adds newsletter-specific rules only.
- Do not bake in the user's specific names, URLs, or signoff phrases unless they appear consistently across 2 or more samples.
- Do not produce a separate voice or banned-words file. Absence patterns live inside newsletter-voice.md as a single section.
- British English throughout unless samples are clearly American.
- Never use em dashes in any output file or in any draft.
- 运行前需确保项目根目录存在voice.md和about-me.md文件。若任一文件缺失,停止操作并引导用户先运行voice-builder。
- 若用户选择基于样本的模式,需至少提供2篇新闻通讯样本。若样本不足,提供原型模式选项。
- newsletter-voice.md文件字数需控制在1200字以内。简洁优先于详尽。
- 请勿自创风格标识。仅基于样本或经voice.md调校后的原型默认模板进行操作。
- 请勿重复voice.md中的内容。仅在相关处引用。newsletter-voice.md仅添加新闻通讯专属规则。
- 除非在2篇及以上样本中均出现,否则请勿加入用户的特定姓名、网址或签名语。
- 请勿生成单独的风格或禁用词汇文件。规避特征需作为单个板块包含在newsletter-voice.md中。
- 全程使用英式英语,除非样本明确为美式英语。
- 在任何输出文件或草稿中均不得使用破折号。