Optimize local Markdown files to make articles more suitable for reading on the WeChat official account.
Applicable scenarios
- Local Markdown files need to be optimized before being published to the WeChat official account
- The article reads too stiffly and needs to be more conversational
- Paragraphs are too long and not suitable for mobile reading
- Paragraph order is unreasonable, and important content is too far back
- The opening is not attractive enough, and the bounce rate is high
- The ending has no guidance and lacks interaction
- Subheadings are too plain and need to be more attractive
Workflow
1. Receive user request
The user provides:
- Markdown file path (required)
- Specific optimization needs (optional)
2. Read and analyze the file
Run the script to read the file content:
node "<skill目录>/scripts/optimize.js" <markdown文件路径> --config "<skill目录>/config.json"
The script will output the file content for you to analyze and optimize.
3. Multi-dimensional content optimization
Based on the optimization guide in references/optimization-guide.md, optimize from the following dimensions:
| Dimension | Optimization points |
|---|---|
| Opening appeal | Capture readers in the first 3 seconds, using pain points/suspense/data/scenarios as the entry point |
| Paragraph order | Adjust paragraph positions, put important content first, and make the logic smoother |
| Paragraph rhythm | Short paragraphs (no more than 4 lines on mobile), more white space, easy to scan |
| Language expression | Conversational, friendly, use "you" to address the reader, and make abstract concepts concrete |
| Subheadings | Use questions/numbers/comparisons/benefit-driven wording to guide reading |
| Ending conversion | Summary/interaction/action/benefits/memorable quotes, giving readers a reason to act |
| Formatting | Bold key points, appropriate quotations, list presentation, and clear hierarchy |
4. Save the optimized file
Write the optimized content into the file:
- By default, save as a new file:
<原文件名>.optimized.md - Or overwrite the original file according to user requirements
- The original file is automatically backed up as:
<原文件名>.md.backup
5. Report optimization results
Explain to the user:
- The optimized file path
- Which aspects were mainly optimized
- The reasons for the optimization and the expected effect
Optimization principles
Target audience
- Age: Chinese users aged 16-50
- Device: Mainly mobile reading
- Scenario: Fragmented time
- Attention: Extremely short, the first 3 seconds determine whether they continue
Language style
- Friendly, easy to understand, with internet flavor but still professional
- Write as if chatting with a friend
- Use "you" more, and use "user" and "reader" less
- Split long sentences into short ones, with each sentence no more than 25 characters
Formatting standards
- 3-4 lines per paragraph (mobile screen)
- Leave a blank line between paragraphs
- Subheadings must be added to guide the reading pace
- Key contentBoldHighlight
Detailed optimization guide
Reference file: references/optimization-guide.md
Read this file when needed to obtain:
- Detailed optimization techniques for each dimension
- Key optimization points for common content types
- Before-and-after optimization comparison examples
- Advanced writing frameworks (SCQA, AIDA)
Configuration instructions
Configuration file: config.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
Example 1: Basic optimization
User: Help me optimize this article F:/docs/article.md
Execution:
- Run the script to read the file
- Analyze the content structure
- Optimize according to the 6 dimensions
- Save as article.optimized.md
- Report the optimization key points
Example 2: Optimization for specific needs
User: This article's opening is too boring, help me make it more engaging, the file is F:/blog/post.md
Execution:
- Focus on optimizing the opening
- Keep other content unchanged
- Provide 2-3 opening versions for selection
Example 3: Conversational transformation
User: This article reads too formally, help me make it more conversational, like chatting
Execution:
- Identify formal/stiff expressions
- Replace with conversational expressions
- Add interjections and transitional sentences
- Adjust sentence length
Precautions
- Preserve the core information of the original text: Optimize the expression without altering the original meaning
- Respect the user's style: Adjust the degree of optimization according to the user's requirements
- Technical content must be accurate: Ensure accuracy after optimizing professional terminology
- Preserve code blocks: Keep the code in technical articles as is
- Preserve links and images: Do not modify the links and image references in the original text
Expected optimization results
The optimized article should:
- Capture the reader's attention in the first 3 seconds
- Short paragraphs, no pressure for mobile reading
- Friendly language, like a friend's recommendation
- Clear structure, subheadings guide reading
- Clear call to action at the end