paper2poster
Convert academic papers (PDF) into conference posters (HTML/PNG). You are the conductor: you decide what each section needs — an original paper figure or text — write the outline, hand-author the poster HTML, and iterate on the render using your own visual read and a blind-reader content quiz. Use when the user wants a poster from a paper PDF.
npx skills add QuZhan51496/paper2anything --skill paper2poster --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Paper2Poster — Conference Poster Skill (You as Conductor) Convert a paper PDF into an academic conference poster (HTML/PNG) by walking a small set of CLI scripts. **You are the conductor**: this file is the recipe, not an orchestrator. There is no `run_pipeline.py` — at each step you run one Bash command, read the intermediate artifact, and ask the user for confirmation at the decision points below. ```text PDF → parse_pdf.py (MinerU → content.md + figures/) → intake QA (you ask size/venue/authors/visual policy) → auto_outline.py (digest.json + assets[]) → choose visuals (you read parsed/figures/ + captions: which sections use an original figure, which use text) → outline.json (you write from content.md; user confirms) → poster.html (you hand-author the poster: original figures where they help, text elsewhere) → render + score (Playwright PNG → deterministic geometry check + your own visual read + blind-reader content quiz) → iterate on poster.html (edit + re-render + re-score until it reads like a real poster) → poster.png ``` `problem_context`, `method_main`, and `result_evidence` are a useful **reading-order spine** to think about — what's the paper about, how does it work, wh
- How you run this skill
- Step 0: Environment Check
- Step 1: Parse the PDF
- Step 2: Poster intake — confirm layout-critical choices [INTERACT]
- Step 4: Write the outline [INTERACT]
- Step 5: Design the poster — YOU hand-author the HTML
- Step 6: Visual read — your own eyes, every render
- Step 7: Blind-reader content check — you orchestrate
- Step 8: Preview & iterate with the user [INTERACT]
- Step 9: Collect the deliverable next to the PDF
- Outline JSON Format
- Troubleshooting
conda run -n paper2anything --no-capture-output python ${SKILL_DIR}/scripts/check_env.py
pip install Pillow requests playwright
playwright install chromium
mkdir -p "$RUN_DIR"
conda run -n paper2anything --no-capture-output python ${SKILL_DIR}/scripts/parse_pdf.py "$pdf_path" \
conda run -n paper2anything --no-capture-output python ${SKILL_DIR}/scripts/auto_outline.py \
conda run -n paper2anything --no-capture-output python ${SKILL_DIR}/scripts/screenshot.py \
conda run -n paper2anything --no-capture-output python ${SKILL_DIR}/scripts/geom_check.py \
mkdir -p "$DEST"
cp "$RUN_DIR/poster.png" "$RUN_DIR/poster.html" "$DEST/"What does the paper2poster skill do?
Convert academic papers (PDF) into conference posters (HTML/PNG). You are the conductor: you decide what each section needs — an original paper figure or text — write the outline, hand-author the poster HTML, and iterate on the render using your own visual read and a blind-reader content quiz. Use when the user wants a poster from a paper PDF.
How do I install it?
Run `npx skills add QuZhan51496/paper2anything --skill paper2poster --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From QuZhan51496/paper2anything, a repository with 333 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.