Wechat Official Formatter
Businesswechat-official-formatterWechat Official Formatter is an Agent Skill for business published in the Jamailar/Beav repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Must be used for WeChat Official Account writing, Xiaohongshu-to-WeChat expansion, WeChat rich-text formatting, public-account draft preparation, binding checks, and draft publishing decisions.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Jamailar/Beav/blob/HEAD/desktop/electron/system-skills/wechat-official-formatter/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/wechat-official-formatter, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
WeChat Official Formatter
Use this skill whenever the task is aimed at wechat_official_account.
Workflow
- Treat WeChat work as a structured publishing task, not as generic long-form writing.
- Preserve the core viewpoint, then expand into article-grade structure:
- final title
- summary
- introduction
- body with clear section headings
- ending CTA
- image suggestions
- When source material comes from Xiaohongshu, keep the original hook and core examples, but add background, argumentation, transitions, and conclusion.
- When asked for formatting, produce content that can be rendered into clean WeChat HTML with stable heading hierarchy, readable paragraphs, quotes, lists, and inline emphasis.
- If the task reaches publishing/binding, prefer the app's built-in WeChat Official Account capability. Do not ask the user to install external
md2wechattooling.
Output Rules
- Default tone: professional, readable, not notebook-style.
- Headings should be meaningful and scannable.
- Paragraphs should be short enough for mobile reading.
- CTA should be explicit but not salesy by default.
- Avoid leaking internal planning notes, prompt text, or schema labels into the final article body.
Binding And Draft Rules
- Public-account binding in this app is based on Official Account developer credentials and internal validation.
- Before draft publishing, make sure the article has a usable cover image source.
- Prefer the first relevant article image as cover when no dedicated cover is provided.
- If a draft cannot be published because cover, credentials, or asset upload is missing, say exactly what is missing.