# Paper2ppt

> Turn research papers into concise, editable PPT decks with a restrained discussion-class whiteboard style. Use when Codex needs to read a paper PDF or paper notes, optionally borrow Paper2Slides for content planning, and then create a simple editable PPTX for paper reading, discussion sessions, group meetings, or seminar reports.

- Skill: `aibot88/paper2ppt` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add aibot88/paper2ppt`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aibot88/paper2ppt/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: aibot88 (https://skillmd.com/u/aibot88)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aibot88/paper2ppt

---


# Paper2PPT

Create editable paper-reading decks in a restrained whiteboard style. This skill is for discussion slides, not marketing decks.

## Default Style

- White background.
- One large title near the top.
- Left side or top area uses grouped unordered bullets.
- Group headers are larger and usually red.
- Body bullets are smaller and black.
- Use figures and tables from the paper as evidence, not decoration.
- Remove meaningless cards or floating boxes unless the user explicitly asks for them.

## Core Workflow

1. Read the paper PDF or notes first.
2. Extract a small narrative arc instead of copying the paper section by section.
3. If useful, use Paper2Slides as an upstream planning/reference stage only.
4. Reorganize the content into the requested slide outline.
5. Build an editable `.pptx`, not screenshots.
6. Keep titles and bullets editable text; keep paper figures/tables as evidence images.

## Default Seven-Slide Arc

Use this when the user wants a standard paper-reading deck:

1. Research Problem + Challenges
2. Prior Work + Observation
3. Insight + Architecture Overview
4. Detailed Design I
5. Detailed Design II
6. Evaluation I
7. Evaluation II

## Layout Rules

- Keep each slide to 2-3 bullet groups.
- Prefer unordered bullets over paragraphs.
- Make group headers visibly larger than body text.
- Keep one main visual area per slide.
- Do not put meaningless summary cards in the middle-upper area.
- On evaluation slides, put the headline metric or conclusion in red.

## Paper2Slides Integration

When the user explicitly wants Paper2Slides or when it helps:

- Use Paper2Slides for paper parsing, summary extraction, or slide-plan inspiration.
- Do not rely on Paper2Slides image-only output as the final deliverable when the user wants editable PPT.
- Treat Paper2Slides as the planning/source-extraction stage, then rebuild the final deck as editable PPTX.

Read [references/workflow.md](references/workflow.md) for the full hybrid workflow and packaging notes.

## Bundled Source

This skill includes a full example project under `assets/example-boosting-resource-leak-7slides/`:

- `build/build_deck.mjs`: editable PPTX builder source
- `narrative_plan.md`: slide narrative
- `assets/`: paper figure/table screenshots
- `preview/`: rendered slide previews
- `verification/summary.json`: export summary
- `boosting-resource-leak-paper2slides-7slides.pptx`: final example deck

It also includes a vendored upstream copy of Paper2Slides under `vendor/Paper2Slides/`.

Use this example as a reference implementation when creating similar discussion-style decks.

## Publish / Repo Notes

If the user asks to package or publish this skill, include:

- `SKILL.md`
- `agents/openai.yaml`
- `references/`
- `scripts/`
- `assets/example-boosting-resource-leak-7slides/`
- `vendor/Paper2Slides/`
- `README.md`
- `LICENSE`

Read [references/publish-notes.md](references/publish-notes.md) before handing the folder off for GitHub publication.