Research to WeChat
Use this skill as a research-first control plane. Do not duplicate downstream skill wording.
Core Rules
- - Match the user's language.
- Ask one question at a time.
- Ask only when the answer changes source interpretation, structural frame, style fidelity, or draft publishing behavior.
- Keep Markdown as the canonical article asset until the HTML handoff.
- Save a draft only. Never publish live.
- Separate verified fact, working inference, and open question.
- Every major claim must be traceable to a source. Collect source URLs during research.
- Every article must end with a "## 参考链接" or "## References" section listing all sources.
- Apply the full normalization checklist to every article before refinement. Source artifacts, broken formatting, and LaTeX fragments must not survive into the final draft.
- Every inline image must pass a two-tier evaluation: first eliminate disqualifying defects, then verify content match to the surrounding text.
- Never pretend the workflow did interviews, long field research, team debate, or hands-on testing when it did not.
- Prefer visible disclosure of AI assistance and source scope. Refuse human-only framing that would misrepresent the process.
- Treat source capture as a runtime boundary: preserve title, author, description, body text, and image list before rewriting.
Operating Paths
Route the request into one of two paths:
use for: topic, keyword, question, notes, transcript, subtitle file
goal: build the article from a research brief and evidence ledger
use for: article text, markdown file, article URL, WeChat URL
goal: preserve the useful source core, then rebuild it for WeChat reading and distribution
Default routing:
- - procedural or tool-teaching material -> INLINECODE2
- thesis, trend, strategy, critique, case material -> INLINECODE3
- multi-topic roundup -> INLINECODE4
Capability Aliases
Resolve capabilities through internal aliases, not vendor-style names:
- - INLINECODE5
- INLINECODE6
- INLINECODE7
- INLINECODE8
- INLINECODE9
- INLINECODE10
- INLINECODE11
- INLINECODE12 (loaded only when Phase 7 is triggered)
Use the current alias map in capability-map.md.
Accepted Inputs
- - keyword, topic phrase, or question
- notes, outline, or raw material dump
- article text
- markdown file
- PDF paper, report, or whitepaper
- article URL
- WeChat article URL
- video URL
- full transcript
- subtitle file that can be expanded into a full transcript
PDF policy:
- - when the source is a PDF paper or report, extract all figures, charts, tables, and diagrams as image assets
- save extracted figures to
imgs/source-fig-*.png with captions and page numbers recorded in INLINECODE14 - source figures carry higher credibility than AI-generated images and must be preferred in the final article
Video policy:
- - a video source is valid only when the workflow can obtain the full spoken transcript
- first attempt transcript recovery from the page, captions, or subtitle assets
- if the page exposes only metadata, description, or chapter markers, do not start article generation
- if no full transcript is obtainable, ask for the transcript or subtitle file and wait
Output
Create one workspace per article:
INLINECODE15
Required assets:
- - INLINECODE16
- INLINECODE17
- INLINECODE18
- INLINECODE19
- INLINECODE20
- INLINECODE21
- INLINECODE22
- INLINECODE23
- inline illustration files referenced by the markdown body
Required frontmatter in final markdown:
- - INLINECODE24
- INLINECODE25
- INLINECODE26
- INLINECODE27
- INLINECODE28
- INLINECODE29
- INLINECODE30
- INLINECODE31
- INLINECODE32
Required records outside the article:
must capture: target reader, thesis, must-cover points, frame choice, and what cannot be dropped
must capture: verified facts, working inferences, open questions, and source notes
must capture:
pathMode,
styleMode,
structureFrame,
sourceType,
confidence,
draftStatus, and output paths
manifest.json.outputs.wechat must include:
markdown,
html,
cover_image,
title,
author,
digest, and
images
optional platform fields (
xiaohongshu,
jike,
xiaoyuzhou,
moments) are added when Phase 8 runs
Script Directory
Determine this SKILL.md directory as SKILL_DIR, then use ${SKILL_DIR}/scripts/<name>.
| Script | Purpose |
|---|
| INLINECODE56 | WeChat article fetch (Python, simulates WeChat mobile UA) |
| INLINECODE57 |
OpenClaw skill installer (copies to
~/.openclaw/skills/) |
Provenance Contract
The workflow must keep a compact evidence ledger throughout the run:
- - what came from the user
- what came from fetched source material
- what was added as supporting context
- what remains uncertain
Default article disclosure should state:
- - what AI did
- what the human provided or reviewed, if known
- what the evidence base was
- what confidence limit remains, if the source packet is thin
Delivery Ladder
Resolve WeChat draft delivery in this order:
- 1. API draft when credentials and converter tooling are ready
- automated browser draft when the worker can drive the editor safely
- assisted browser draft when login or selectors need user help
- manual handoff with exact file paths when automation fails
Style Resolution
Resolve style in this order:
- 1. explicit user instruction
- preset mode
- author mode
- custom brief
Use the full style system in style-engine.md.
Execution
Run the article through these phases:
- 1. intake and route selection
- source packet, brief, and strategic clarification
- research architecture with structured question lattice (32+ questions across 4 cognitive layers)
- research merge and evidence ledger
- frame-routed master draft with full normalization checklist and writing framework self-check
- refinement, image strategy, visual evaluation, and design selection
- WeChat HTML rendering, draft upload, and manifest
- (optional) multi-platform content generation and distribution
Phase 8 only executes when the user explicitly requests it (e.g., "多平台分发", "转小红书", "转即刻", "写朋友圈文案", "做播客脚本").
Use the execution contract in execution-contract.md.
Use the design guide in design-guide.md for article design selection.
Use the platform copy specs in platform-copy.md for Phase 8.
Done Condition
The skill is complete only when all of these hold:
- - the article reads as researched before it reads as polished
- the route choice and structure frame fit the source instead of forcing one house style
- the chosen style is visible without collapsing into imitation
- the writing framework self-check for the chosen frame has been applied
- the evidence ledger clearly separates fact from interpretation
- every visual adds narrative or explanatory value
- the normalization checklist has been applied: no citation artifacts, no LaTeX, no broken tables, no scraped UI remnants
- every image placeholder was evaluated against placement criteria before generation, and every generated image passed the two-tier quality check
- markdown and HTML agree on title, summary, cover, and image paths
- INLINECODE59 agrees with the actual output set and draft state
- the article does not overclaim research effort or authorship
- the workflow can stop safely at the highest-quality completed artifact if a later handoff fails
- if Phase 8 was triggered, platform copies follow platform-copy.md specs and manifest includes their output entries
研究到微信
将此技能作为以研究为先导的控制平面。不要重复下游技能的措辞。
核心规则
- - 匹配用户的语言。
- 一次只问一个问题。
- 仅当答案改变来源解读、结构框架、风格保真度或草稿发布行为时才提问。
- 在移交HTML之前,保持Markdown作为规范的稿件资产。
- 仅保存草稿。切勿发布上线。
- 区分已核实的事实、工作中的推论和未解决的问题。
- 每个主要主张必须可追溯至来源。在研究过程中收集来源URL。
- 每篇文章必须以## 参考链接或## References部分结尾,列出所有来源。
- 在精炼之前,对每篇文章应用完整的规范化检查清单。来源痕迹、格式错误和LaTeX片段不得出现在最终草稿中。
- 每张内嵌图片必须通过两级评估:首先消除不合格缺陷,然后验证内容与周围文本的匹配度。
- 切勿假装工作流程进行了采访、长期实地研究、团队辩论或动手测试(如果实际并未进行)。
- 倾向于明确披露AI辅助和来源范围。拒绝可能歪曲流程的纯人类视角描述。
- 将来源捕获视为运行时边界:在重写前保留标题、作者、描述、正文和图片列表。
操作路径
将请求路由至以下两条路径之一:
用于:主题、关键词、问题、笔记、转录稿、字幕文件
目标:基于研究简报和证据台账构建文章
用于:文章文本、markdown文件、文章URL、微信URL
目标:保留有用的来源核心,然后为微信阅读和分发重建
默认路由:
- - 程序性或工具教学材料 -> 教程
- 论文、趋势、策略、评论、案例材料 -> 深度分析
- 多主题汇总 -> 通讯稿
能力别名
通过内部别名(而非供应商风格名称)解析能力:
- - source-ingest(来源摄取)
- markdown-polish(Markdown润色)
- inline-visuals(内嵌视觉元素)
- cover-art(封面图)
- article-design(文章设计)
- wechat-render(微信渲染)
- wechat-draft(微信草稿)
- multi-platform-distribute(多平台分发,仅在触发阶段7时加载)
使用capability-map.md中的当前别名映射。
接受的输入
- - 关键词、主题短语或问题
- 笔记、大纲或原始材料转储
- 文章文本
- markdown文件
- PDF论文、报告或白皮书
- 文章URL
- 微信文章URL
- 视频URL
- 完整转录稿
- 可扩展为完整转录稿的字幕文件
PDF政策:
- - 当来源是PDF论文或报告时,提取所有图形、图表、表格和图示作为图片资产
- 将提取的图形保存至imgs/source-fig-*.png,并在source.md中记录标题和页码
- 来源图形的可信度高于AI生成的图片,在最终文章中必须优先使用
视频政策:
- - 仅当工作流程能获取完整口语转录稿时,视频来源才有效
- 首先尝试从页面、字幕或字幕资产中恢复转录稿
- 如果页面仅暴露元数据、描述或章节标记,则不要开始文章生成
- 如果无法获取完整转录稿,则请求提供转录稿或字幕文件并等待
输出
每篇文章创建一个工作空间:
research-to-wechat/YYYY-MM-DD-/
必需资产:
- - source.md
- brief.md
- research.md
- article.md
- article-formatted.md
- article.html
- manifest.json
- imgs/cover.png
- Markdown正文引用的内嵌插图文件
最终Markdown中必需的前置元数据:
- - title(标题)
- author(作者)
- description(描述)
- digest(摘要)
- coverImage(封面图片)
- styleMode(风格模式)
- sourceType(来源类型)
- structureFrame(结构框架)
- disclosure(披露声明)
文章外必需的记录:
必须包含:目标读者、核心论点、必须涵盖的要点、框架选择,以及不可删除的内容
必须包含:已核实的事实、工作中的推论、未解决的问题和来源注释
必须包含:pathMode(路径模式)、styleMode(风格模式)、structureFrame(结构框架)、sourceType(来源类型)、confidence(置信度)、draftStatus(草稿状态)和输出路径
manifest.json.outputs.wechat 必须包含:markdown、html、cover_image、title、author、digest和images
可选平台字段(xiaohongshu、jike、xiaoyuzhou、moments)在阶段8运行时添加
脚本目录
将此SKILL.md所在目录确定为SKILLDIR,然后使用${SKILLDIR}/scripts/。
| 脚本 | 用途 |
|---|
| scripts/fetchwechatarticle.py | 微信文章抓取(Python,模拟微信移动端UA) |
| scripts/install-openclaw.sh |
OpenClaw技能安装程序(复制到~/.openclaw/skills/) |
溯源契约
工作流程必须在整个运行过程中保持紧凑的证据台账:
- - 哪些来自用户
- 哪些来自抓取的来源材料
- 哪些作为支持性上下文添加
- 哪些仍然不确定
默认文章披露声明应说明:
- - AI做了什么
- 人类提供或审查了什么(如果已知)
- 证据基础是什么
- 如果来源包信息薄弱,仍存在什么置信度限制
交付阶梯
按以下顺序解决微信草稿交付:
- 1. 当凭据和转换工具就绪时,通过API提交草稿
- 当工作程序能安全驱动编辑器时,通过自动化浏览器提交草稿
- 当登录或选择器需要用户帮助时,通过辅助浏览器提交草稿
- 当自动化失败时,通过精确文件路径手动移交
风格解析
按以下顺序解析风格:
- 1. 明确的用户指令
- 预设模式
- 作者模式
- 自定义简报
使用style-engine.md中的完整风格系统。
执行
通过以下阶段运行文章:
- 1. 接收和路径选择
- 来源包、简报和策略澄清
- 研究架构与结构化问题网格(跨4个认知层共32+个问题)
- 研究合并与证据台账
- 基于框架路由的主稿,包含完整的规范化检查清单和写作框架自检
- 精炼、图片策略、视觉评估和设计选择
- 微信HTML渲染、草稿上传和清单
- (可选)多平台内容生成和分发
阶段8仅在用户明确请求时执行(例如,多平台分发、转小红书、转即刻、写朋友圈文案、做播客脚本)。
使用execution-contract.md中的执行契约。
使用design-guide.md中的设计指南进行文章设计选择。
使用platform-copy.md中的平台文案规范进行阶段8操作。
完成条件
仅当满足以下所有条件时,技能才算完成:
- - 文章读起来像是经过研究而非仅仅润色
- 路径选择和结构框架适合来源,而非强行套用一种风格
- 所选风格可见,但不沦为模仿
- 所选框架的写作框架自检已应用
- 证据台账清晰区分事实与解读
- 每个视觉元素都增加了叙事或解释价值
- 规范化检查清单已应用:无引用痕迹、无LaTeX、无损坏表格、无抓取的UI残留
- 每个图片占位符在生成前已根据放置标准进行评估,且每个生成的图片已通过两级质量检查
- Markdown和HTML在标题、摘要、封面和图片路径上保持一致
- manifest.json与实际输出集和草稿状态一致
- 文章未夸大研究工作量或作者身份
- 如果后续移交失败,工作流程能在最高质量的已完成稿件处安全停止
- 如果阶段8已触发,平台文案遵循platform-copy.md规范,且清单包含其输出条目