WeWrite is a workflow for creating and publishing WeChat public-account articles with an AI coding agent, covering topic selection, source gathering, drafting, review, optional illustrations, formatting, and draft delivery. It is for public-account writers who want to produce articles or adapt them for other platforms, and its catalogue entries provide the skills and plugin for running those workflow steps.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add imraywang/wewrite --skill wewrite-publishgit clone --depth 1 https://github.com/imraywang/wewriteWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/imraywang/wewrite/wewrite-publish)<a href="https://agentmods.dev/skills/imraywang/wewrite/wewrite-publish"><img src="https://agentmods.dev/badge/skills/imraywang/wewrite/wewrite-publish/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/imraywang/wewrite/wewrite-publish"><img src="https://agentmods.dev/badge/skills/imraywang/wewrite/wewrite-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.00693 |
| Opus 5 | $0.00023 | $0.00347 |
| Sonnet 5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
wewrite-publish scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
wewrite-publish — 排版、预览、草稿箱
前置
用户指定文章时使用该文件；否则 wewrite run show。如果
artifacts.illustrated_article 存在且非空就使用它，否则使用 artifacts.article；读取标题、
摘要、封面、预览路径、发布权限和降级标记。已完成文章可以直接排版或发布，不要恢复写作
任务。主题取 style.yaml 的 theme，默认 professional-clean。
排版和发布不得自动调用 wewrite-visual。没有封面时照常生成本地预览；只有用户另行要求
配图时才进入视觉模块。
用户本轮明确要求“推到草稿箱/发布”时，有任务先运行
wewrite run permission publish allow；用户撤回时运行 wewrite run permission publish deny。
只排版、预览或“完整制作”都不能授予发布权限。
有任务时进入：
wewrite run step publish in_progress
预检
- 标题存在且符合微信限制；摘要不超过 120 字节；正文 200-20000 字。
- 正文图片不超过 10 张且实际可读；表格不超过 4 列。
- 发布草稿必须有封面。没有封面不能假设微信会补默认图，改走本地预览。
- 发布必须同时满足：
permissions.publish=true、flags.skip_publish=false、用户本轮没有撤回。
动作
始终先生成本地预览，有任务时保存到 artifacts.preview；任务外文章保存到原文件旁：
wewrite preview {article} --theme {theme} --no-open -o {preview}
确认预览产物存在且通过兼容性校验。若没有明确发布权限，流程到此结束；“写一篇”“完整制作” 都不等于允许发布。
只有用户明确要求草稿箱且预检全部通过时执行：
wewrite publish {article} --cover {cover} --theme {theme} --title "{title}" --digest "{digest}"
发布失败时保留预览，不自动重试产生外部动作。有任务时更新 publish.preview_html；成功时再写
publish.media_id，随后：
wewrite run step publish completed
辅助功能
| 用户说 | 动作 |
|---|---|
| 看主题 | wewrite gallery |
| 换主题 | 重新 preview；只有再次明确要求才重新 publish |
| 做图片帖 | 先确认用户确实要推草稿箱，再执行 wewrite image-post |
| 只排版 | 只 preview |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 75 lines · 47 tokens per session scan A 77d4a89d80d7
wewrite-publish is a skill published in the GitHub repository imraywang/wewrite (3,264 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 693 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…