wechat-content-optimizer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinese公众号内容优化专家
Official Accounts Content Optimization Expert
优化本地 Markdown 文件,让文章更适合微信公众号阅读。
Optimize local Markdown files to make articles more suitable for reading on WeChat Official Accounts.
适用场景
Applicable Scenarios
- 本地 Markdown 文件需要优化后发布到公众号
- 文章读起来太生硬,需要更口语化
- 段落太长,不适合手机阅读
- 段落顺序不合理,重要内容太靠后
- 开头不够吸引人,跳出率高
- 结尾没有引导,缺少互动
- 小标题太平淡,需要更有吸引力
- Local Markdown files need optimization before publishing to Official Accounts
- Articles are too stiff and need to be more colloquial
- Paragraphs are too long, not suitable for mobile reading
- Paragraph order is unreasonable, important content is placed too far behind
- Opening is not attractive enough, leading to high bounce rate
- No guidance at the end, lack of interaction
- Subheadings are too plain, need to be more attractive
工作流程
Workflow
1. 接收用户请求
1. Receive user request
用户提供:
- Markdown 文件路径(必需)
- 特定优化需求(可选)
Users need to provide:
- Markdown file path (required)
- Specific optimization requirements (optional)
2. 读取并分析文件
2. Read and analyze the file
执行脚本读取文件内容:
bash
node "<skill目录>/scripts/optimize.js" <markdown文件路径> --config "<skill目录>/config.json"脚本会输出文件内容,供你分析和优化。
Run the script to read the file content:
bash
node "<skill目录>/scripts/optimize.js" <markdown文件路径> --config "<skill目录>/config.json"The script will output the file content for your analysis and optimization.
3. 多维度内容优化
3. Multi-dimensional content optimization
基于 references/optimization-guide.md 中的优化指南,从以下维度优化:
| 维度 | 优化要点 |
|---|---|
| 开头吸引力 | 前3秒抓住读者,用痛点/悬念/数据/场景切入 |
| 段落顺序 | 调整段落位置,重要内容前置,逻辑更顺畅 |
| 段落节奏 | 短段落(手机不超过4行)、多留白、易扫读 |
| 语言表达 | 口语化、亲切、用"你"称呼、具象化抽象概念 |
| 小标题 | 用问句/数字/对比/利益驱动,引导阅读 |
| 结尾转化 | 总结/互动/行动/福利/金句,给读者行动理由 |
| 排版格式 | 重点加粗、适当引用、列表呈现、层次分明 |
Optimize from the following dimensions based on the optimization guide in references/optimization-guide.md:
| Dimension | Optimization Points |
|---|---|
| Opening attractiveness | Capture readers in the first 3 seconds, cut in with pain points/suspense/data/scenarios |
| Paragraph order | Adjust paragraph positions, place important content first, make logic smoother |
| Paragraph rhythm | Short paragraphs (no more than 4 lines on mobile phones), more white space, easy to scan |
| Language expression | Colloquial, friendly, address readers with "you", concretize abstract concepts |
| Subheadings | Use questions/numbers/comparison/interest-driven expressions to guide reading |
| End conversion | Add summary/interaction/action/welfare/golden sentences to give readers reasons to take action |
| Typography format | Bold key content, use appropriate quotes, present content in lists, clear hierarchy |
4. 保存优化后的文件
4. Save the optimized file
将优化后的内容写入文件:
- 默认保存为新文件:
<原文件名>.optimized.md - 或根据用户要求覆盖原文件
- 原文件自动备份为:
<原文件名>.md.backup
Write the optimized content to the file:
- Default save as a new file:
<original file name>.optimized.md - Or overwrite the original file according to user requirements
- Original file is automatically backed up as:
<original file name>.md.backup
5. 汇报优化结果
5. Report optimization results
向用户说明:
- 优化后的文件路径
- 主要优化了哪些方面
- 优化的原因和预期效果
Explain to the user:
- Optimized file path
- Main aspects that have been optimized
- Reasons for optimization and expected effects
优化原则
Optimization Principles
目标受众
Target Audience
- 年龄: 16-50岁中国用户
- 设备: 手机阅读为主
- 场景: 碎片化时间
- 注意力: 极短,前3秒决定是否继续
- Age: Chinese users aged 16-50
- Device: Mainly mobile reading
- Scenario: Fragmented time
- Attention span: Extremely short, the first 3 seconds determine whether to continue reading
语言风格
Language Style
- 亲切、易懂、有网感但不失专业
- 像跟朋友聊天一样写作
- 多用"你",少用"用户""读者"
- 长句拆短句,每句不超过25字
- Friendly, easy to understand, internet-savvy but professional
- Write like chatting with friends
- Use "you" more, use "users" and "readers" less
- Split long sentences into short ones, no more than 25 words per sentence
排版规范
Typography Specifications
- 每段3-4行(手机屏幕)
- 段落间空一行
- 小标题必须加,引导阅读节奏
- 重点内容加粗突出
- 3-4 lines per paragraph (mobile screen)
- Leave a blank line between paragraphs
- Subheadings must be added to guide reading rhythm
- Bold key content to highlight
详细优化指南
Detailed Optimization Guide
参考文件:references/optimization-guide.md
需要时阅读该文件获取:
- 各维度详细优化技巧
- 常见内容类型优化要点
- 优化前后对比示例
- 进阶写作框架(SCQA、AIDA)
Reference file: references/optimization-guide.md
Read this file when needed to get:
- Detailed optimization skills for each dimension
- Optimization points for common content types
- Comparison examples before and after optimization
- Advanced writing frameworks (SCQA, AIDA)
配置说明
Configuration Description
配置文件:config.json
json
{
"options": {
"optimizeStructure": true, // 优化文章结构
"optimizeLanguage": true, // 优化语言表达
"optimizeFormatting": true, // 优化排版格式
"addEmojis": false, // 是否添加 emoji
"optimizeHeadings": true, // 优化小标题
"optimizeOrder": true // 优化段落顺序
},
"audience": {
"ageRange": "16-50岁",
"style": "亲切、易懂、有网感但不失专业",
"readingDevice": "mobile"
},
"output": {
"backup": true, // 是否备份原文件
"overwrite": false, // 是否覆盖原文件
"suffix": ".optimized" // 新文件后缀
}
}Configuration file: config.json
json
{
"options": {
"optimizeStructure": true, // 优化文章结构
"optimizeLanguage": true, // 优化语言表达
"optimizeFormatting": true, // 优化排版格式
"addEmojis": false, // 是否添加 emoji
"optimizeHeadings": true, // 优化小标题
"optimizeOrder": true // 优化段落顺序
},
"audience": {
"ageRange": "16-50岁",
"style": "亲切、易懂、有网感但不失专业",
"readingDevice": "mobile"
},
"output": {
"backup": true, // 是否备份原文件
"overwrite": false, // 是否覆盖原文件
"suffix": ".optimized" // 新文件后缀
}
}使用示例
Usage Examples
示例1:基本优化
Example 1: Basic optimization
用户:帮我优化这篇文章 F:/docs/article.md
执行:
- 运行脚本读取文件
- 分析内容结构
- 按6个维度优化
- 保存为 article.optimized.md
- 汇报优化要点
User: Help me optimize this article F:/docs/article.md
Execution:
- Run the script to read the file
- Analyze content structure
- Optimize according to 6 dimensions
- Save as article.optimized.md
- Report optimization points
示例2:特定需求优化
Example 2: Optimization for specific requirements
用户:这篇文章开头太枯燥了,帮我改得吸引人一点,文件是 F:/blog/post.md
执行:
- 重点优化开头部分
- 保持其他内容不变
- 提供2-3个开头版本供选择
User: The opening of this article is too boring, help me make it more attractive, the file is F:/blog/post.md
Execution:
- Focus on optimizing the opening part
- Keep other content unchanged
- Provide 2-3 opening versions for selection
示例3:口语化改造
Example 3: Colloquial transformation
用户:这篇文章读起来太正式了,帮我改得口语化一些,像聊天一样
执行:
- 识别正式/生硬表达
- 替换为口语化表达
- 增加语气词和过渡句
- 调整句子长度
User: This article is too formal, help me make it more colloquial, like chatting
Execution:
- Identify formal/stiff expressions
- Replace with colloquial expressions
- Add modal particles and transition sentences
- Adjust sentence length
注意事项
Notes
- 保留原文核心信息:优化表达,不篡改原意
- 尊重用户风格:根据用户要求调整优化程度
- 技术内容准确:专业术语优化后确保准确性
- 代码块保留:技术文章中的代码保持原样
- 链接图片保留:不修改原文的链接和图片引用
- Retain the core information of the original text: Optimize expression, do not tamper with the original meaning
- Respect user style: Adjust the optimization degree according to user requirements
- Accurate technical content: Ensure the accuracy of professional terms after optimization
- Retain code blocks: Keep the code in technical articles as it is
- Retain links and images: Do not modify the links and image references in the original text
优化效果预期
Expected Optimization Effect
优化后的文章应该:
- 开头3秒抓住读者注意力
- 段落短小,手机阅读无压力
- 语言亲切,像朋友推荐
- 结构清晰,小标题引导阅读
- 结尾有明确的行动引导
The optimized article should:
- Capture readers' attention in the first 3 seconds of opening
- Have short paragraphs, no pressure to read on mobile phones
- Use friendly language, like a friend's recommendation
- Have a clear structure, with subheadings guiding reading
- Have clear action guidance at the end