Baoyu-skills baoyu-post-to-wechat
Posts content to WeChat Official Account (微信公众号) via API or Chrome CDP. Supports article posting (文章) with HTML, markdown, or plain text input, and image-text posting (贴图, formerly 图文) with multiple images. Markdown article workflows default to converting ordinary external links into bottom citations for WeChat-friendly output. Use when user mentions "发布公众号", "post to wechat", "微信公众号", or "贴图/图文/文章".
git clone https://github.com/JimLiu/baoyu-skills
T=$(mktemp -d) && git clone --depth=1 https://github.com/JimLiu/baoyu-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/baoyu-post-to-wechat" ~/.claude/skills/jimliu-baoyu-skills-baoyu-post-to-wechat && rm -rf "$T"
skills/baoyu-post-to-wechat/SKILL.mdPost to WeChat Official Account
User Input Tools
When this skill prompts the user, follow this tool-selection rule (priority order):
- Prefer built-in user-input tools exposed by the current agent runtime — e.g.,
,AskUserQuestion
,request_user_input
,clarify
, or any equivalent.ask_user - Fallback: if no such tool exists, emit a numbered plain-text message and ask the user to reply with the chosen number/answer for each question.
- Batching: if the tool supports multiple questions per call, combine all applicable questions into a single call; if only single-question, ask them one at a time in priority order.
Concrete
AskUserQuestion references below are examples — substitute the local equivalent in other runtimes.
Language
Respond in the user's language. If they write in Chinese, reply in Chinese; if English, English. Keep technical tokens (paths, flags, field names) in English.
Script Directory
{baseDir} = this SKILL.md's directory. Resolve ${BUN_X}: prefer bun; else npx -y bun; else suggest brew install oven-sh/bun/bun.
| Script | Purpose |
|---|---|
| Image-text posts (图文) |
| Article posting via browser (文章) |
| Article posting via API (文章) |
| Markdown → WeChat-ready HTML with image placeholders |
| Verify environment & permissions |
Preferences (EXTEND.md)
Check these paths in order; first hit wins:
| Path | Scope |
|---|---|
| Project |
| XDG |
| User home |
Found → read, parse, apply. Not found → run first-time setup (
references/config/first-time-setup.md) before anything else.
Minimum keys (case-insensitive, accept
1/0 or true/false):
| Key | Default | Mapping |
|---|---|---|
| empty | Fallback for when CLI/frontmatter not provided |
| | in |
| | in |
Recommended EXTEND.md:
default_theme: default default_color: blue default_publish_method: api default_author: 宝玉 need_open_comment: 1 only_fans_can_comment: 0 chrome_profile_path: /path/to/chrome/profile
Theme options: default, grace, simple, modern. Color presets: blue, green, vermilion, yellow, purple, sky, rose, olive, black, gray, pink, red, orange (or hex).
Value priority: CLI args → frontmatter → EXTEND.md (account-level → global) → skill defaults.
Multi-Account Support
EXTEND.md supports an
accounts: block for managing multiple Official Accounts. With 2+ entries, the workflow inserts a Step 0.5 to prompt for account selection (or auto-selects based on default: true or --account <alias>).
Full details — compatibility rules, per-account keys, credential resolution, per-account Chrome profiles, CLI usage — in
references/multi-account.md.
Pre-flight Check (Optional)
Before first use, suggest the environment check (user can skip):
${BUN_X} {baseDir}/scripts/check-permissions.ts
Checks: Chrome, profile isolation, Bun, Accessibility, clipboard, paste keystroke, API credentials, Chrome conflicts.
| Check fails | Fix |
|---|---|
| Chrome | Install Chrome or set |
| Profile dir | Shared profile at |
| Bun runtime | or |
| Accessibility (macOS) | System Settings → Privacy & Security → Accessibility → enable terminal app |
| Clipboard copy | Ensure Swift/AppKit (macOS: ) |
| Paste keystroke (Linux) | Install (X11) or (Wayland) |
| API credentials | Follow guided setup in Step 2, or set in |
Image-Text Posting (图文)
Short posts with multiple images (up to 9):
${BUN_X} {baseDir}/scripts/wechat-browser.ts --markdown article.md --images ./images/ ${BUN_X} {baseDir}/scripts/wechat-browser.ts --title "标题" --content "内容" --image img.png --submit
Details:
references/image-text-posting.md.
Article Posting Workflow (文章)
- [ ] Step 0: Load preferences (EXTEND.md) - [ ] Step 0.5: Resolve account (multi-account only — see references/multi-account.md) - [ ] Step 1: Determine input type - [ ] Step 2: Select method and configure credentials - [ ] Step 3: Resolve theme/color and validate metadata - [ ] Step 4: Publish to WeChat - [ ] Step 5: Report completion
Step 0: Load Preferences
Check and load EXTEND.md (see "Preferences" above). If not found, complete first-time setup before any other questions. Resolve and cache for later steps:
default_theme, default_color, default_author, need_open_comment, only_fans_can_comment.
Step 1: Determine Input Type
| Input | Detection | Next |
|---|---|---|
| HTML file | Path ends , file exists | Skip to Step 3 |
| Markdown file | Path ends , file exists | Step 2 |
| Plain text | Not a file path, or file doesn't exist | Save to markdown, then Step 2 |
Plain-text handling:
- Generate slug (first 2-4 meaningful words, kebab-case; translate Chinese to English for the slug).
- Save to
(create directory if needed).post-to-wechat/YYYY-MM-DD/<slug>.md - Continue as a markdown file.
Step 2: Select Publishing Method and Configure
Ask method unless specified in EXTEND.md or CLI:
| Method | Speed | Requires |
|---|---|---|
(Recommended) | Fast | API credentials |
| Slow | Chrome + logged-in session |
API selected + missing credentials → run guided setup per
references/api-setup.md (writes to .baoyu-skills/.env).
Step 3: Resolve Theme/Color and Validate Metadata
- Theme: CLI
→ EXTEND.md--theme
→default_theme
(first match wins; do NOT ask if resolved).default - Color: CLI
→ EXTEND.md--color
→ omit (theme default applies).default_color - Validate metadata (frontmatter for markdown, meta tags for HTML):
| Field | Missing → |
|---|---|
| Title | Ask, or press Enter to auto-generate from content |
| Summary | Frontmatter → → ask or auto-generate |
| Author | CLI → frontmatter → EXTEND.md |
Auto-generation: title = first H1/H2 or first sentence; summary = first paragraph, truncated to 120 chars.
- Cover image (required for API
): CLIarticle_type=news
→ frontmatter (--cover
/coverImage
/featureImage
/cover
) →image
→ first inline image → stop and request one if still missing.imgs/cover.png
Step 4: Publish
Important — never pre-convert markdown to HTML. Publishing scripts handle the conversion internally and the two methods render images differently: API renders
<img> tags for upload, browser uses placeholders for paste-and-replace. Passing a pre-converted HTML breaks one or the other.
Markdown citation default: for markdown input, ordinary external links are converted to bottom citations by default. Use
--no-cite only if the user explicitly wants to keep inline links. Existing HTML input is left as-is.
API method (accepts
.md or .html):
${BUN_X} {baseDir}/scripts/wechat-api.ts <file> --theme <theme> [--color <color>] [--title <title>] [--summary <summary>] [--author <author>] [--cover <cover_path>] [--no-cite]
Always pass
--theme even if it's default. Only pass --color when explicitly set by the user or EXTEND.md.
payload rules:draft/add
- Endpoint:
POST https://api.weixin.qq.com/cgi-bin/draft/add?access_token=ACCESS_TOKEN
:article_type
(default) ornewsnewspic- For
, includenews
(cover required)thumb_media_id - Always include
(defaultneed_open_comment
) and1
(defaultonly_fans_can_comment
) in the request body, even if the CLI doesn't expose them0
Browser method (accepts
--markdown or --html):
${BUN_X} {baseDir}/scripts/wechat-article.ts --markdown <markdown_file> --theme <theme> [--color <color>] [--no-cite] ${BUN_X} {baseDir}/scripts/wechat-article.ts --html <html_file>
Step 5: Completion Report
WeChat Publishing Complete! Input: [type] - [path] Method: [API | Browser] Theme: [theme] [color if set] Article: • Title: [title] • Summary: [summary] • Images: [N] inline • Comments: [open/closed], [fans-only/all] ← API method only Result: ✓ Draft saved to WeChat Official Account • media_id: [media_id] ← API method only Next Steps (API): → Manage drafts: https://mp.weixin.qq.com (登录后进入「内容管理」→「草稿箱」) Files created: [• post-to-wechat/YYYY-MM-DD/slug.md (if plain text input)] [• slug.html (converted)]
Feature Comparison
| Feature | Image-Text | Article (API) | Article (Browser) |
|---|---|---|---|
| Plain text input | ✗ | ✓ | ✓ |
| HTML input | ✗ | ✓ | ✓ |
| Markdown input | Title/content | ✓ | ✓ |
| Multiple images | ✓ (up to 9) | ✓ (inline) | ✓ (inline) |
| Themes | ✗ | ✓ | ✓ |
| Auto-generate metadata | ✗ | ✓ | ✓ |
Default cover fallback () | ✗ | ✓ | ✗ |
| Comment control | ✗ | ✓ | ✗ |
| Requires Chrome | ✓ | ✗ | ✓ |
| Requires API credentials | ✗ | ✓ | ✗ |
| Speed | Medium | Fast | Slow |
Troubleshooting
| Issue | Fix |
|---|---|
| Missing API credentials | Follow guided setup in Step 2 |
| Access token error | Verify credentials valid and not expired |
| Not logged in (browser) | First run opens browser — scan QR to log in |
| Chrome not found | Set |
| Title/summary missing | Use auto-generation or provide manually |
| No cover image | Add frontmatter cover or place in article directory |
| Wrong comment defaults | Check / in EXTEND.md |
| Paste fails | Check system clipboard permissions |
References
| File | Content |
|---|---|
| Image-text parameters, auto-compression |
| Article themes, image handling |
| Multi-account compatibility, credentials, Chrome profiles, CLI |
| Guided credential setup |
| First-time EXTEND.md setup |
Extension Support
Custom configurations via EXTEND.md. See "Preferences" for paths and supported options.