Literature Report PPT Builder skill
Codex and Claude Code skill that turns a research paper into a literature report deck with real figures and an evidence check
- 122 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The skill reads papers and writes the deck and helper files in the working folder.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/literature-report-ppt-builderDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The skill reads papers and writes the deck and helper files in the working folder.
This is third-party code. Review the repository files before installing.
What it does
The skill builds a research paper report deck in Chinese. First `paper_analysis.json` is created and validated from the paper text and supplementary material: a logic tree (object, problem, strategy, method, conclusion, limitations), figure records (what is visible and what a figure cannot prove alone) and an evidence chain «question, figure, interpretation, page conclusion». Every data slide is tied to a real figure with source file, page and number. Then a delivery route is chosen. Route A builds each page as a verified image and packs it into PPTX, though objects inside are not editable. Route B inherits the master and navigation of a built-in template for editable pages. Route C creates editable slides from scratch in a red, black and gray palette. Scientific plots, spectra, micrographs, structures and mechanisms are never redrawn or distorted.
Who it is for. Graduate students and researchers preparing a paper talk for a group seminar who want to rely on verifiable figures from the original.
Good fit when
- A deck on a paper is needed in which each conclusion rests on a real figure.
- Before slides the logic of the paper must be laid out as a tree and evidence chains.
- An editable deck should reproduce the built-in template with navigation.
- A check report is needed: the validator flags gaps in the analysis.
Not a fit when
- You need a deck with no ties to scientific data.
- A deck in Russian or English is required: the skill targets Chinese.
- You want to redraw or improve plots from the paper.
Example request
Make a literature seminar deck from this paper and its SI, first build paper_analysis.json and check it with the validator.Limitations
The skill targets Chinese-language decks and natural science papers with figures. Route A requires a confirmed GPT-image-2 image backend, otherwise route B or C is chosen, and route A output is not editable by object. The validator `validate_paper_analysis.py` runs with `--fail-on-review` and stops work when gaps appear. The last commit dates from July 2026. Inserting figures needs source PDFs or files you are entitled to use. The license is MIT.
How to disable. Delete the `~/.codex/skills/academic-slide-pragmatic-fallback` or `~/.claude/skills/academic-slide-pragmatic-fallback` folder. Finished decks stay in the working folder.
FAQ
How do I install it for Codex?
Clone the repository and copy `skills/academic-slide-pragmatic-fallback` with `cp -R` into `~/.codex/skills/`. Restart the Codex session.
How do I install it for Claude Code?
Create `~/.claude/skills`, then copy the same `academic-slide-pragmatic-fallback` folder into it.
How do routes A, B and C differ?
A produces image pages, B inherits a template and C creates editable slides from scratch.
What does the validator check?
The `paper_analysis.json` file: each evidence page needs a source, page, figure number, observation and a boundary of the conclusion.
Does the skill alter scientific figures?
No. Paper figures, spectra and tables are used as they are and not redrawn or reinterpreted.
Discussion
No questions or reviews yet.
Related
SkillsA skill for talks: outlines a deck around the audience's train of thought, picks images and video, and checks finished slides before you present
A skill that turns an article, report or notes into a deck of full-slide images and assembles them into a pptx
Four skills for Codex and Claude Code build editable PPTX and Word reports, website demo videos and Xiaohongshu cards.
A skill that builds editable PowerPoint decks from outline.json with scripts and checks layout and density before delivery.
A skill that builds a deck from a topic or article, or restyles an old one from a reference image, keeping the text and editable slides
Skill turns the agent into a deck producer: brief, storyboard, slide posters, QA and a PDF or editable PPTX.
README in short
The project sets a sequence: paper analysis, page plan, route choice, production and acceptance. Documentation and slide text are in Chinese, with an English README.
README badge
Original SKILL.md
--- name: academic-slide-pragmatic-fallback description: Create Chinese academic literature-report PPTs from real paper/SI figures. Use for journal-club, thesis-defense, paper-to-PPT, and slide-review tasks, especially when Image2-style full-slide generation is unavailable. Preserve the strict Image2-only route when available; otherwise require explicit consent and choose a clean template-fidelity or a sample-style pragmatic fallback with real figures, source tracking, structural QA, and render QA. --- # Academic Slides with Safe Fallbacks Create academic decks that are evidence-led, readable, and honest about their production route. ## Non-negotiable rules - Use scientific visuals only from the paper, SI, or user-provided sources. Never fabricate, redraw, or semantically alter data figures, microscopy, spectra, molecular structures, mechanisms, tables, or charts. - Write conclusion-style titles, trace every visual in a figure-source manifest, and calibrate claims to evidence. - Do not call an editable or code-built deck Image2-only. ## Choose one route ### Route A: Image2-only authoritative deck Use only when a full-slide Image2 backend is confirmed and can faithfully preserve supplied scientific crops. Keep `image2_manifest.json`, package one approved full-slide image per PPTX slide, and run `scripts/validate_image_only_pptx.py`. ### Route B: template-fidelity fallback Use only after explicit user consent and a passed hygiene audit. The template owns its navigation, footer, and mapped slots; code edits inherited objects in place and must not add a second navigation layer. When the user explicitly asks to reproduce the bundled sample template exactly, use Route B's exact-template mode. Preserve the sample's navigation labels and decorative chrome intentionally, map each output page to a distinct source-slide archetype, and replace or remove every source-specific scientific object. Do not describe a code-redrawn Route C deck as an exact reproduction. Read `references/exact-template-fidelity.md` before building. ```text python scripts/build_fallback_template_pptx.py edit_plan.json exact.pptx --strict --fail-on-warnings python scripts/audit_fallback_template_pptx.py exact.pptx --build-report exact.build-report.json --check-masters --exact-template --fail-on-review python scripts/audit_exact_template_fidelity.py exact.pptx --plan edit_plan.json --build-report exact.build-report.json --fail-on-review ``` ```text python scripts/audit_fallback_template_pptx.py template.pptx --check-masters --fail-on-review ``` Reject templates containing old scientific content, figure labels, sample names, or non-removable master/layout objects. For adaptive cross-domain reuse, also reject fixed legacy navigation. The only exception is exact-template mode, where the user has explicitly requested that navigation and it remains semantically appropriate. Read `references/template-hygiene.md` and `references/fallback-template-pptx.md`. ### Route C: pragmatic fallback Use only after explicit user consent when Image2 is unavailable and no clean, domain-compatible template passes Route B. Start from a blank 16:9 presentation: code owns every visible object.