Install any skill in seconds. Free to start, no credit card required.
Get Started Free →quzhan51496/paper2slides
Turn an academic paper PDF into a presentation deck (.pptx) end-to-end.
Passed 16 of 19 test cases with the skill, and 4 of 19 without it.
and 18 more in the full report
15 fixed4 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
I uploaded `quantum_computing.pdf`. Can you read through this paper and write a 3-paragraph summary of its key findings for my research notes? I do not want slides made.
| Checked | Without skill | With skill |
|---|---|---|
| Informs the user that paper2slides is designed for presentation deck generation. | Missed | Passed |
| Asks whether to proceed with slide deck generation before running the pipeline. | Missed | Passed |
The instructions your model reads when the skill loads.
Turn an academic paper PDF into a presentation-ready .pptx. This is a conductor skill: you make the
editorial and design judgments, while the mechanical steps are handled by this skill's own self-contained
scripts — PDF parsing via the MinerU cloud API (scripts/parse_pdf.py) and .pptx rendering via a PptxGenJS
bridge (scripts/render_pptx.py). It orchestrates a "paper → outline → spec → render → QA" pipeline and
depends on no other skill.
| Stage | Input | Output | Owner |
|---|---|---|---|
| 0.5. configure | user dialogue | <workdir>/config.json | you (AskUserQuestion to confirm three items: length tier + whether to run visual QA + color scheme) |
| 1. extract | paper.pdf | paper_meta.json + figures_index.json + figures/ + pages/ + equations + hi-res figure/table crops (produced in one shot by the MinerU cloud API) | scripts/parse_pdf.py |
| 2. outline | paper_meta.json | slide_outline.json | you (per references/outline-heuristics.md) |
| 3. spec | slide_outline.json + figures | slide_spec.json | you (per references/design-style.md) |
| 4. render | slide_spec.json | output.pptx | scripts/render_pptx.py (PptxGenJS bridge) |
| 5. qa | output.pptx | pass / fail + fix list | content QA always runs; visual QA is gated by Stage 0.5's config.json/visual_qa |
See references/pipeline.md for the detailed per-stage protocol.
Invocation form:
/paper2slides <paper.pdf> [output.pptx] [--from-stage <name>] [--force]
output.pptx omitted → <paper-dir>/<paper-stem>_slides/<paper-stem>.pptx; on a name collision the directory auto-appends _v2 _v3<paper-dir>/.paper2anything/slides/<paper-stem>/; when the paper directory is read-only, fall back to ~/.cache/paper2anything/slides/Python environment: all scripts run in the paper2anything conda environment. Command prefix
conda run -n paper2anything --no-capture-output python -m scripts.<name> ...
(the prefix can be omitted once conda activate paper2anything is in effect). Every -m scripts.<name> must be run from this
skill's directory (the parent of scripts/), otherwise you get No module named 'scripts'; the prefix-omission convention is in
references/pipeline.md §General Conventions.
The first step is always to resolve the workspace:
test cases passed, vs 4 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.