Paper to ppt pipeline
Skill walterkken/popular-process-skills/paper-to-ppt-pipeline
Agent skills for popular work processes: GTD, OKR, PDSA, DMAIC, Design Thinking, Lean Startup, OODA, and research paper writing.
npx -y skills add walterkken/popular-process-skills --skill paper-to-ppt-pipelineAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Turn a research paper into a structured, styled PowerPoint deck: read a lawful paper/PDF, reconstruct the paper logic, create a top-level presentation outline, generate slide-level titles, map each slide to paper text/figures/tables/equations, create consistent slide images, and export a final PPT/PPTX. Use when Codex is asked to make a PPT from a paper, article, thesis chapter, technical report, or research PDF.
SKILL.md
3.0 KB, as published. Nobody here has run it
Paper to PPT Pipeline
Boundary
Use only papers and assets the user has lawful access to. Reusing original figures, tables, or long text may require citation, permission, or redrawing depending on the use case. For public/commercial decks, prefer original redraws or summarized diagrams with clear citations.
Do not fabricate results, citations, figures, tables, equations, or experimental claims. If the paper does not support a slide, mark the gap.
Workflow
- Intake the paper: confirm PDF/source file, target audience, language, slide count, presentation length, purpose, and reuse permissions.
- Read and reconstruct logic: use
references/paper-logic.mdto identify problem, gap, question, method, evidence, results, contribution, limitations, and implications. - Build the deck outline: create a top-level table of contents before writing slides.
- Generate slide titles: break each section into small slide titles that each make one clear point.
- Map paper content: use
references/content-mapping.mdto connect every slide to exact paper sections, claims, figures, tables, formulas, and citations. - Design slide storyboard: decide layout, visual hierarchy, figure/table treatment, and speaker logic for every slide.
- Create slide images: render each slide as a consistent full-slide image or visual preview using
references/visual-style.md. Keep typography, colors, margins, labels, and figure styles unified. - Assemble PPT/PPTX: use the rendered slide images and/or editable text/figures to create the final deck. Prefer editable PPT elements when the user needs later editing; prefer slide images when visual fidelity matters.
- Quality check: verify slide order, narrative continuity, citations, figure/table provenance, text fit, contrast, image resolution, and missing evidence.
- Deliver artifacts: output the
.pptx, slide image folder, content map, source/citation map, and unresolved issues.
马斯克 Supervision
Delete weak slides before designing them. Do not turn every paper section into a slide. Keep only slides that move the argument forward. Simplify the story before polishing the visual style.
Output
- paper logic map
- deck table of contents
- slide-by-slide title list
- slide content map
- figure/table/equation inventory
- style specification
- rendered slide images
- final PPT/PPTX
- citation/provenance report
- quality-check report
Resources
references/paper-logic.mdreferences/content-mapping.mdreferences/visual-style.md