agentleFS
Aias00Aias00/agent-skills/article-multi-publisher/SKILL.md

article-multi-publisher

Skill2 starsChanged 8 months agoApache-2.0View on GitHub

Publish the same article package directly to one or more of WeChat Official Account (微信公众号), Xiaohongshu (小红书), and Toutiao (头条号). Use when the user wants a unified workflow for 多平台发文, 同步发布到公众号/小红书/头条, or wants one article package dispatched to these Chinese content platforms.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when one reviewed article or one article package needs to go to any combination of:

    line 8
  2. Distinctive:

    If you only publish to WeChat, Xiaohongshu and Toutiao runtime dependencies do not need to be healthy in the current run.

    line 36
  3. Very specific:

    If <source> is a directory, the script resolves platform variants automatically:

    line 40
  4. Very specific:

    If WeChat needs a default author, keep wechat-publisher/EXTEND.md as the source of truth.

    line 111
  5. Very specific:

    If you distribute this repo to another machine, verify the platform-specific runtimes in post-to-xhs/, toutiao-publisher/, and …

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Article Multi Publisher

Use this skill when one reviewed article or one article package needs to go to any combination of:

  • 微信公众号
  • 小红书
  • 头条号

Unified Entry

From the repository root:

python3 article-multi-publisher/scripts/publish.py <source> [options]

<source> can be:

  • an article package directory
  • a single .md file
  • a single .html file

Repo-local Dependencies

This repo-local version resolves platform publishers from the repository itself:

  • WeChat → wechat-publisher
  • Xiaohongshu → post-to-xhs/
  • Toutiao → toutiao-publisher/

If you only publish to WeChat, Xiaohongshu and Toutiao runtime dependencies do not need to be healthy in the current run.

Source Resolution

If <source> is a directory, the script resolves platform variants automatically:

  • wechat: pass directory or final HTML straight to wechat-publisher
  • xhs: article-xhs.md → xhs.md → article-toutiao.md → article.md
  • toutiao: article-toutiao.md → article.md → article.html

Cover/image fallback:

  • images/01-cover.*
  • images/cover.*
  • images/cover-wide.*
  • imgs/cover.*
  • first image under images/ or imgs/

Defaults

Optional config files:

  • project: .baoyu-skills/article-multi-publisher/EXTEND.md
  • user: $HOME/.baoyu-skills/article-multi-publisher/EXTEND.md

Supported keys:

  • default_platforms
  • default_xhs_mode
  • default_xhs_template
  • default_xhs_account
  • default_wechat_author

Usage

Publish to all configured platforms:

python3 article-multi-publisher/scripts/publish.py ./article-package

Publish to WeChat + Toutiao only:

python3 article-multi-publisher/scripts/publish.py ./article-package --platforms wechat,toutiao

Force Xiaohongshu long-article mode:

python3 article-multi-publisher/scripts/publish.py ./article-package \
  --platforms xhs \
  --xhs-mode long-article \
  --xhs-template "杂志风"

Resolve commands without publishing:

python3 article-multi-publisher/scripts/publish.py ./article-package --dry-run

Platform Strategy

  • wechat: delegates article publishing to wechat-publisher
  • xhs: uses repo-local post-to-xhs; defaults to image-text unless long-article template is configured
  • toutiao: uses repo-local toutiao-publisher direct API flow

Current boundary:

  • This wrapper resolves source files, titles, covers, and per-platform variants.
  • Platform-specific metadata quirks should be fixed in the underlying platform skill, not duplicated here.

Notes

  • If WeChat needs a default author, keep wechat-publisher/EXTEND.md as the source of truth.
  • Existing logins and credentials are reused from the underlying platform skills; this wrapper does not create new sessions by itself.
  • If you distribute this repo to another machine, verify the platform-specific runtimes in post-to-xhs/, toutiao-publisher/, and wechat-publisher/ before expecting end-to-end publishing to succeed.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.