← ClaudeAtlas

render-paperlisted

Compile a LaTeX paper (ACM/IEEE/arXiv) to PDF and render its pages to high-DPI PNGs for mobile/on-screen review. Use whenever asked to "render / compile / show / screenshot" a .tex paper, or to produce phone-readable page images of a draft (e.g. ACM/IEEE workshop submissions). Encodes the toolchain + the gotchas already hit (font-expansion crash, filecontents bib, bibtex cycle).
zernie/paperlint · ★ 7 · Code & Development · score 74
Install: claude install-skill zernie/paperlint
<!-- vigiles:sha256:0943963cae95f8f1 compiled from skills/render-paper/SKILL.md.spec.ts --> # render-paper — .tex → PDF → readable page PNGs ## Run me 🔴 FIRST, before any other step: ``` node .claude/skills/paper-pipeline/scripts/announce.mjs render-paper <paper-dir> ``` An advisory pass cannot be observed failing — silence is both its error state and its normal state — so starting is an event, and events get written down. Turns a LaTeX source into (a) a compiled PDF and (b) per-page PNG images crisp enough to read the font on a phone. Encodes the exact toolchain and the failures already debugged, so it works first try. ## 🔴 This is a COMMAND, not a stage You run it twenty times a day. It has no position in the pipeline and nothing waits its turn to reach it: **any `.tex` / `paper.md` edit is the trigger** — render, then eyeball pages 1–2 before believing anything you say about the paper. Scorecard row **`render`** (in the CONTINUOUS section of `paper-pipeline`) records the last render and its page count; that page count is the hard input the `tighten-paper` structure gate is blocked on, which is the only sense in which anything "comes after" this. *It used to carry a number in a stage list, which made a compile look like a milestone you pass once. That list was replaced on 2026-08-03; nothing about the toolchain below changed.* ## Toolchain (one command, not a checklist) - **Compiler:** TeX Live, installed by paperlint with exactly the packages the venue profiles