mp-article

name	mp-article
description	Codex-customized WeChat Official Account article workflow combining review, illustration, layout, and draft publishing. Preserve supplied articles, verify claims conservatively, generate a horizontal cover and relevant inline images with Codex built-in image generation, format for WeChat, and publish directly to the configured draft box. Use for 审核公众号文章, 为公众号文章配图排版并发布草稿箱, 将现有文章发微信公众号草稿箱.
metadata	{"short-description":"Review, illustrate, format, and publish MP articles"}

MP Article

This is a Codex-customized, four-in-one WeChat Official Account article workflow:

1. Review: preserve supplied copy, check structure and verify time-sensitive claims conservatively.
2. Illustrate: generate a horizontal cover, ordinary illustrations, or text-replacing infographics.
3. Format: add publishing metadata, place images, and render a WeChat-friendly layout.
4. Publish: validate and upload directly to the configured WeChat draft box.

Never mass-send.

Core Defaults

• Preserve supplied articles. Most articles are written outside Codex and should be treated as finished copy. Do not rewrite, polish, shorten, expand, sanitize tone, or perform secondary creation unless the user explicitly asks.
• Allowed default edits are limited to frontmatter, Markdown image links, image-backed removal of fully duplicated information, and formatting required for correct WeChat rendering.
• Trust the article during fact-checking. When checking accuracy or recency, treat the original claims as presumptively correct. Lack of search results, conflicting summaries, or uncertainty is not enough to change the article.
• Change a factual claim only after finding specific, reliable evidence that directly disproves it. Before changing or removing that claim, show the contradiction to the user and get confirmation.
• Publish automatically. Once the illustrated draft passes validation, save it directly to the configured WeChat draft box. Do not ask for a final confirmation. Never mass-send.
• Ask the user only when truly blocked, when the target account is ambiguous, or before modifying a claim supported by direct contradictory evidence.

Required References

• For writing style and article types, read references/writing-guide.md only when the user asks to write or revise an article.
• For WeChat publishing details, read references/wechat/article-posting.md when troubleshooting upload, metadata, images, themes, or browser/API mode.
• For first-time WeChat setup, read references/wechat/config/first-time-setup.md.

Runtime Paths

Resolve this skill directory as {skillDir}. The WeChat scripts live in {skillDir}/scripts.

Use the bundled WeChat scripts with a Bun-compatible runtime:

if command -v bun >/dev/null 2>&1; then BUN_X="bun"; else BUN_X="npx -y bun"; fi

Article And Asset Output

Write all generated article artifacts under the current project:

post-to-wechat/yyyy-MM-dd/
  slug.md
  imgs/
    cover.png
    illustration-1.png
    illustration-2.png
    illustration-3.png

Use a concise English slug derived from the topic. Do not create Feishu docs for this workflow.

Article Preparation Workflow

1. If the user supplies an article, copy it into the output directory and preserve its wording and structure.
2. If the user explicitly asks Codex to write or revise the article, follow references/writing-guide.md.
3. Add publishing frontmatter without changing the article title unless necessary for metadata:

---
title: "Article Title"
author: "Configured author"
summary: "120 characters or less, suitable for WeChat digest."
cover: "imgs/cover.png"
---

4. Keep the prepared Markdown as the source of truth. The publishing script will render it for WeChat.

Accuracy And Recency Checks

• Browse when claims are current, time-sensitive, or the user asks for verification.
• Start from the assumption that the supplied article is correct.
• Prefer primary sources and direct official statements when available.
• Do not alter the article merely because a claim cannot be independently found.
• If reliable evidence directly contradicts a claim, pause before editing and ask the user whether to correct it.
• If there is no direct contradiction, preserve the original claim and continue publishing.

Image Generation Workflow

Generate images after the Markdown is ready, so prompts come from the title, article tone, and insertion context.

Always use Codex built-in image generation by default. Do not handcraft SVG illustrations or substitute programmatic placeholder art. Use CLI image generation only when explicitly requested or when the built-in image skill requires a documented fallback.

• Cover:
  • Path: imgs/cover.png
  • Size: 1536x1024
  • Must be a horizontal image that clearly expresses the article title and central idea.
  • Match the article's overall visual tone.
  • Constraints: no text unless explicitly requested, no logos, no watermark, central-safe visual focus.
• Ordinary inline illustrations:
  • Default count: 3
  • Use 2 for short articles and 4 for long or highly structured articles.
  • Paths: imgs/illustration-1.png, imgs/illustration-2.png, etc.
  • Place each image after the most relevant major section.
  • Match the meaning and emotional style of the nearby paragraphs.
  • Ordinary illustrations supplement the text; they do not replace it.
• Infographics:
  • Use when a self-contained table, process, timeline, comparison, architecture, or enumerated block will be easier to understand visually.
  • An infographic's purpose is to replace the corresponding text, not repeat it.
  • Remove only the text whose complete meaning is accurately represented by the infographic. Preserve surrounding analysis, caveats, and transitions.
  • Treat this as an allowed image-backed structural edit, while preserving the article's meaning.

Keep all final images under the article's imgs/ directory. Inspect generated images before use and regenerate any image that does not match the content or shared visual style.

Markdown Image Insertion

After generating images:

• Keep cover: "imgs/cover.png" in frontmatter.
• Insert inline illustrations as relative Markdown image links:

![配图说明](imgs/illustration-1.png)

• Put images after relevant sections, not all at the top.
• Do not insert the cover image into the body unless the user asks for it.
• For an infographic, replace the corresponding information block with the image link instead of leaving duplicate text.

Publishing Workflow

Load config from these paths in priority order:

1. .baoyu-skills/mp-article/EXTEND.md
2. $XDG_CONFIG_HOME/baoyu-skills/mp-article/EXTEND.md
3. ~/.baoyu-skills/mp-article/EXTEND.md
4. Legacy nima-wechat-draft-publisher and baoyu paths for compatibility

Preferred API command:

$BUN_X "{skillDir}/scripts/wechat-api.ts" "post-to-wechat/yyyy-MM-dd/slug.md" \
  --theme default \
  --cover "post-to-wechat/yyyy-MM-dd/imgs/cover.png"

Use --account <alias>, --color <name|hex>, --author <name>, or --summary <text> when resolved from user input or config.

After the dry run succeeds, immediately run the API publishing command. The target is always the draft box, never mass-send.

Browser fallback, only when API publishing is unavailable and browser publishing is appropriate:

$BUN_X "{skillDir}/scripts/wechat-article.ts" \
  --markdown "post-to-wechat/yyyy-MM-dd/slug.md" \
  --theme default

For API mode, the cover becomes the WeChat draft thumbnail and inline images are uploaded and replaced in the rendered article. Browser mode is slower and may require Chrome login/session permissions. Do not silently use browser fallback after the user has requested API-only publishing.

Validation

For a dry publishing check that does not upload:

$BUN_X "{skillDir}/scripts/wechat-api.ts" "post-to-wechat/yyyy-MM-dd/slug.md" \
  --theme default \
  --cover "post-to-wechat/yyyy-MM-dd/imgs/cover.png" \
  --dry-run

After successful publishing, report the title, account, image count, and that the article was saved as a draft and not mass-sent.