wechat-article-generator
Skill2 starsChanged 8 months agoApache-2.0View on GitHub
Legacy compatibility skill for generating older WeChat article package outputs such as tar.gz bundles and inline-style HTML. Use only when maintaining an existing legacy package workflow or reproducing historical deliverables.
In this repository27 other files it gives its agents.
- ai-hotspot-collectorSkill
- article-multi-publisherSkill
- article-pipeline-skillSkill
- character-ip-risk-checkSkill
- chrome-extension-devSkill
- chrome-extension-e2e-automationSkill
- chrome-extension-publishSkill
- chrome-extension-social-promoSkill
- chrome-webstore-image-generatorSkill
- code-reviewSkill
- fund-querySkill
- github-trending-writerSkill
- lark-workflow-doc-to-slidesSkill
- notionSkill
- playwright-twitter-accessSkill
- post-to-xhsSkill
- rewrite-skillSkill
- small-capital-investingSkill
- technical-article-preflightSkill
- technical-article-reviewSkill
- technical-spoken-rewriteSkill
- tencent-dev-community-publisherSkill
- toutiao-publisherSkill
- url-readerSkill
- wechat-article-formatterSkill
- wechat-publisherSkill
- wechat-sticker-publisherSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Use this legacy skill only when you explicitly need to reproduce the older package shape:
- Very specific: line 39
If a user asks for “生成旧发布包”“兼容之前的 tar.gz 交付结构”“复刻老的 article-wechat.html 输出”,this skill is still appropriate.
≈ “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.
Files
WeChat Article Generator (Legacy)
This skill is kept for backward compatibility only.
Do Not Use For New Work
For new article workflows, use:
technical-article-review
→ technical-article-preflight
→ wechat-article-formatter
→ wechat-publisherWhen It Is Still Acceptable
Use this legacy skill only when you explicitly need to reproduce the older package shape:
article.mdarticle-wechat.htmlimages/README.txt{slug}.tar.gz
Why It Is Legacy
- It uses the older inline-style HTML conversion path.
- It bypasses the newer review-first pipeline by default.
- It is not the preferred formatter for current WeChat publishing work.
Safe Boundary
If a user asks for “生成旧发布包”“兼容之前的 tar.gz 交付结构”“复刻老的 article-wechat.html 输出”,this skill is still appropriate.
Otherwise, prefer the repo-local modern workflow above.
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
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.

