baoyu-post-to-wechat

Overview of baoyu-post-to-wechat skill

What baoyu-post-to-wechat does

baoyu-post-to-wechat is a publishing skill for WeChat Official Accounts that handles two different jobs: long-form article posting and image-text posting. It supports Markdown, HTML, and plain text inputs, then publishes either through the WeChat API or through a Chrome CDP browser flow. For most users, the real value is not “posting to WeChat” in the abstract, but turning draft content into something WeChat will actually accept with less manual cleanup.

Who should install baoyu-post-to-wechat

This skill fits writers, operators, and AI-assisted content workflows that already draft in Markdown and need repeatable WeChat publishing. It is especially useful if you want frontmatter-driven title/author/summary extraction, image handling, browser automation, or a fallback path when API-only posting is not enough. If you only need one-off manual publishing in the WeChat editor, a normal prompt is often simpler.

Why this skill is different from a generic prompt

The baoyu-post-to-wechat skill includes executable scripts, not just instructions. The practical differentiators are:

• Markdown-to-WeChat HTML conversion via scripts/md-to-wechat.ts
• Separate article and image-text flows via scripts/wechat-article.ts and scripts/wechat-browser.ts
• API and browser-based posting options
• Default conversion of ordinary external links into bottom citations, which is unusually aligned with WeChat formatting realities
• Chrome profile and permission checks via scripts/check-permissions.ts

What matters before adoption

The main install decision is environment fit. This skill expects bun or npx -y bun, a supported Chrome/Chromium/Edge install, and enough local browser access for CDP-based automation. If your workflow cannot use a local browser profile or browser automation, read that limitation first before investing time in setup.

How to Use baoyu-post-to-wechat skill

Install context and first files to read

For baoyu-post-to-wechat install, start in skills/baoyu-post-to-wechat and read:

• SKILL.md
• references/article-posting.md
• references/image-text-posting.md
• references/config/first-time-setup.md
• scripts/check-permissions.ts

The repo expects ${BUN_X} to resolve to bun if installed, otherwise npx -y bun. Before trying to publish anything, run the environment check script so you know whether Chrome detection, profile isolation, and clipboard/browser dependencies are working.

How baoyu-post-to-wechat usage works in practice

There are three practical entry paths:

• Article via browser: scripts/wechat-article.ts
• Article via API: scripts/wechat-api.ts
• Image-text for Social Media posting: scripts/wechat-browser.ts

Typical article command:
bun ./scripts/wechat-article.ts --markdown article.md --theme grace

Typical image-text command:
bun ./scripts/wechat-browser.ts --markdown source.md --images ./images/ --submit

If you already have rendered HTML:
bun ./scripts/wechat-article.ts --html content.html --title "Title"

Use --profile <dir> when you need a specific Chrome profile, and use --no-cite if inline external links matter more than citation-style output.

What input gives the best results

The strongest baoyu-post-to-wechat usage starts with a clean Markdown file that includes frontmatter:

---
title: Practical WeChat Publishing Workflow
author: Your Name
summary: A concise summary used for article metadata.
---

Then structure the body with one H1, clear section headings, valid local image paths, and final link formatting you are comfortable converting. Better input means:

• fewer title extraction mistakes
• stronger summary generation
• cleaner image replacement and upload handling
• less manual fixing in the WeChat editor

A weak prompt is “post this to WeChat.” A stronger one is: “Use baoyu-post-to-wechat to publish drafts/q2-update.md as an article, keep WeChat-friendly citations enabled, apply grace theme, set author to Team Ops, and use Chrome profile ./tmp/wechat-profile.”

Workflow tips that reduce guesswork

A reliable baoyu-post-to-wechat guide is:

1. Validate environment with scripts/check-permissions.ts
2. Choose article vs image-text flow first
3. Prepare Markdown with frontmatter and local images
4. Test conversion using scripts/md-to-wechat.ts if formatting is the main risk
5. Publish with browser or API path
6. Review the draft/output inside WeChat before final distribution

If something breaks, inspect scripts/cdp.ts, scripts/wechat-agent-browser.ts, and scripts/wechat-extend-config.ts before changing content. Those files explain how Chrome is found, how browser control works, and how local config can override defaults.

baoyu-post-to-wechat skill FAQ

Is baoyu-post-to-wechat good for beginners?

Yes, if you are comfortable running scripts and preparing Markdown. It is not ideal for users who want a pure chat-only experience with no local setup. The operational value comes from repeatability, not from being beginner-minimal.

When should I use this instead of a normal AI prompt?

Use baoyu-post-to-wechat when the hard part is execution: converting Markdown, handling images, honoring WeChat constraints, and posting with less manual browser work. Use a generic prompt when you only need help writing copy, titles, or summaries.

What are the main boundaries of baoyu-post-to-wechat for Social Media work?

It is specialized for WeChat Official Account publishing, not broad multichannel social scheduling. If you need one workflow for X, LinkedIn, Instagram, and WeChat together, this skill is too narrow on its own. It is best as the WeChat-specific publishing step in a larger content pipeline.

When is baoyu-post-to-wechat a bad fit?

Skip it if your environment forbids local browser automation, if you cannot install bun-compatible tooling, or if your team already has a stable CMS-to-WeChat integration. It is also overkill for rare manual posts with simple formatting.

How to Improve baoyu-post-to-wechat skill

Give baoyu-post-to-wechat better source material

The fastest way to improve baoyu-post-to-wechat output is better input discipline:

• put title, author, and summary in frontmatter
• keep one clear H1
• use accessible local image paths
• remove broken or tracking-heavy external links
• decide early whether you want citation conversion or --no-cite

This reduces downstream editing and makes the Markdown-to-WeChat transform much more predictable.

Avoid the most common failure modes

Common issues are usually operational, not conceptual:

• Chrome not found or wrong browser path
• profile conflicts from using a personal Chrome profile
• unexpected title/summary extraction from weak Markdown structure
• image path problems
• assuming article and image-text modes behave the same

Run permission checks first, isolate the profile, and test with a small sample document before batch use.

Improve prompts and handoff instructions

For better baoyu-post-to-wechat guide quality, specify:

• publish mode: article or image-text
• source file path
• title override or frontmatter source of truth
• whether to submit or preview/draft
• theme choice
• citation behavior
• profile path

A good instruction is concrete enough that the agent can pick the right script without guessing.

Iterate after the first output

After the first run, improve the result by adjusting the source Markdown before retrying, not by patching everything manually in WeChat. Check whether the issue came from content structure, metadata, image placement, or browser environment. For most teams, the best long-term improvement to the baoyu-post-to-wechat skill is building a reusable Markdown template and a known-good local profile setup.