WeChat Official Account Writer

能完成什么

这个 skill 面向微信公众号创作者、技术博主、AI 资讯号、产品团队和内容运营，能把一个主题、一段素材、一个链接或一组 AI 热点整理成可发布的公众号草稿。

典型任务：

• 从一句话主题生成公众号标题、大纲、正文和结尾。
• 把英文/中文链接翻译、消化、重组为原创中文公众号文章。
• 把 AI 新闻、AI HOT 条目、产品发布、技术资料改写成适合公众号阅读的内容。
• 为技术文章生成架构图、流程图、系统图等正文插图方案。
• 使用 image2/imagegen 生成封面图和正文插图，而不是静态 SVG 模板。
• 输出微信安全 HTML 和上传 JSON，并调用内置上传器创建微信公众号草稿箱条目。
• 做发布前检查，识别标题夸张、事实缺口、敏感表述、排版问题和读者理解断点。

Operating Principle

Produce publishable Chinese public-account drafts, not generic essays. Optimize for a clear reader promise, a strong opening, skimmable structure, concrete examples, restrained claims, useful images, and clean output that can be pasted into an editor or sent to the bundled WeChat draft uploader.

Default to Chinese unless the user asks otherwise. Preserve user-provided facts, names, product details, quotes, and constraints exactly. Do not invent data, endorsements, customer cases, policy claims, or source links.

Workflow

1. Identify the article job:

   • From scratch: turn a topic or rough idea into titles, outline, and draft.
   • Material rewrite: transform notes, reports, transcripts, web pages, or bullet points into an article.
   • Link translation/rewrite: extract the source idea, translate only what is necessary, then reorganize into an original Chinese article with commentary.
   • Polish: improve an existing draft for clarity, flow, headline strength, and WeChat readability.
   • Illustrate: plan or generate a cover and body images.
   • Upload prep: produce the bundled wechat-article-workbench JSON format and run validation/draft commands when requested.
   • Review: find weak logic, risky claims, unsupported facts, tone problems, and publishing friction.

2. Ask at most two clarifying questions only when missing information would materially change the article:

   • target readers
   • intended angle or goal
   • article length
   • brand/persona voice
   • hard facts or materials that must be used

   If the user wants momentum or gives enough context, make reasonable assumptions and state them briefly before drafting.

3. Shape the article before writing:

   • Define one reader promise in one sentence.
   • Choose one primary angle, not a list of loosely related points.
   • Draft 8-12 title options when title ideation is requested or useful.
   • Build a section outline with each section answering one reader question.

4. Write the draft:

   • Open with a concrete scene, contrast, recent change, or direct reader pain.
   • Avoid empty throat-clearing such as "在当今时代" and "随着互联网的发展".
   • Use short paragraphs, visible section headings, and examples.
   • Keep claims proportional to evidence.
   • End with a clear takeaway, question, checklist, or action, depending on the article type.

5. Package for publishing:

   • Provide a final recommended title.
   • Provide 3-5 alternate titles when useful.
   • Provide a one-sentence summary or abstract if the user may need it.
   • Provide Markdown body unless the user asks for upload prep or draft-box upload.
   • For draft-box upload, provide or write WeChat-safe HTML JSON matching the bundled scripts/wechat-article-workbench uploader.
   • For draft-box upload, use image generation for the cover by default and save the final image to the local project before drafting.
   • For body images, use image generation whenever an illustration materially improves the article.
   • Add a "发布前检查" section only when doing review or when the article contains facts, sensitive claims, or business persuasion.

Image Generation

For draft-box upload, always generate a model-based cover image first. Use the imagegen skill/tool, which should route to the available image2/imagegen path. Save project-bound images under the bundled uploader's data/images/ directory and reference them from the generated article JSON.

Default assets:

• Cover: one horizontal editorial image based on the article title, core argument, and emotional or technical theme. Avoid embedded title text unless the user explicitly asks for it; image text often renders poorly.
• Body images: 1-3 generated images when they clarify the article. For technical topics, prefer polished architecture diagrams, workflow visuals, system maps, product scenes, timelines, or concept diagrams. For non-technical topics, prefer editorial illustrations or symbolic scenes that deepen the point.
• Never use the local SVG/template cover generator as the default.

Read references/image-and-draft-upload.md before creating images or preparing draft-box upload.

Bundled Uploader

This skill includes a self-contained Node.js uploader at scripts/wechat-article-workbench. Use it when the user wants a real WeChat draft-box entry.

Setup is required once per installation:

1. Run npm install in scripts/wechat-article-workbench.
2. Copy config.example.env to .env.
3. Fill WECHAT_APPID, WECHAT_APPSECRET, and short WECHAT_AUTHOR.
4. Keep DRY_RUN=1 for the first validation run, then set DRY_RUN=0 to create real drafts.

If credentials are missing or the WeChat API/IP whitelist is not ready, still produce the article JSON and image files, then tell the user what setup is missing.

Reference Loading

Load only the reference needed for the task:

• Read references/article-patterns.md for article structures, opening patterns, ending patterns, and title formulas.
• Read references/output-checklist.md when polishing, reviewing, or doing a final publish-ready pass.
• Read references/image-and-draft-upload.md when generating images, creating WeChat HTML JSON, using the bundled uploader, or turning links/manual topics into draft-box entries.

Quality Bar

Before finalizing, verify:

• The headline matches the body and does not overpromise.
• The first 200 Chinese characters make the reader know why to keep reading.
• Each section advances the same central promise.
• Concrete examples outweigh abstract adjectives.
• Data, rankings, policy, medical, legal, financial, and competitor claims are either sourced by the user or clearly framed as assumptions.
• The Markdown is clean and does not contain internal reasoning notes.
• Upload JSON validates with the local schema before drafting.
• Draft upload must not proceed without a real coverImagePath, unless the user explicitly enables the static fallback.