agentleFS
zzu-kenzzu-ken/ai-skills/skills/wechat-article-writer/SKILL.md

wechat-article-writer

Skill4 starsChanged 9 months agoISCView on GitHub

Multi-agent workflow for generating WeChat public account articles (微信公众号推文). Fetches source articles, searches hot news and supplementary data via internet, rewrites with original perspectives, and polishes through editorial review. Use when user asks to write, rewrite, or generate a WeChat article, 公众号推文, or Chinese content article from a URL, text, or topic keyword. Supports two modes — article-based rewrite and keyword-driven generation — with integrated web search for trending news.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use codegen-diagram, codegen-doc and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xstongxueSkill

    codegen-diagram

    基于当前项目/代码生成 Draw.io 图表,支持技术栈图、系统架构图、数据结构图、E-R 图四种类型。输出符合 Draw.io 语法的 .drawio 文件(mxGraph XML),可直接导入 Draw.io 编辑。当用户提到技术栈、系统架构、数据结构、E-R 图时使用。

    Also in 3 projects that use this

  • xstongxueSkill

    codegen-doc

    基于当前项目/代码生成各类文档,支持论文章节、项目梳理、重点问题、简历项目描述四种类型。当用户提到生成论文章节、项目梳理、技术难点、简历项目描述时使用。要给新同事看的上手文档(新人文档、架构文档、代码导读、onboarding)用 project-docs。

    Also in 3 projects that use this

  • catsonkeyboardSkill

    drawio-diagram

    将 ASCII 图或 Mermaid 图转换为 draw.io 专业矢量图并导出 PNG 图片。 当用户需要将 ASCII 文本图、Mermaid 图、流程图、架构图、关系图转换为矢量图时使用。 触发场景:"转成流程图"、"生成架构图"、"ASCII 转图片"、"mermaid 转图片"、 "mermaid 转 drawio"、"画流程图"、"drawio"、"导出 PNG"、"画个图"、"转成图片"。

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

  • +3 more from xstongxue

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search for facts, data, expert opinions, and stakeholder responses around the topic.

    line 198
  2. Distinctive:

    Search trending news related to the topic using a 3-funnel approach:

    line 202
  3. Distinctive:

    Check before proceeding to writing:

    line 219
  4. Distinctive:

    Read the following reference documents:

    line 254
  5. Distinctive:

    Write Markdown file to output directory

    line 317
  6. Distinctive:

    After the article draft, output a supplement list with 2-4 items:

    line 324
  7. Distinctive:

    Search in both English (primary sources) and Chinese (local perspectives), cross-validate.

    line 363

≈ “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

WeChat Article Writer v2

Multi-agent workflow to produce polished WeChat public account articles (微信公众号推文) from a source article or topic keyword, with internet search for hot news integration.

Key Principles:

  1. No fabrication — All data must have verifiable sources
  2. No filler — Remove "获取方式", "下期预告", empty predictions
  3. Human tone — Write like developers talking to developers
  4. Source attribution — Every claim needs a link or citation

Workflow Overview

Phase 0: Input Parsing + Structure Selection
  │  Detect input type → extract topic/keywords
  │  Select article structure (A/B/C/D)
  │
  ├──────────────┬──────────────┐
  ▼              ▼              ▼
Agent A        Agent B        Agent C         Phase 1 (parallel)
Research       Hot News       Strategy
  │              │              │
  └──────────────┼──────────────┘
                 ▼
          Gate 1: Material Check + Source Validation
                 ▼
          Agent D: Writer                     Phase 2
                 ▼
          Agent E: Editor                     Phase 3
                 ▼
          Agent F: Fact Checker               Phase 4
                 ▼
          Gate 2: Final Check → Output + Supplement List

Article Structure Templates (4 Types)

Structure is auto-selected based on topic type:

Structure A: Direct (新闻/发布)

Use when: Product launch, company announcement, breaking news

What happened (1-2 sentences)
→ Key points (3 bullets max)
→ What it means for readers
→ Action items (if any)
→ Sources

Characteristics:

  • No section numbers
  • Natural transitions
  • 500-800 characters
  • Minimal Markdown (maybe 1-2 bold phrases)

Example opening:

OpenAI 在 3 月 5 日发布了 GPT-5.4。

更新就三点:降低幻觉率、减少说教、改进代码能力。
价格没变,订阅用户自动升级。

Structure B: Question-Driven (评测/对比)

Use when: Product review, comparison, "should I upgrade" topics

A question to open ("GPT-5.4 值得升吗?")
→ My answer (clear stance)
→ Why (2-3 reasons with evidence)
→ Counter-argument
→ My response
→ Final recommendation

Characteristics:

  • Conversational tone
  • Back-and-forth reasoning
  • 1000-1500 characters
  • Occasional short paragraphs for emphasis

Example opening:

GPT-5.4 值得升吗?

我的答案:可以,但不用急。

如果你在用 GPT-5.3,变化感知不强。
如果你还在用 GPT-4,直接升。

Structure C: Story-Driven (经验/案例)

Use when: Personal experience, case study, lesson learned

A scene to open ("今天早上...")
→ Problem encountered
→ How I solved it
→ What I learned
→ How readers can apply it

Characteristics:

  • First-person narrative
  • Has plot/tension
  • 1200-1800 characters
  • Emotional arc (frustration → solution → relief)

Example opening:

今天早上,我的自动化脚本挂了。

原因是 OpenAI 昨晚偷偷改了 API...

Structure D: List-Based (工具/资源)

Use when: Tool recommendations, resource collections, checklists

One sentence on why this matters
→ 1. Tool 1 (why + how to use)
→ 2. Tool 2
→ 3. Tool 3
→ One sentence close

Characteristics:

  • Practical, scannable
  • Each item has clear value
  • 800-1200 characters
  • Numbers OK, but no fancy formatting

Example opening:

分享 3 个我每天都在用的 CLI 工具。

不是那种"应该有用"的,是真离不开的。

Structure Selection Logic

Topic TypeKeywordsStructure
News/Launch"发布", "上线", "推出"A (Direct)
Review/Comparison"评测", "对比", "vs"B (Question)
Experience/Case"我", "经验", "案例"C (Story)
Tools/Resources"工具", "清单", "推荐"D (List)

Agent C (Strategy) proposes structure in Phase 1, Writer executes in Phase 2.

Phase 0: Input Parsing

Detect input type and extract execution parameters:

InputDetectionPath
Article URLContains httpFetch → extract topic → Phase 1
Article textLong pasted contentAnalyze directly → Phase 1
Topic keywordShort phraseSkip fetch → keyword-driven Phase 1
MixedURL + extra requirementsFetch + parse requirements → Phase 1

Extract parameters (use defaults when unspecified):

topic:      ""           # Core topic
keywords:   []           # Auto-expand synonyms
source_url: ""           # Source URL if any
tone:       "default"    # default / aggressive / neutral / humorous
word_count: 1500         # Target word count
hot_news:   true         # Search related trending news
output_dir: "./"         # Output directory

Phase 1: Three Parallel Agents

Launch three agents concurrently. Read references/agent-prompts.md for detailed prompt templates.

Agent A: Research

Search for facts, data, expert opinions, and stakeholder responses around the topic. Use 5-layer search strategy from narrow to broad.

Agent B: Hot News Search

Search trending news related to the topic using a 3-funnel approach:

  1. Direct hits (★★★) — same event chain → must integrate into main narrative
  2. Same-field (★★☆) — forms contrast or backdrop → 1-2 sentences
  3. Cross-field resonance (★☆☆) — shared underlying logic → analogy only
  4. Unrelated (☆☆☆) — discard, never force-fit

Also capture: mainstream opinion, dissent, controversy focal points.

Agent C: Content Strategy

Analyze source (if any), propose differentiated angles from 7 dimensions: technical reality, business logic, strategic timing, user experience gap, historical parallel, contrarian view, China-local perspective.

Output: fact checklist, 5-7 angles, recommended structure, tone calibration, 3-4 punchlines.

Gate 1: Material Sufficiency

Check before proceeding to writing:

□ ≥3 reliable data points?
□ ≥1 direct-hit hot news (★★★)?
□ ≥2 different stakeholder perspectives?
□ ≥3 viable differentiated angles?
□ ≥1 usable historical analogy?

5/5 → proceed | 3-4/5 → proceed with gaps noted | <3/5 → supplementary search

Phase 2: Writing

Integrate all Phase 1 outputs into a draft. Read references/formatting.md for color system and HTML templates.

Material Allocation Rules

  • ★★★ hot news → weave into main argument
  • ★★☆ hot news → 1-2 sentence supplement, don't steal the spotlight
  • Key data → place after claims that need backing
  • Direct quotes → place where authority matters
  • Analogies → place where comprehension barriers exist

Hot News Integration Modes

ModeWhenHow
BackdropHot news precedes topicOpen with hot news, transition to topic
ContrastHot news opposes topicSide-by-side, let reader judge
AnalogyShared underlying logic1-2 sentences in analysis section
EvidenceHot news data supports claimEmbed as proof within argument

Quality Standards

Read the following reference documents:

  • references/quality-standards.md — Writing standards and anti-patterns
  • references/calibration-checklist.md — Mandatory pre-output checklist
  • references/formatting.md — Color system and HTML templates

Core rules:

  1. Concise — every sentence must carry information
  2. Opinionated — ≥2 original angles not in the source
  3. Plain but assertive — no "震惊/炸了/细思极恐"
  4. Respect reader intelligence — facts + analysis, let them conclude
  5. Data needs denominators — absolute numbers require base/ratio
  6. No emoji spam, no cliché closings
  7. NO FABRICATION — if you didn't test it, don't claim test results
  8. Source everything — every data point needs a link or citation

Phase 3: Editorial Review

Launch review agent to audit on 8 dimensions: plagiarism risk, information density, logic flow, language quality, fresh angles, hot news integration, mobile formatting, title strength.

Output: per-issue diagnosis + rewrite suggestion + 2-3 alternative titles.

Phase 4: Fact Checking (NEW)

Critical step — Launch fact-checking agent to verify:

Source Verification

□ Every data point has a source link?
□ Every quote is attributed to a real person/source?
□ No fabricated test results or case studies?
□ No "according to research" without citation?

Content Integrity

□ No "获取方式", "下期预告" or similar operational filler?
□ No empty predictions ("必将", "一定会", "注定")?
□ No AI clichés ("震惊", "炸了", "细思极恐", "历史拐点")?
□ No forced engagement ("你觉得呢?评论区留言")?

Uncertainty Handling

□ Unverified claims marked as "待验证" or "据称"?
□ Conflicting data presented with both sources?
□ Limitations acknowledged where applicable?

Output: fact-check report with issues flagged + required fixes.

Phase 5: Final Output

  1. Apply all editorial + fact-check fixes
  2. Run final checklist:
    • All data sourced?
    • No fabricated content?
    • No operational filler?
    • Structure matches topic type?
    • Markdown used appropriately (not over-formatted)?
    • Title optimized?
    • Ending strong (no empty predictions)?
    • Word count in range?
  3. Write Markdown file to output directory
  4. Also output:
    • Source bibliography (all links used)
    • Supplement List (待补充清单) — items for user to add personal touch

Supplement List Format (待补充清单)

After the article draft, output a supplement list with 2-4 items:

───────────────────────────────
📝 建议补充的内容(可选)

1. 个人体验(位置:第 X 节)
   这里可以加你的实际使用感受
   提示:[具体问题引导,如"你这周用 GPT-5.4 做了什么?"]

2. 观点表态(位置:第 X 节)
   这里可以加你的明确立场
   提示:[如"你推荐升还是不推荐?为什么?"]

3. 个人案例(位置:可选)
   有没有真实用户故事可以加?
   提示:[如"有没有读者反馈可以分享?"]

───────────────────────────────

Purpose: Let user add personal experience and opinions to reduce AI-generated feel. Default: 2-4 items, each with specific location and prompt question.

Keyword Expansion Strategy

Auto-expand from user's topic:

Topic: "[用户主题]"
├── Core terms (CN + EN)
├── Event terms (related incidents)
├── Company/person terms
├── Concept terms (underlying ideas)
├── Comparison terms (X vs Y)
├── Industry terms
└── China-local terms (国内产品/平台)

Search in both English (primary sources) and Chinese (local perspectives), cross-validate.

Quick Start Prompts

Mode A: Rewrite from URL

使用多智能体工作流为我完成以下任务:

原文链接:[URL]

任务:
1. 抓取并分析原文,提炼核心信息
2. 联网搜索相关热点新闻和补充素材
3. 二次加工改写,增加新的论点和视角
4. 多轮打磨后输出微信公众号推文

写作标准:
- 简洁有力,有观点有干货
- 语言平实但有态度,不煽情
- 不把读者当小白,逻辑清晰节奏明快
- 尊重读者智商

重要要求:
- 所有数据必须有来源链接
- 不编造测试数据或案例
- 不添加"获取方式"、"下期预告"等运营内容
- 不确定内容标注"待验证"

排版要求:对比内容用不同颜色 section 标签区分,
避免抄袭,总字数 1200-1500 字,输出 Markdown 到当前目录。

Mode B: Generate from topic keyword

使用多智能体工作流为我完成以下任务:

话题:[关键词或一句话描述]

任务:
1. 联网搜索该话题最新动态、核心事件、各方观点
2. 搜索关联热点新闻,找到可以"借势"的内容
3. 整合素材,生成一篇有观点的微信公众号推文

写作标准:
- 简洁有力,有观点有干货
- 语言平实但有态度,不煽情
- 不把读者当小白,逻辑清晰节奏明快
- 尊重读者智商

重要要求:
- 所有数据必须有来源链接
- 不编造测试数据或案例
- 不添加"获取方式"、"下期预告"等运营内容
- 不确定内容标注"待验证"

排版要求:对比内容用不同颜色 section 标签区分,
总字数 1200-1500 字,输出 Markdown 到当前目录。

Scene Adaptation

ScenarioAdjustment
Source is short/thinIncrease Research + Hot News agent weight
Source is long/denseIncrease Strategy agent weight, focus on filtering
Topic-only (no source)All Phase 1 agents driven by keyword search
Stronger opinionsAdd "provide 3 controversial takes" to Strategy
More neutralAdd "present multiple viewpoints without judgment"
Ride trending waveMax Hot News agent, use Backdrop or Contrast mode
Non-tech topicAdjust search dimensions (finance→policy; social→legal)
Article seriesAdd "reserve 2-3 extension angles for follow-ups"
Breaking newsLimit Hot News search to 24-48 hours
Long-form deep diveTarget 2500-3000 words, expand to 7-8 sections

Troubleshooting

ProblemSolution
URL unreachableAsk user to paste text, or search article title
Few search resultsBroaden keywords, switch to English search
Weak hot news relevanceDowngrade to ★☆☆, analogy-only use
Missing stakeholder responseNote "no public statement as of search time"
Conflicting dataShow both sources with discrepancy noted
Major editorial issuesDon't patch — rewrite affected section from Phase 2

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.