wechat article publisher
将 Markdown 或网页链接自动发布到微信公众号草稿并支持模板
zhenglong2015
@zhenglong2015
What This Skill Does
Extracts content from a Markdown file or web URL and publishes it as a draft or directly to WeChat Official Account. Supports two built-in templates (standard/viral) and can auto-generate cover images.
Replaces manually copying content into WeChat's editor and formatting it by automating draft creation, template styling, and optional direct publishing.
When to Use It
- Publish a local Markdown article as a WeChat draft with a consistent template
- Extract a blog post from a URL and create a WeChat draft from it
- Batch publish multiple articles by reusing the same workflow with different inputs
- Preview how an article will look in WeChat before creating a draft
- Automate the full publish-to-WeChat pipeline including draft creation and submission
Install
$ openclaw skills install @zhenglong2015/wechat-article-publisherWeChat Article Publisher
何时使用
当用户明确要求以下任一任务时触发本 skill：
- 把本地
.md文章发布到微信公众号 - 把网页链接（博客/新闻页）提取后发布到微信公众号
- 需要统一微信排版模板（
standard或viral）并自动生成封面 - 需要程序化输出
media_id、publish_id、发布状态
工作流
- 准备配置：
- 编辑本目录
config.json，仅需填写：wechat.app_id、wechat.app_secret、wechat.author
- 编辑本目录
- 安装依赖：
python scripts/publish_wechat.py --install
- 预览（不调用微信接口）：
python scripts/publish_wechat.py <输入> --dry-run
- 创建草稿：
python scripts/publish_wechat.py <输入>
- 直接提交发布（可选）：
python scripts/publish_wechat.py <输入> --publish --status
<输入> 支持：
- 本地 Markdown 文件路径
http:///https://网页 URL
命令参数
主脚本：scripts/publish_wechat.py
input：Markdown 文件路径或网页 URL--config：配置文件路径，默认本 skill 的config.json--template：覆盖模板，standard|viral--author：覆盖作者--source-url：覆盖原文链接--cover-image：指定本地封面图--dry-run：仅提取+渲染，不调微信 API--publish：草稿创建后调用freepublish/submit--status：提交发布后查询一次发布状态
执行约束
- 发布前优先做
--dry-run，检查标题、摘要和渲染 HTML。 - 如果账号无
freepublish权限，--publish可能返回48001，此时保留草稿手动发布。 - 若创建草稿时报
41005 media data missing，请通过--cover-image指定封面图。
输出结果
脚本标准输出 JSON，关键字段：
draft_media_idpublish_id（仅--publish）status（仅--status）preview_html（仅--dry-run）
Top skills in this category
Wechat Article Search
@wuchubuzai2018搜索微信公众号文章技能。通过微信搜索获取文章列表，覆盖科技/AI、社会热点、财经、教育、职场等各类中文资讯；可按关键词检索并返回标题、概要、发布时间、来源公众号与链接。当用户需要查找微信公众号文章、整理参考资料或快速获取文章信息时使用此技能。
YouTube
@byungkyuYouTube Data API integration with managed OAuth. Search videos, manage playlists, access channel data, and interact with comments. Use this skill when users want to interact with YouTube. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a YouTube connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a YouTube action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with YouTube examples; they add no YouTube capability - YouTube is not an event source, a trigger cannot read YouTube data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
gmail
@byungkyuGmail API integration with managed OAuth. Read, send, and manage emails, threads, labels, and drafts. Use this skill when users want to interact with Gmail. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Gmail connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Gmail action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Gmail examples; they add no Gmail capability - Gmail is itself an event source, so its own events are in `references/google-mail/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
ATXP
@emilioaccAccess ATXP paid API tools for web search, AI image generation, music creation, video generation, X/Twitter search, email, and agent account management. Use...
WhatsApp Business
@byungkyuWhatsApp Business API integration with managed OAuth. Send messages, manage templates, and handle conversations. Use this skill when users want to interact with WhatsApp Business. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a WhatsApp Business connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a WhatsApp Business action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with WhatsApp Business examples; they add no WhatsApp Business capability - WhatsApp Business is not an event source, a trigger cannot read WhatsApp Business data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).