nature-paper-card

Nature Paper Card - Router

Use this skill to turn one paper into an evidence-grounded research card, not a translated abstract, generic summary, reviewer report, or publication article.

The skill uses:

• a static core under static/core/ for principles, workflow, and the fixed output contract;
• one paper-type fragment under static/fragments/paper_type/;
• on-demand references for evidence labels, the exact card schema, and research-idea checks.

Routing protocol

Follow these steps every time.

1. Load the manifest and core layer

Read manifest.yaml, then read every file under always_load. Do not generate the card from this router alone.

2. Establish the source boundary

Identify which material is available:

• full paper with figures and tables;
• paper text without reliable layout;
• abstract or metadata only;
• an existing nature-reader artifact with stable source IDs.

Prefer an existing nature-reader artifact when supplied. Do not repeat full bilingual translation or figure extraction. If only partial material is available, create a visibly partial card and mark every unsupported section Not assessable from supplied material.

For a PDF or nature-reader source-map JSON, the bundled script is mandatory.

1. Resolve SKILL_DIR as the directory containing this loaded SKILL.md.
2. Verify SKILL_DIR/scripts/prepare_paper.py exists.
3. Run exactly the bundled script by its resolved path:

python "SKILL_DIR/scripts/prepare_paper.py" INPUT \
  --output WORKDIR/source_bundle.json

Add --render-dir WORKDIR/rendered-pages when visual page review is needed. Inspect the script exit code and the bundle validation block before drafting.

For source-map input, also inspect locator_summary and unlocated_blocks. Only records under pages have verified positive PDF page locators. Missing or invalid page locators remain in unlocated_blocks with an explicit status and must be cited structurally, never as page 1.