Nature Reader

Full-Paper Markdown Reader

Use this skill to turn a research paper into a complete Markdown reading artifact.

The default output should read like a bilingual paper companion, not a summary dump:

• keep the extractable prose, paragraph structure, and section flow
• show original text and Chinese translation together at block level
• extract figures and tables as assets and place them at the first substantive mention or interpretation point
• keep captions attached to figures/tables with English caption text and Chinese caption translation
• preserve stable page and block anchors for traceability
• write a complete paper.md by default, plus source_map.json, translation_notes.md, and assets/

This skill is for papers, preprints, and conference proceedings across disciplines. It is not limited to Nature-family journals.

When to use

Use this skill when the user wants any of the following:

• translate an entire paper into a complete Markdown document
• make a paper easier to read without losing the original wording
• generate a full-paper reading file with original/translation alignment
• keep figures or tables visually close to the claims they support
• preserve exact source locations for every substantive block
• build a source-grounded markdown artifact rather than a slide deck or short summary

If the user only wants a summary, use a summarization skill instead. If the user only wants citation search, use a citation skill instead.

Non-negotiable defaults

When the user asks for paper translation, reading, nature-reader, 中英文对照, 原文对照, 全文翻译, or 翻译解读, produce a paragraph-level bilingual reader by default.

Do not replace the reader with:

• a Chinese-only summary
• a paper review without original/translation alignment
• figure captions without figure/table crops
• a list of key points detached from source locations
• only the abstract, introduction, or selected highlights

If constraints prevent full processing, still create a draft reader and clearly label missing pages, missing figures/tables, untranslated blocks, or low-confidence OCR/crops in translation_notes.md.

Core principle

Translate for meaning, not for style. Preserve the paper's structure, evidence, hedging, terminology, equations, units, and citation markers. Keep the output in prose paragraphs unless the source itself is tabular or list-like. Do not collapse the paper into keyword bullets or slide-style notes.

The reading file should help a reader move between:

• original text
• translated text
• source location
• figure or table evidence

Each substantive source block should have a stable anchor and a visible bilingual pair:

<a id="S001"></a>
**Source:** p.1 S001

**Original:** [source paragraph]

**中文:** [faithful Chinese translation]

For copyrighted publisher PDFs, keep chat responses short and point to the local artifact. In local paper.md, include the bilingual reader only for the user-provided source file or clearly lawful open-access content; avoid reproducing large copyrighted text directly in chat.

Workflow

1. Identify the source and paper type

Determine whether the source is:

• selectable-text PDF
• scanned PDF
• publisher HTML
• DOI or arXiv link
• pasted text or notes

Then identify the paper type at a high level:

• discovery or mechanism paper
• methods or algorithm paper
• resource or dataset paper
• conference paper
• review or perspective

This helps decide how tightly to couple text, figures, and captions.

2. Build a full-document source map before translating

If the user provides a full paper, process the entire document. Do not stop at the abstract, introduction, or a few representative pages unless the user explicitly asks for a preview.

Create stable IDs for source blocks:

• S001, S002, ... for body text
• C001, C002, ... for captions
• F001, F002, ... for figures
• T001, T002, ... for tables

For each block, capture:

• page number
• block type
• original text
• translation
• reading-order index
• nearby figure or table references
• first substantive figure/table mention when applicable
• confidence level when extraction is uncertain

Keep the source map stable so later questions can point back to the same IDs. For long papers, add a page index so the reader can jump across the whole document without losing location.

3. Translate conservatively

Translate every extractable substantive block with these rules:

• preserve technical terms unless a standard Chinese equivalent is clearly better
• keep gene names, protein names, formulas, model names, and symbols intact
• keep citations, superscripts, subscripts, and numeric values unchanged
• do not collapse methods details into vague prose
• keep paragraph order and section order unless the user asks for restructuring
• mark uncertain text instead of guessing when OCR or layout extraction is weak
• keep the source's paragraph form; do not convert dense prose into bullet-point keywords
• do not silently skip Methods, limitations, data availability, code availability, competing interests, or extended captions
• if the paper is too long for one pass, write paper.md incrementally by page/section and mark pending blocks rather than switching to summary mode

If a sentence contains multiple claims, keep the translation readable but do not split away the original evidence chain.

4. Extract and place figures and tables near the relevant discussion

Do not try to recreate the PDF pixel-for-pixel. Preserve semantic proximity instead.

Default placement rule:

• crop each figure/table into assets/ and show it near its first substantive mention in the body text
• keep the caption attached to the figure/table
• show both original caption and Chinese caption translation
• if the caption contains critical details, keep caption and figure together
• if a table is central to the claim, keep it near the paragraph that interprets it
• if a figure/table appears before the body discussion in PDF layout, still place it where it best supports the reading flow and add Placed near: p.X SYYY
• if a later section mentions the same figure/table again, link back to the already inserted figure/table block instead of duplicating it

If the paper has a complex multi-column layout, prefer a clean reading layout over exact visual mimicry.

4b. Crop figures and tables tightly

When extracting a figure or table image:

• crop only the figure or table content area, not the whole page
• use the smallest rectangle that fully contains the visual object
• exclude page headers, footers, surrounding prose, and unrelated margins
• keep the caption separate unless the caption is part of the requested visual crop
• if the crop box is uncertain, mark it as approximate instead of enlarging it

Precision matters more than convenience here. A slightly smaller but correct crop is better than a wider crop that includes unrelated page content.

Figure/table blocks in paper.md should use this shape:

<a id="F001"></a>
### Fig. 1. [short translated title]

**Placed near:** p.3 S012
**Source:** p.4 C001

![Fig. 1](assets/fig1.png)

**Original caption:** [caption text]

**中文图注:** [caption translation]

**Reading note:** [brief explanation of what to inspect in the figure]

5. Generate the Markdown file

Default output is a single full-paper paper.md file.

The Markdown must include:

• metadata header
• a short page/section index
• page-level or section-level divisions for long papers
• paragraph-level original/Chinese pairs for all extractable substantive text
• figure and table blocks placed near the relevant discussion
• source anchors on every substantive text, figure, caption, and table block
• a terminology table for recurring technical terms
• a short 阅读提示 / critical reading notes section only after the bilingual body, not as a replacement for it
• short uncertainty notes only when extraction is weak

Do not add an interactive Q&A panel or follow-up widget in the Markdown deliverable. If the user later asks a question, answer it in chat using the source map rather than embedding a conversational panel in the artifact.

If a browser preview is explicitly requested, a companion reader.html can be generated as a secondary artifact, but the Markdown file remains the primary output.

6. Answer follow-up questions with source grounding

When the user asks a question after the file is created:

• identify the most relevant source blocks first
• answer from the paper, not from memory
• cite the exact block IDs and page numbers
• if the answer depends on a figure or table, cite that too
• if the paper does not support the claim, say so plainly

Every substantive answer should include a source pointer such as:

• p.4 S012-S013
• Fig. 2 caption
• Table 1

If the answer is a synthesis across several blocks, list all supporting locations.

Output contract

Prefer these outputs:

• paper.md for the full-paper Markdown artifact
• source_map.json for stable source anchors
• translation_notes.md for terminology, uncertainty, and layout notes
• assets/ for extracted figures or cropped snippets when needed
• reader.html only when the user explicitly wants a browser preview

Do not hide missing information. If the source is incomplete, label the output as draft mode.

Before final response, verify:

• paper.md contains **Original:** and **中文:** block pairs
• every image/table link used in paper.md exists under assets/
• every figure/table in assets/ has a corresponding Markdown block and source pointer
• source_map.json parses as JSON and includes source block IDs
• translation_notes.md records skipped, uncertain, or draft-mode content

Tooling guidance

If the input is a PDF, load the pdf skill first for extraction and OCR guidance. If the user asks for a richer browser view, use web-artifacts-builder or frontend-design only as a preview layer on top of the Markdown workflow. If the user wants citation-level grounding to original text, keep the source map explicit and do not lose the page or block IDs.

Quality bar

Good output feels like a paper reader, not a machine translation dump.

It should let a reader:

• read the paper in two languages
• see where a claim came from
• inspect the nearby figure or table
• move through a complete Markdown file without losing source traceability

nature-reader 技能

nature-reader 是以 Markdown 为核心的全文论文阅读工作流。

功能

nature-reader 可以把 PDF、DOI、arXiv 链接、出版社 HTML 页面或粘贴的手稿文本转化为完整 Markdown 阅读材料，包含：

• 段落级原文与中文翻译，并以正文形式呈现。
• 提取出的图和表，放在首次实质性讨论它们的位置附近。
• 原始图注和中文图注翻译。
• 稳定的页码与文本块锚点，便于回溯来源。
• 紧凑图像裁剪和完整文档 source map。

主要产物

• paper.md
• source_map.json
• translation_notes.md
• assets/

reader.html 可以作为二级预览生成，但该技能默认以 Markdown 为中心，不默认生成交互式问答面板。

触发短语

当用户提出以下需求时使用该技能：

• 全文翻译
• 原文对照
• 中英文对照
• 图文对应
• 图表提取
• 翻译解读
• 全文 Markdown
• paper md
• source-grounded reading notes

注意事项

不要把该技能用于摘要、关键词列表或只做引用检索的任务。一旦触发，默认产物应是带有可见 Original / 中文 对照和图表卡片的 paper.md，不能只输出中文摘要。

Article Anatomy — a reading aid (Nat Commun 2025 CS/AI corpus)

Use this file as a reading aid while building the bilingual reader, to label the argumentative function of each block so the reader can locate the gap, the contribution, the decisive result, and the self-contained figure legends. It is distilled from a 2025 set of 20 open-access Nature Communications computer science / AI papers across genres.

This is an aid for locating structure, not a license to summarise. The

core/principles.md contract still holds: translate every block for meaning,

keep the bilingual side-by-side, and never degrade to a summary-only output.

Use the function labels to help a reader navigate, e.g. in a short orientation

note, not to replace the full translation.

Where each function lives

• Abstract = a funnel. Read it as five moves: field value → gap (almost

always after However) → hinge Here we show/present X → one quantified result → significance. The hinge sentence is the fastest way to state what the paper actually contributes.

• Introduction = hook → gap → contribution. Gap signal words to spot:

However / remains / Unfortunately / underexplored / the scarcity of … / Without X, Y cannot be …. The contribution is the explicit Here we… / In this work, we… sentence, often with a (Fig. 1) pointer.

• Results = conclusion-first. Each paragraph opens with the judgement; the

figure call (Fig. Xa, or Figure X shows…) and the numbers follow. Subheadings are often conclusions or method names, so the subheading list alone sketches the evidence ladder.

• Figure/Table legends are self-contained. Fig. N | bold noun title, then

a/b/c panels, with n=, error type, and test written in. A legend's last sentence sometimes advances a claim ("…indicating that the models are not predicting poses based on physics…") — flag it; it is interpretation, not description.

• **Discussion = restate contribution → why credible → wider meaning → limits

(Another limitation… / remains to be tested) → future work.** The limits sentence is where the paper bounds its own claim.

Genre tells (so the reader frames the paper correctly)

• Research article: own data, IMRaD, we + passive.
• Review: chapters by topic/modality synthesising others' citations, little

own data, closes with Conclusions and outlook.

• Perspective: history/era hook, numbered argument, normative X should…,

roadmap close.

• Comment: first-person I, rhetorical-question opening, analogy/history,

no IMRaD, no figures.

• Benchmark/framework: the gap is "the field lacks an agreed standard";

tables dominate; stresses community / reproducibility / versioning.

中文阅读提示

• 给读者的导航可标注每段功能(背景/空白/贡献/结果/局限),帮助快速抓论证骨架;

但不得因此省略逐段对照翻译或退化为摘要。

• "然而 / 仍是挑战 / 鲜有研究 / 缺乏 / 没有 X 就无法 Y"是空白信号词;Here we / 本文

之后是作者自述贡献。

• 图注通常自足(含 n、误差、检验);若图注末句给出推断结论,标注为"解读"而非"描述"。
• 先判定体裁(研究论文/综述/观点/评论/基准),再据此理解其组织方式与语气。

Figure and table extraction

Open this reference when extracting and placing figures or tables. It expands step 4 of the reading workflow.

Placement near the relevant discussion

Do not try to recreate the PDF pixel-for-pixel. Preserve semantic proximity instead.

Default placement rule:

• crop each figure/table into assets/ and show it near its first substantive mention in the body text
• keep the caption attached to the figure/table
• show both original caption and Chinese caption translation
• if the caption contains critical details, keep caption and figure together
• if a table is central to the claim, keep it near the paragraph that interprets it
• if a figure/table appears before the body discussion in PDF layout, still place it where it best supports the reading flow and add Placed near: p.X SYYY
• if a later section mentions the same figure/table again, link back to the already inserted figure/table block instead of duplicating it

If the paper has a complex multi-column layout, prefer a clean reading layout over exact visual mimicry.

Crop figures and tables tightly

When extracting a figure or table image:

• crop only the figure or table content area, not the whole page
• use the smallest rectangle that fully contains the visual object
• exclude page headers, footers, surrounding prose, and unrelated margins
• keep the caption separate unless the caption is part of the requested visual crop
• if the crop box is uncertain, mark it as approximate instead of enlarging it

Precision matters more than convenience here. A slightly smaller but correct crop is better than a wider crop that includes unrelated page content.

Figure/table block shape

Figure/table blocks in paper.md should use this shape:

<a id="F001"></a>
### Fig. 1. [short translated title]

**Placed near:** p.3 S012
**Source:** p.4 C001

![Fig. 1](assets/fig1.png)

**Original caption:** [caption text]

**中文图注:** [caption translation]

**Reading note:** [brief explanation of what to inspect in the figure]

Grounding Rules

Answering questions

When the user asks a follow-up question about the paper:

1. Find the most relevant source blocks. 2. Answer from those blocks first. 3. Cite the exact page and block IDs. 4. Include the figure or table if it is part of the evidence. 5. Say 原文未明确说明 if the paper does not support the claim.

Good answer pattern

• 结论
• 原文依据: p.5 S014-S016, Fig. 3 caption
• 补充说明: 这是译文中的概括，不是原文逐字表述

Bad answer pattern

• vague paraphrase without source IDs
• answer based only on the title or abstract when the question needs body text
• claiming support from a figure without citing the figure or caption
• inventing missing detail when OCR or extraction is uncertain

Translation rules

• Keep specialized terms stable.
• Keep equations, units, symbols, and citations unchanged.
• Do not over-simplify method steps.
• If a term has no clear Chinese equivalent, keep the original term and add a short note.
• Preserve paragraph-level original/Chinese alignment in paper.md.
• Do not convert a full-paper translation request into a Chinese-only summary or critique.
• If a full English paragraph cannot be included because of source restrictions or extraction failure, keep the block anchor and explain the limitation in translation_notes.md.

Figure and table rules

• Cite the caption when explaining a figure.
• Cite the relevant table row or table block when explaining a table.
• If the claim relies on both text and figure, cite both.
• If figure placement is uncertain, mark it as a layout approximation.
• Extract figures/tables to assets/ whenever possible.
• Place each figure/table card near the first substantive mention in the bilingual text.
• Include original caption, Chinese caption translation, and a short reading note.
• Do not use whole-page screenshots as figure/table replacements unless no tighter crop is possible; mark those as approximate.

Output Spec

Standard bundle

Produce these files when possible:

• paper.md
• source_map.json
• translation_notes.md
• assets/ for extracted images, crops, or figure snippets
• reader.html only when the user explicitly asks for a browser preview

Full-text mode

When the source is a full paper, include all pages or all extractable sections in the reader. Do not limit the bundle to selected pages, a teaser excerpt, or the abstract unless the user explicitly requests a preview.

paper.md is the primary deliverable. It must expose paragraph-level bilingual alignment:

<a id="S001"></a>
**Source:** p.1 S001

**Original:** ...

**中文:** ...

For source material that cannot be extracted or translated confidently, keep the source anchor and write a visible uncertainty note instead of dropping the block.

source_map.json

Keep a stable source map so follow-up questions can cite the same anchors.

{
  "paper": {
    "title": "",
    "venue": "",
    "source_type": "pdf|html|doi|arxiv|text",
    "language": "en",
    "source_path": ""
  },
  "blocks": [
    {
      "id": "S001",
      "page": 1,
      "type": "heading|paragraph|caption|table|table_row|note",
      "order": 1,
      "original_text": "",
      "translation": "",
      "bbox": [0, 0, 0, 0],
      "confidence": "high|medium|low",
      "refs": ["F001", "T001"],
      "insert_after": "S001"
    }
  ],
  "pages": [
    {
      "page": 1,
      "block_ids": ["S001", "S002", "S003", "C001"]
    }
  ],
  "figures": [
    {
      "id": "F001",
      "page": 3,
      "caption_id": "C001",
      "image_path": "",
      "bbox": [0, 0, 0, 0],
      "placement_hint": "near_first_mention",
      "placed_after": "S012",
      "alt_text": ""
    }
  ],
  "glossary": [
    {
      "term": "",
      "translation": "",
      "note": ""
    }
  ]
}

paper.md

The Markdown reader should support:

• stable headings in paper order
• paragraph-level original/Chinese pairs
• source IDs on every substantive block
• figure/table cards near the relevant prose
• English captions and Chinese caption translations
• page navigation for full papers
• terminology notes and uncertainty notes

reader.html

The page should support:

• desktop side-by-side original and translation
• mobile stacked layout
• clickable source IDs on every block
• figure cards near the relevant text
• section navigation
• page navigation for full papers

Do not add a question area unless explicitly requested.

Layout rules

• Keep paragraph alignment stable.
• Keep captions attached to their figures.
• Show tables where they are explained, not only where they appear in the PDF.
• Prefer semantic proximity over exact visual reconstruction.
• If a figure is referenced across multiple sections, anchor it at the first substantive discussion and link later mentions back to it.
• Crop figures and tables with the tightest valid bounding box.
• Do not use a full-page screenshot when the actual content occupies a smaller region.
• If the exact crop box cannot be verified, label the crop as approximate.
• For full papers, preserve page order and include a page index.

Figure/table card format

<a id="F001"></a>
### Fig. 1. 中文短标题

**Placed near:** p.3 S012
**Source:** p.4 C001

![Fig. 1](assets/fig1.png)

**Original caption:** ...

**中文图注:** ...

**Reading note:** ...

Every image/table asset must have a corresponding card in paper.md. Every card must identify the source caption and placement block.

Citation format in the page

Use short, stable source pointers:

• p.7 S021
• p.8 C003
• Fig. 2
• Table 1

For follow-up answers, combine page and block ID when available.

Output contract

Prefer these outputs:

• paper.md for the full-paper Markdown artifact
• source_map.json for stable source anchors
• translation_notes.md for terminology, uncertainty, and layout notes
• assets/ for extracted figures or cropped snippets when needed
• reader.html only when the user explicitly wants a browser preview

Do not hide missing information. If the source is incomplete, label the output as draft mode.

Pre-response verification

Before final response, verify:

• paper.md contains **Original:** and **中文:** block pairs
• every image/table link used in paper.md exists under assets/
• every figure/table in assets/ has a corresponding Markdown block and source pointer
• source_map.json parses as JSON and includes source block IDs
• translation_notes.md records skipped, uncertain, or draft-mode content

Tooling guidance

• If the input is a PDF, load the pdf skill first for extraction and OCR guidance.
• If the user asks for a richer browser view, use web-artifacts-builder or frontend-design only as a preview layer on top of the Markdown workflow.
• If the user wants citation-level grounding to original text, keep the source map explicit and do not lose the page or block IDs.

Core principles (reader)

Use this skill to turn a research paper into a complete Markdown reading artifact. The default output should read like a bilingual paper companion, not a summary dump:

• keep the extractable prose, paragraph structure, and section flow
• show original text and Chinese translation together at block level
• extract figures and tables as assets and place them at the first substantive mention or interpretation point
• keep captions attached to figures/tables with English caption text and Chinese caption translation
• preserve stable page and block anchors for traceability
• write a complete paper.md by default, plus source_map.json, translation_notes.md, and assets/

This skill is for papers, preprints, and conference proceedings across disciplines. It is not limited to Nature-family journals. If the user only wants a summary, use a summarization skill instead. If the user only wants citation search, use a citation skill instead.

Non-negotiable defaults

When the user asks for paper translation, reading, nature-reader, 中英文对照, 原文对照, 全文翻译, or 翻译解读, produce a paragraph-level bilingual reader by default.

Do not replace the reader with:

• a Chinese-only summary
• a paper review without original/translation alignment
• figure captions without figure/table crops
• a list of key points detached from source locations
• only the abstract, introduction, or selected highlights

If constraints prevent full processing, still create a draft reader and clearly label missing pages, missing figures/tables, untranslated blocks, or low-confidence OCR/crops in translation_notes.md.

Core principle

Translate for meaning, not for style. Preserve the paper's structure, evidence, hedging, terminology, equations, units, and citation markers. Keep the output in prose paragraphs unless the source itself is tabular or list-like. Do not collapse the paper into keyword bullets or slide-style notes.

The reading file should help a reader move between:

• original text
• translated text
• source location
• figure or table evidence

Each substantive source block should have a stable anchor and a visible bilingual pair:

<a id="S001"></a>
**Source:** p.1 S001

**Original:** [source paragraph]

**中文:** [faithful Chinese translation]

Copyright caution

For copyrighted publisher PDFs, keep chat responses short and point to the local artifact. In local paper.md, include the bilingual reader only for the user-provided source file or clearly lawful open-access content; avoid reproducing large copyrighted text directly in chat.

Quality bar

Good output feels like a paper reader, not a machine translation dump. It should let a reader:

• read the paper in two languages
• see where a claim came from
• inspect the nearby figure or table
• move through a complete Markdown file without losing source traceability

Reading workflow

Run these six steps for any paper-reading job. Steps 1-2 build the source map, 3-5 produce the artifact, 6 covers follow-up questions.

1. Identify the source and paper type

The source-format fragment loaded for this job covers how to extract from the specific input. At a high level, also identify the paper type so you know how tightly to couple text, figures, and captions:

• discovery or mechanism paper
• methods or algorithm paper
• resource or dataset paper
• conference paper
• review or perspective

2. Build a full-document source map before translating

If the user provides a full paper, process the entire document. Do not stop at the abstract, introduction, or a few representative pages unless the user explicitly asks for a preview.

Create stable IDs for source blocks:

• S001, S002, ... for body text
• C001, C002, ... for captions
• F001, F002, ... for figures
• T001, T002, ... for tables

For each block, capture: page number, block type, original text, translation, reading-order index, nearby figure or table references, first substantive figure/table mention when applicable, and confidence level when extraction is uncertain.

Keep the source map stable so later questions can point back to the same IDs. For long papers, add a page index so the reader can jump across the whole document without losing location.

3. Translate conservatively

Translate every extractable substantive block with these rules:

• preserve technical terms unless a standard Chinese equivalent is clearly better
• keep gene names, protein names, formulas, model names, and symbols intact
• keep citations, superscripts, subscripts, and numeric values unchanged
• do not collapse methods details into vague prose
• keep paragraph order and section order unless the user asks for restructuring
• mark uncertain text instead of guessing when OCR or layout extraction is weak
• keep the source's paragraph form; do not convert dense prose into bullet-point keywords
• do not silently skip Methods, limitations, data availability, code availability, competing interests, or extended captions
• if the paper is too long for one pass, write paper.md incrementally by page/section and mark pending blocks rather than switching to summary mode

If a sentence contains multiple claims, keep the translation readable but do not split away the original evidence chain. Build the Terminology Ledger (../../../_shared/core/terminology-ledger.md) as you translate so recurring terms stay consistent across the whole document.

4. Extract and place figures and tables near the relevant discussion

Crop each figure/table into assets/ and place it near its first substantive mention, keeping the caption attached with both original and Chinese caption text. For the full placement and tight-crop rules, and the figure/table block shape, open references/figure-extraction.md.

5. Generate the Markdown file

Default output is a single full-paper paper.md file. It must include:

• metadata header
• a short page/section index
• page-level or section-level divisions for long papers
• paragraph-level original/Chinese pairs for all extractable substantive text
• figure and table blocks placed near the relevant discussion
• source anchors on every substantive text, figure, caption, and table block
• a terminology table for recurring technical terms (from the Terminology Ledger)
• a short 阅读提示 / critical reading notes section only after the bilingual body, not as a replacement for it
• short uncertainty notes only when extraction is weak

Do not add an interactive Q&A panel or follow-up widget in the Markdown deliverable. If a browser preview is explicitly requested, a companion reader.html can be generated as a secondary artifact, but the Markdown file remains the primary output.

6. Answer follow-up questions with source grounding

When the user asks a question after the file is created, answer from the paper, not from memory, and cite exact block IDs and page numbers. For the full grounding rules, open references/grounding-rules.md.

Source: DOI or arXiv identifier

The user gave a bare DOI or arXiv id/link that must be resolved before reading.

• Resolve the identifier to the actual article first:
• arXiv → the abstract page, then the PDF (and HTML/LaTeX source when available).
• DOI → the publisher landing page, then the open-access PDF or HTML if lawfully available.
• After resolving, this becomes a pdf-text, scanned-pdf, or html job — load that fragment and follow it for extraction. This fragment only covers retrieval.
• Capture bibliographic metadata (title, authors, venue, year, DOI/arXiv id) for the paper.md metadata header.
• Prefer the open-access version (arXiv, author copy, PMC) when the version of record is paywalled. Note which version was read in translation_notes.md, since arXiv and published versions can differ.
• If the identifier cannot be resolved or only the abstract is reachable, build a draft reader from what is available and clearly mark the rest as not retrieved. Do not fabricate body text.
• Apply the copyright caution to the resolved artifact.

Source: publisher or preprint HTML

The source is an HTML page (publisher site, preprint server, or similar).

• Extract the article body; strip site navigation, cookie banners, related-article rails, reference-manager widgets, and advertisements.
• Keep the section structure and paragraph order from the article markup.
• Figures and tables are usually separate image/HTML elements — capture each figure image and its caption, and place per references/figure-extraction.md. Reconstruct HTML tables faithfully rather than screenshotting them when the markup is clean.
• Preserve inline math (MathML/LaTeX/images), superscript citation markers, and links to the reference list.
• Respect the copyright caution: for paywalled or all-rights-reserved pages, keep chat output short and point to the local artifact. Reproduce full bilingual text only for clearly lawful open-access content.
• If the page is JavaScript-rendered and content is missing, note what could not be retrieved instead of inventing it.

Source: pasted text or notes

The user pasted prose or notes directly, with no retrievable original layout or page images.

• Treat the pasted text as the source of truth. Build the source map and bilingual pairs from it.
• Page numbers may be unknown. Use sequential block IDs (S001, S002, ...) and, where the paste shows section headings, use section-level anchors instead of page anchors. Note in translation_notes.md that page anchors are unavailable.
• There are usually no figure/table images. Do not invent crops. If the text references figures/tables, keep the references and captions as text blocks and note that the visual assets were not provided.
• If the paste is clearly partial (for example abstract and intro only), build the reader for what was given and label it draft mode; do not backfill missing sections from memory.
• Preserve any citation markers, equations, and symbols exactly as pasted.
• Keep the bilingual reader format; do not collapse pasted prose into a summary just because layout metadata is missing.

Source: selectable-text PDF

The PDF has an extractable text layer. Load the pdf skill first for extraction guidance.

• Extract the text layer directly; do not OCR text that is already selectable.
• Process the whole document, not just the first pages. Build the source map (step 2) across every page.
• Watch for multi-column layouts: recover natural reading order rather than top-to-bottom raw stream order.
• Keep ligatures, hyphenated line breaks, superscripts, subscripts, and math intact; rejoin words split across line breaks.
• Figures and tables are images embedded in the page — crop them per references/figure-extraction.md; do not paste the page text of a table where the table image belongs.
• If some pages have a text layer and others are scanned, treat the scanned pages with the scanned-pdf rules and mark them with a confidence note.

Source: scanned PDF (OCR required)

The PDF is image-only or has an unreliable text layer. Load the pdf skill first for OCR guidance.

• OCR every page; do not assume a usable text layer exists.
• Record a confidence level for each block in the source map, and mark low-confidence blocks explicitly in translation_notes.md rather than guessing.
• Preserve the original wording where OCR is confident; flag, do not silently "correct", garbled text.
• Be careful with numerals, units, symbols, gene/protein names, and chemical formulas — OCR errors here change meaning. Cross-check against context and mark uncertainty.
• Figures and tables are page regions: crop them per references/figure-extraction.md. For low-quality scans, a tight correct crop still beats a wide noisy one.
• If pages are skewed, rotated, or partly cut off, note the affected pages and translate only what is legible.