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:

• Path A: research-first article use for: topic, keyword, question, notes, transcript, subtitle file goal: build the article from a research brief and evidence ledger

• Path B: source-to-WeChat edition 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 -> tutorial
• thesis, trend, strategy, critique, case material -> deep-analysis
• multi-topic roundup -> newsletter

Capability Aliases

Resolve capabilities through internal aliases, not vendor-style names:

• source-ingest
• markdown-polish
• inline-visuals
• cover-art
• article-design
• wechat-render
• wechat-draft
• multi-platform-distribute (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 source.md
• source figures carry higher credibility than AI-generated images and must be preferred in the final article