Paper reading

Treat a paper report as an argument with inspectable evidence, not a longer abstract. Preserve the familiar paper-type structure and the original technical template while cutting any sentence that adds no mechanism, evidence, comparison, limitation, or implication.

Resolve <skill-dir> as the directory containing this file before using bundled scripts or assets.

In examples, PYTHON_EXE means the actual interpreter of a compatible active or isolated environment—for example python3, python, py -3, or an absolute venv executable. Resolve it for the current platform; do not run the token literally or assume one command name exists.

1. Choose only the output format

Honor an explicit or clearly implied format. Otherwise ask once whether the user wants Markdown or HTML, then wait. Explain briefly: Markdown is light and editable; HTML adds the designed reading surface, one section outline, static mathematics, and click-to-enlarge visuals.

Do not ask for a reading level. Use one standard throughout: read the complete argument, retain all load-bearing technical detail, and write it concisely. Do not run reproduction experiments as part of this workflow.

Gate: record format; do not silently choose it when genuinely ambiguous.

2. Ground the source

Accept a local or remote PDF, official full-text HTML, or complete pasted text. Prefer PDF when available because page and figure anchors are stable; do not make PDF mandatory.