paper-deep-dive
Paper Deep Dive
Short description: PDF to deep paper notes workflow. Historical source: Feishu wiki AI Research Skills; current durable delivery is Notion-first.
Use this skill when the user wants a complete paper reading workflow from PDF to stable notes, paper card, assets, and shareable summaries.
Single Source of Truth
This skill is the only canonical delivery standard for single-paper deep dives. Other skills may trigger, route, write to Feishu/Notion/Obsidian, preserve Chinese wording, or distill the finished deep dive into a wiki, but they must not define a second deep-dive structure or mark a package complete under weaker rules.
When any user request says deep dive, 深读, 详细解析, detailed-read, dive into, 精读这篇论文, or requests a complete 原文中译稿, treat it as this full workflow unless the user explicitly asks for a lighter artifact such as quick summary, paper card only, partial translation, or English manuscript only. A lighter artifact must be labeled as such and must not be called a compliant deep dive.
The completion standard is product-level, not effort-level. A good summary or a partial translation is still incomplete. A package is compliant when the main page contains the complete Chinese manuscript, and figures/captions, formulas, references, hierarchy, and target-platform read-back verification all pass the delivery gate below. A 精读稿 is not part of the default package. Do not add a main-page 精读稿 / 精读部分, Paper Card, editable 论文解析树, source-order close reading, or mechanism synthesis unless the user explicitly requests that artifact in the current task. Child pages are not part of the default completion gate. Missing a 精读稿 is never a completion failure.
Canonical Platform Delivery Gate
Also use research-doc-workflow and notion-doc-workflow for new deep dives. Notion is the canonical durable target because Feishu storage is limited. Keep one Markdown-first manuscript and close-reading structure; only Notion hierarchy, native equations/captions, uploads, editable trees, citation chrome, and write verification need platform adaptation. Do not create or maintain a parallel Feishu deep-dive copy unless the user explicitly requests a legacy repair or migration.