/present-paper

name: present-paper
description: Use when preparing an academic talk such as a journal club, grand rounds, seminar, conference presentation, or lecture/teaching deck. Analyzes the source, drafts audience-adapted speaker scripts, builds or augments the PPTX with speaker notes and prepares Q&A.
metadata:
  triggers: "present paper, paper presentation, journal club, seminar presentation, grand rounds, academic presentation, presentation prep, lecture, lecture material, teaching slides, course slides, 강의자료, 발표자료, 슬라이드, pptx"

Present-Paper Skill

Phase 0: Init & Outline

Step 0a — Load design references (read before drafting outline)

Read three files **now**, in full. Read the rest only **when the answer to Q0/Q2 tells you which one you need** — a talk has one venue and one style, and reading the others teaches nothing you will use.

**Read now (always):**

**A. `references/ai_slide_tells.md`** — the marks a generated deck leaves. Read all of it, first. Building against it is why the deck does not need catching later; `scripts/check_slide_tells.py` catches what slips through (Step 3.6). Where another reference conflicts with it, it wins. Eyebrow labels and brand footers on every slide are the single most-cited visual tell.

**B. `references/presentation_archetypes.md`** — the **skeleton**, chosen by where the speaker is standing: conference oral, journal-club critique, case-anchored grand rounds, didactic lecture, defence, keynote (Duarte's sparkline, the Jobs STAR moment, Takahashi/Lessig), lay talk, decision brief (Minto's pyramid, action titles, Kawasaki's 10/20/30). The *archetype* (what the talk has to **do**) and the *visual style* (what it **looks like**) are independent choices. **The skin is a preference; the skeleton is not.** Its mechanical half is `scripts/check_deck_budget.py`.

**C. `references/presentation_design_guidelines.md`** — the enforceable rules (assertion headlines, 24-pt floor, negative space, ≤3 colours, colourblind-safe palettes, redraw-don't-screenshot, animation discipline) plus the G1–G10 self-check the Phase 3.5 critic scores against.

**Read on demand — after Q0/Q2 tell you which one:**

| File | Read it when | |---|---| | `references/medical_presentation_templates.md` | the venue is one of the five medical ones — then read **that section only** | | `references/slide_visual_styles/CATALOG.md` → one style file | Q2 has chosen a style | | `references/slide_design_principles.md` | you are stuck on *why* a slide is not landing — the Reynolds / Duarte / Knaflic / Tufte theory under the rules in **C** | | `references/generated_illustrations.md` | you are about to generate any image for a slide, or a text-only slide keeps failing the critic; its first rule (never generate a medical image) is not optional | | `references/spoken_notes_and_bilingual.md` | you are drafting speaker notes, or the deck is not monolingual |

Required Inputs

Collect these before starting. Do not draft until the target audience is defined.

| Input | Why | |-------|-----| | **Paper** | PDF path, DOI, or PMID | | **Presentation time** | Determines depth and slide count | | **Target audience** | Specialty mix, knowledge level — controls terminology depth | | **Context** | Course name, conference, journal club format, prior session topics | | **Template / visual style** | Institutional template (.pptx/.potx) to fill, or a visual style to generate in. Default: ask (Step 0b) | | **Extension section** | Optional topic to include (e.g., AI directions, clinical implications). Default: none |

Step 0b — Template & visual style selection

Before drafting the outline, settle how the deck will look. Ask (use `AskUserQuestion`; skip a question the user already answered in their request):

**Q0 — "Where are you standing, and for how long?"** (venue + minutes)

This decides the **archetype** — the skeleton — before any question about looks. Map the answer with the selector table in `references/presentation_archetypes.md`, and carry `archetype` + `minutes` forward: Step 3.6 checks the built deck against them.

If the user gives only a topic and no venue, **ask**. Do not guess: a deck built for no particular room comes out generic in exactly the way every reviewer can see.

**Q1 — "Do you have an institutional or branded template to use?"**

• **Yes** → the user supplies a `.pptx`/`.potx`. Switch to **Mode C** (Phase 3, "Fill an

institutional template"). Do **not** also ask Q2 — the template's theme *is* the style.

• **No / none** → ask Q2.

**Q2 — "Which visual style should I generate in?"** Offer the `CATALOG.md` menu with a one-line preview each (recommended option first, labelled):

| Option | One-line preview | |--------|------------------| | **Nature / Lancet** *(recommended for medical academic talks)* | White, navy + coral accent, hairline dividers, Inter/Pretendard — restrained editorial-academic | | **Clinical Blue** | White/light-blue, navy-teal, calm and trustworthy, colorblind-safe — grand rounds / CME | | **Editorial Mono** | High-contrast black-on-white, oversized type, one accent — single big-message keynote | | **Dark Modern** | Deep-slate background, off-white text, electric accent — AI / method / tech talks | | **Other** | Describe a palette/feel, or name a journal/brand to emulate |

Record the choice and pass the matching style spec to Phase 3. With no preference and a medical academic talk, default to **Nature / Lancet**. Style changes only Phase 3 rendering — not the outline, script, or Q&A.

**Q3 — conference decks only: is slide 1 a submission requirement?** Many societies require the title slide to carry the title, authors, affiliations and country **exactly as entered in the abstract submission**. Do not shorten them to satisfy the density check — **the requirement wins**. Copy the fields from the submission portal, and record `SLIDE_TOO_DENSE` on slide 1 as consciously overruled with that reason.

Paper Analysis

Read the paper and produce a structure