Token导航 LogoToken导航

Agent Skill · 开发

wechat-article-publisher(微信文章发布者)

wechat-article-publisher 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 Codex、Claude、Cursor、Gemini CLI 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

wechat-article-publisher 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 1,064。

总安装 41,616周安装 1,667GitHub Stars 132下载 13,464核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:wechat-article-publisher(微信文章发布者)
来源仓库:https://github.com/iamzifei/wechat-article-publisher-skill
仓库路径:skills/wechat-article-publisher
安装命令:
npx skills add https://github.com/iamzifei/wechat-article-publisher-skill --skill wechat-article-publisher
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/iamzifei/wechat-article-publisher-skill --skill wechat-article-publisher

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

通过API将Markdown或HTML文章发布到微信公众号草稿中。

支持Markdown和HTML文件格式并自动转换; HTML 保留原始格式 两种文章类型可供选择:标准新闻格式和以图像为中心的新闻图片(小绿书)模式 需要WECHAT_API_KEY环境变量和wx.limyai.com上授权的微信帐号 仅发布到草稿(用户在微信管理面板中手动发布);包括帐户列表和过期令牌或缺少授权的错误处理

来源仓库内路径:skills/wechat-article-publisher

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/iamzifei/wechat-article-publisher-skill --skil…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

wechat-article-publisher 怎么安装?

在终端执行 npx skills add https://github.com/iamzifei/wechat-article-publisher-skill --skill wechat-a…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

wechat-article-publisher 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

wechat-article-publisher 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

wechat-article-publisher 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

wechat-article-publisher 用的人多吗?

公开数据是累计安装 41,616 次,近一周安装 1,667 次,下载 13,464 次,GitHub 132 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

wechat-article-publisher 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
wechat-article-publisher

微信文章发布者 · 本页

41,616132接触敏感数据MIT有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

WeChat Article Publisher

Publish Markdown or HTML content to WeChat Official Account drafts via API, with automatic format conversion.

Prerequisites

  • WECHAT_API_KEY environment variable set (from.env file)
  • Python 3.9+
  • Authorized WeChat Official Account on wx.limyai.com

Scripts

Located in ~/.claude/skills/wechat-article-publisher/scripts/:

wechat_api.py

WeChat API client for listing accounts and publishing articles:

# List authorized accounts
python wechat_api.py list-accounts

# Publish from markdown file
python wechat_api.py publish --appid <wechat_appid> --markdown /path/to/article.md

# Publish from HTML file (preserves formatting)
python wechat_api.py publish --appid <wechat_appid> --html /path/to/article.html

# Publish with custom options
python wechat_api.py publish --appid <appid> --markdown /path/to/article.md --type newspic

parse_markdown.py

Parse Markdown and extract structured data (optional, for advanced use):

python parse_markdown.py <markdown_file> [--output json|html]

Workflow

Strategy: "API-First Publishing"

Unlike browser-based publishing, this skill uses direct API calls for reliable, fast publishing.

  1. Load WECHAT_API_KEY from environment
  2. List available WeChat accounts (if user hasn't specified)
  3. Detect file format (Markdown or HTML) and parse accordingly
  4. Call publish API to create draft in WeChat
  5. Report success with draft details

Supported File Formats:

  • .md files → Parsed as Markdown, converted by WeChat API
  • .html files → Sent as HTML, formatting preserved

Step-by-Step Guide

Step 1: Check API Key

Before any operation, verify the API key is available:

# Check if .env file exists and contains WECHAT_API_KEY
cat .env | grep WECHAT_API_KEY

If not set, remind user to:

  1. Copy .env.example to .env
  2. Set their WECHAT_API_KEY value

Step 2: List Available Accounts

Get the list of authorized WeChat accounts:

python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py list-accounts

Output example:

{
  "success": true,
  "data": {
    "accounts": [
      {
        "name": "我的公众号",
        "wechatAppid": "wx1234567890",
        "username": "gh_abc123",
        "type": "subscription",
        "verified": true,
        "status": "active"
      }
    ],
    "total": 1
  }
}

Important:

  • If only one account, use it automatically
  • If multiple accounts, ask user to choose
  • Note the wechatAppid for publishing

Step 3: Publish Article

For Markdown files:

python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py publish \
  --appid <wechatAppid> \
  --markdown /path/to/article.md

For HTML files (preserves formatting):

python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py publish \
  --appid <wechatAppid> \
  --html /path/to/article.html

For 小绿书 (image-text mode):

python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py publish \
  --appid <wechatAppid> \
  --markdown /path/to/article.md \
  --type newspic

Success response:

{
  "success": true,
  "data": {
    "publicationId": "uuid-here",
    "materialId": "uuid-here",
    "mediaId": "wechat-media-id",
    "status": "published",
    "message": "文章已成功发布到公众号草稿箱"
  }
}

Step 4: Report Result

After successful publishing:

  • Confirm the draft was created
  • Remind user to review and publish manually in WeChat admin panel
  • Provide any relevant IDs for reference

API Reference

Authentication

All API requests require the X-API-Key header:

X-API-Key: WECHAT_API_KEY

Get Accounts List

POST https://wx.limyai.com/api/openapi/wechat-accounts

Publish Article

POST https://wx.limyai.com/api/openapi/wechat-publish

Parameters:

ParameterTypeRequiredDescription
wechatAppidstringYesWeChat AppID
titlestringYesArticle title (max 64 chars)
contentstringYesArticle content (Markdown/HTML)
summarystringNoArticle summary (max 120 chars)
coverImagestringNoCover image URL
authorstringNoAuthor name
contentFormatstringNo'markdown' (default) or 'html'
articleTypestringNo'news' (default) or 'newspic'

Error Codes

CodeDescription
API_KEY_MISSINGAPI key not provided
API_KEY_INVALIDAPI key invalid
ACCOUNT_NOT_FOUNDAccount not found or unauthorized
ACCOUNT_TOKEN_EXPIREDAccount authorization expired
INVALID_PARAMETERInvalid parameter
WECHAT_API_ERRORWeChat API call failed
INTERNAL_ERRORServer error

Critical Rules

  1. NEVER auto-publish - Only save to drafts, user publishes manually
  2. Check API key first - Fail fast if not configured
  3. List accounts first - User may have multiple accounts
  4. Handle errors gracefully - Show clear error messages
  5. Preserve original content - Don't modify user's markdown unnecessarily

Supported Formats

Markdown Files (.md)

  • H1 header (#) → Article title
  • H2/H3 headers (##, ###) → Section headers
  • Bold (text)
  • Italic (*text*)
  • Links text
  • Blockquotes (>)
  • Code blocks (...)
  • Lists (- or 1.)
  • Imagesalt → Auto-uploaded to WeChat

HTML Files (.html)

  • <title> or <h1> → Article title
  • All HTML formatting preserved (styles, tables, etc.)
  • <img> tags → Images auto-uploaded to WeChat
  • First <p> → Auto-extracted as summary
  • Supports inline styles and rich formatting

HTML Title Extraction Priority:

  1. <title> tag content
  2. First <h1> tag content
  3. "Untitled" as fallback

HTML Content Extraction:

  • If <body> exists, uses body content
  • Otherwise, strips <html>, <head>, <!DOCTYPE> and uses remaining content

Article Types

news (普通文章)

  • Standard WeChat article format
  • Full Markdown/HTML support
  • Rich text with images

newspic (小绿书/图文消息)

  • Image-focused format (like Instagram posts)
  • Maximum 20 images extracted from content
  • Text content limited to 1000 characters
  • Images auto-uploaded to WeChat

Example Flow

Markdown File

User: "把 ~/articles/ai-tools.md 发布到微信公众号"

# Step 1: Verify API key
cat .env | grep WECHAT_API_KEY

# Step 2: List accounts
python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py list-accounts

# Step 3: Publish (assuming single account with appid wx1234567890)
python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py publish \
  --appid wx1234567890 \
  --markdown ~/articles/ai-tools.md

# Step 4: Report
# "文章已成功发布到公众号草稿箱!请登录微信公众平台预览并发布。"

HTML File

User: "把这个HTML文章发布到公众号:~/articles/newsletter.html"

# Step 1: Verify API key
cat .env | grep WECHAT_API_KEY

# Step 2: List accounts
python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py list-accounts

# Step 3: Publish HTML (auto-detects format)
python ~/.claude/skills/wechat-article-publisher/scripts/wechat_api.py publish \
  --appid wx1234567890 \
  --html ~/articles/newsletter.html

# Step 4: Report
# "文章已成功发布到公众号草稿箱!HTML格式已保留。请登录微信公众平台预览并发布。"

Error Handling

API Key Not Found

Error: WECHAT_API_KEY environment variable not set.

Solution: Ask user to set up .env file with their API key.

Account Not Found

Error: ACCOUNT_NOT_FOUND - 公众号不存在或未授权

Solution: Ask user to authorize their account on wx.limyai.com.

Token Expired

Error: ACCOUNT_TOKEN_EXPIRED - 公众号授权已过期

Solution: Ask user to re-authorize on wx.limyai.com.

WeChat API Error

Error: WECHAT_API_ERROR - 微信接口调用失败

Solution: May be temporary issue, retry or check WeChat service status.

Best Practices

Why use API instead of browser automation?

  1. Reliability: Direct API calls are more stable than browser automation
  2. Speed: No browser startup, page loading, or UI interactions
  3. Simplicity: Single command to publish
  4. Portability: Works on any system with Python (no macOS-only dependencies)

Content Guidelines

  1. Images: Use public URLs when possible; local images will be uploaded
  2. Title: Keep under 64 characters
  3. Summary: Auto-extracted from first paragraph if not provided
  4. Cover: First image in markdown becomes cover if not specified

Workflow Efficiency

Minimal workflow (1 command):
- list-accounts → get appid → publish → done

Full workflow (with verification):
1. Check .env → list accounts → confirm with user
2. Publish with options → report result

Troubleshooting

Q: How do I get a WECHAT_API_KEY?

A: Register and authorize your WeChat account at wx.limyai.com to get your API key.

Q: Can I publish to multiple accounts?

A: Yes, use list-accounts to see all authorized accounts, then specify the target --appid.

Q: Images not showing in WeChat?

A: Ensure images are accessible URLs. Local images are auto-uploaded but may fail if path is incorrect.

Q: Title is too long?

A: WeChat limits titles to 64 characters. The script will use the first 64 chars of H1.

Q: What's the difference between news and newspic?

A: news is standard article format; newspic (小绿书) is image-focused with limited text.

平台分布

Claude Code

31.3%
按下载量换算4,214

OpenCode

19.97%
按下载量换算2,689

Gemini CLI

18.58%
按下载量换算2,502

Cursor

11.16%
按下载量换算1,503

Antigravity

7.05%
按下载量换算949

windsurf

3.54%
按下载量换算477

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills