Post to WeChat Official Account

Language

Match user's language: Respond in the same language the user uses. If user writes in Chinese, respond in Chinese. If user writes in English, respond in English.

Script Directory

Agent Execution: Determine this SKILL.md directory as {baseDir}, then use {baseDir}/scripts/<name>.ts. Resolve ${BUN_X} runtime: if bun installed → bun; if npx available → npx -y bun; else suggest installing bun.

Script	Purpose
INLINECODE7	Image-text posts (图文)
INLINECODE8

Article posting via browser (文章) |
| scripts/wechat-api.ts | Article posting via API (文章) |
| scripts/md-to-wechat.ts | Markdown → WeChat-ready HTML with image placeholders |
| scripts/check-permissions.ts | Verify environment & permissions |

Preferences (EXTEND.md)

Check EXTEND.md existence (priority order):

CODEBLOCK0

CODEBLOCK1

┌────────────────────────────────────────────────────────┬───────────────────┐
│ Path │ Location │
├────────────────────────────────────────────────────────┼───────────────────┤
│ .baoyu-skills/baoyu-post-to-wechat/EXTEND.md │ Project directory │
├────────────────────────────────────────────────────────┼───────────────────┤
│ $HOME/.baoyu-skills/baoyu-post-to-wechat/EXTEND.md │ User home │
└────────────────────────────────────────────────────────┴───────────────────┘

┌───────────┬───────────────────────────────────────────────────────────────────────────┐
│ Result │ Action │
├───────────┼───────────────────────────────────────────────────────────────────────────┤
│ Found │ Read, parse, apply settings │
├───────────┼───────────────────────────────────────────────────────────────────────────┤
│ Not found │ Run first-time setup (references/config/first-time-setup.md) → Save → Continue │
└───────────┴───────────────────────────────────────────────────────────────────────────┘

EXTEND.md Supports: Default theme | Default color | Default publishing method (api/browser) | Default author | Default open-comment switch | Default fans-only-comment switch | Chrome profile path

First-time setup: references/config/first-time-setup.md

Minimum supported keys (case-insensitive, accept 1/0 or true/false):

Key	Default	Mapping
INLINECODE14	empty	Fallback for author when CLI/frontmatter not provided
INLINECODE16

1 | articles[].need_open_comment in draft/add request |
| only_fans_can_comment | 0 | articles[].only_fans_can_comment in draft/add request |

Recommended EXTEND.md example:

CODEBLOCK2

Theme options: default, grace, simple, modern

Color presets: blue, green, vermilion, yellow, purple, sky, rose, olive, black, gray, pink, red, orange (or hex value)

Value priority:

1. 1. CLI arguments
2. Frontmatter
3. EXTEND.md (account-level → global-level)
4. Skill defaults

Multi-Account Support

EXTEND.md supports managing multiple WeChat Official Accounts. When accounts: block is present, each account can have its own credentials, Chrome profile, and default settings.

Compatibility rules:

Condition	Mode	Behavior
No accounts block	Single-account	Current behavior, unchanged
INLINECODE26 with 1 entry

Single-account | Auto-select, no prompt |
| accounts with 2+ entries | Multi-account | Prompt to select before publishing |
| accounts with default: true | Multi-account | Pre-select default, user can switch |

Multi-account EXTEND.md example:

CODEBLOCK3

Per-account keys (can be set per-account or globally as fallback):
default_publish_method, default_author, need_open_comment, only_fans_can_comment, app_id, app_secret, INLINECODE36

Global-only keys (always shared across accounts):
default_theme, INLINECODE38

Account Selection (Step 0.5)

Insert between Step 0 and Step 1 in the Article Posting Workflow:

CODEBLOCK4

Credential Resolution (API Method)

For a selected account with alias {alias}:

1. 1. app_id / app_secret inline in EXTEND.md account block
2. Env var WECHAT_{ALIAS}_APP_ID / WECHAT_{ALIAS}_APP_SECRET (alias uppercased, hyphens → underscores)
3. INLINECODE44 with prefixed key INLINECODE45
4. INLINECODE46 with prefixed key
5. Fallback to unprefixed WECHAT_APP_ID / INLINECODE48

.env multi-account example:

CODEBLOCK5

Chrome Profile (Browser Method)

Each account uses an isolated Chrome profile for independent login sessions:

Source	Path
Account chrome_profile_path in EXTEND.md	Use as-is
Auto-generated from alias

{shared_profile_parent}/wechat-{alias}/ |
| Single-account fallback | Shared default profile (current behavior) |

CLI --account Argument

All publishing scripts accept --account <alias>:

CODEBLOCK6

Pre-flight Check (Optional)

Before first use, suggest running the environment check. User can skip if they prefer.

CODEBLOCK7

Checks: Chrome, profile isolation, Bun, Accessibility, clipboard, paste keystroke, API credentials, Chrome conflicts.

If any check fails, provide fix guidance per item:

Check	Fix
Chrome	Install Chrome or set WECHAT_BROWSER_CHROME_PATH env var
Profile dir

Shared profile at baoyu-skills/chrome-profile (see CLAUDE.md Chrome Profile section) |
| Bun runtime | brew install oven-sh/bun/bun (macOS) or npm install -g bun |
| Accessibility (macOS) | System Settings → Privacy & Security → Accessibility → enable terminal app |
| Clipboard copy | Ensure Swift/AppKit available (macOS Xcode CLI tools: xcode-select --install) |
| Paste keystroke (macOS) | Same as Accessibility fix above |
| Paste keystroke (Linux) | Install xdotool (X11) or ydotool (Wayland) |
| API credentials | Follow guided setup in Step 2, or manually set in .baoyu-skills/.env |

Image-Text Posting (图文)

For short posts with multiple images (up to 9):

CODEBLOCK8

See references/image-text-posting.md for details.

Article Posting Workflow (文章)

Copy this checklist and check off items as you complete them:

CODEBLOCK9

Step 0: Load Preferences

Check and load EXTEND.md settings (see Preferences section above).

CRITICAL: If not found, complete first-time setup BEFORE any other steps or questions.

Resolve and store these defaults for later steps:

• - default_theme (default default)
• INLINECODE63 (omit if not set — theme default applies)
• INLINECODE64
• INLINECODE65 (default 1)
• INLINECODE67 (default 0)

Step 1: Determine Input Type

Input Type	Detection	Action
HTML file	Path ends with .html, file exists	Skip to Step 3
Markdown file

Path ends with .md, file exists | Continue to Step 2 | | Plain text | Not a file path, or file doesn't exist | Save to markdown, continue to Step 2 |

Plain Text Handling:

1. 1. Generate slug from content (first 2-4 meaningful words, kebab-case)
2. Create directory and save file:

CODEBLOCK10

1. 3. Continue processing as markdown file

Slug Examples:

• - "Understanding AI Models" → INLINECODE71
• "人工智能的未来" → ai-future (translate to English for slug)

Step 2: Select Publishing Method and Configure

Ask publishing method (unless specified in EXTEND.md or CLI):

Method	Speed	Requirements
INLINECODE73 (Recommended)	Fast	API credentials
INLINECODE74

Slow | Chrome, login session |

If API Selected - Check Credentials:

CODEBLOCK11

CODEBLOCK12

If Credentials Missing - Guide Setup:

CODEBLOCK13

After location choice, prompt for values and write to .env:

CODEBLOCK14

Step 3: Resolve Theme/Color and Validate Metadata

1. 1. Resolve theme (first match wins, do NOT ask user if resolved):

- CLI --theme argument - EXTEND.md default_theme (loaded in Step 0) - Fallback: INLINECODE78

1. 2. Resolve color (first match wins):

- CLI --color argument - EXTEND.md default_color (loaded in Step 0) - Omit if not set (theme default applies)

1. 3. Validate metadata from frontmatter (markdown) or HTML meta tags (HTML input):

Field	If Missing
Title	Prompt: "Enter title, or press Enter to auto-generate from content"
Summary

Use fallback chain: frontmatter description → frontmatter summary → prompt user or auto-generate | | Author | Use fallback chain: CLI --author → frontmatter author → EXTEND.md default_author |

Auto-Generation Logic:

• - Title: First H1/H2 heading, or first sentence
• Summary: First paragraph, truncated to 120 characters

1. 4. Cover Image Check (required for API article_type=news):

1. Use CLI --cover if provided. 2. Else use frontmatter (coverImage, featureImage, cover, image). 3. Else check article directory default path: imgs/cover.png. 4. Else fallback to first inline content image. 5. If still missing, stop and request a cover image before publishing.

Step 4: Publish to WeChat

CRITICAL: Publishing scripts handle markdown conversion internally. Do NOT pre-convert markdown to HTML — pass the original markdown file directly. This ensures the API method renders images as <img> tags (for API upload) while the browser method uses placeholders (for paste-and-replace workflow).

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 ordinary external links inline.
• Existing HTML input is left as-is; no extra citation conversion is applied.

API method (accepts .md or .html):

CODEBLOCK15

CRITICAL: Always include --theme parameter. Never omit it, even if using default. Only include --color if explicitly set by user or EXTEND.md.

draft/add payload rules:

• - Use endpoint: INLINECODE101
• INLINECODE102: news (default) or INLINECODE104
• For news, include thumb_media_id (cover is required)
• Always resolve and send:

- need_open_comment (default 1)
- only_fans_can_comment (default 0)

• - author resolution: CLI --author → frontmatter author → EXTEND.md INLINECODE114

If script parameters do not expose the two comment fields, still ensure final API request body includes resolved values.

Browser method (accepts --markdown or --html):

CODEBLOCK16

Step 5: Completion Report

For API method, include draft management link:

CODEBLOCK17

For Browser method:

CODEBLOCK18

Detailed References

Topic	Reference
Image-text parameters, auto-compression	references/image-text-posting.md
Article themes, image handling

references/article-posting.md |

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 (imgs/cover.png) | ✗ | ✓ | ✗ | | Comment control (need_open_comment, only_fans_can_comment) | ✗ | ✓ | ✗ | | Requires Chrome | ✓ | ✗ | ✓ | | Requires API credentials | ✗ | ✓ | ✗ | | Speed | Medium | Fast | Slow |

Prerequisites

For API method:

• - WeChat Official Account API credentials
• Guided setup in Step 2, or manually set in INLINECODE120

For Browser method:

• - Google Chrome
• First run: log in to WeChat Official Account (session preserved)

Config File Locations (priority order):

1. 1. Environment variables
2. INLINECODE121
3. INLINECODE122

Troubleshooting

Issue	Solution
Missing API credentials	Follow guided setup in Step 2
Access token error

Check if API credentials are valid and not expired | | Not logged in (browser) | First run opens browser - scan QR to log in | | Chrome not found | Set WECHAT_BROWSER_CHROME_PATH env var | | Title/summary missing | Use auto-generation or provide manually | | No cover image | Add frontmatter cover or place imgs/cover.png in article directory | | Wrong comment defaults | Check EXTEND.md keys need_open_comment and only_fans_can_comment | | Paste fails | Check system clipboard permissions |

Extension Support

Custom configurations via EXTEND.md. See Preferences section for paths and supported options.