mrkeyoor.com_
Sat 26 Sept 18:47 UTC
AI Toolsevaluationupdated 25 Aug 2026

ppt-master review

PPT Master is a local skill and Python toolset that lets an AI coding agent turn documents, web pages, or a brief into an editable PowerPoint deck. It plans the argument, authors slide visuals as SVG, converts them into native PowerPoint objects, and can also fill existing templates or add charts, notes, transitions, animation, and narration.

+824stars / 7d
Verdict

PPT Master is one of the more serious open workflows for generating a deck that remains genuinely editable in PowerPoint. Its value comes from story planning, explicit design choices, and native object export, not from eliminating human review. Use it when the output will receive a real editorial pass; choose a code library or Markdown deck system when repeatability matters more than an agent's design judgment.

We ran it

Lab card: what happened when we ran ppt-masterScreenshot of ppt-master (hugohe3.github.io/ppt-master-examples)
Install✓ · 46s108 packages · 301 MB
Build✓ · 6s
Testsn/ano test script
Known vulns0(pip-audit)
Repo14250 files~165,217 lines of source · 721.1 MB · 1 CI workflows

Answers from our run

Does ppt-master build from source?

Dependencies installed in 46 seconds (108 packages), and the build succeeded in 6 seconds. We cloned commit 613e0d1 into a clean Debian container with 3 CPUs and no project-specific setup.

Does ppt-master have tests you can run?

Not through a standard command: the project exposes no test script or target that our harness could run.

Does ppt-master have known vulnerabilities in its dependencies?

pip-audit found none in the dependency tree at the time of our run.

Who should not use ppt-master?

People expecting a one-click perfect deck: the README says final polishing remains the user's job and quality depends heavily on the chosen model.

What are the alternatives to ppt-master?

PptxGenJS, python-pptx, Marp. PPT Master is one of the more serious open workflows for generating a deck that remains genuinely editable in PowerPoint.

Setup3/5Python setup is easy; agent, model, assets, and review add effort
Docs5/5Detailed workflow, platform, template, export, and troubleshooting guides
Community4/5Fresh releases and responsive discussions around a small issue queue
Maturity3/5Capable export system without a measured automated test target

Who it’s for

PowerPoint users who want AI-generated decks they can continue editing object by object.
Analysts and consultants willing to review the story, design specification, sources, and final slides.
Claude Code, Codex, Cursor, Kimi, or other agent users comfortable granting local file and command access.
Teams that want to adapt a repeatable presentation workflow to their own templates and source materials.

Who it’s NOT for

People expecting a one-click perfect deck: the README says final polishing remains the user's job and quality depends heavily on the chosen model.
Budget-sensitive users who cannot control long agent runs or image generation: an open issue reports the best result in one personal comparison also cost the most.
Teams requiring an upstream automated test target: our measured checkout had no test script, target, or tests directory.
Users who need exact formula behavior in Keynote, WPS, or LibreOffice: the documented editable formula contract covers PowerPoint 2010 and later only.
Existing clone owners who cannot realign after rewritten history: v5.0.0 says old and new histories share no ancestor.

Setup reality

Our clean Python 3.12 sandbox installed 108 packages in 46 seconds and used 301 MB. The build succeeded in 6 seconds. There was no test script or target, so tests were skipped; pip-audit found no known vulnerabilities. The measured commit occupied 721.1 MB with 14,250 files and about 165,217 lines of source.

The basic path needs Python 3.10 or newer plus an agent that can read, write, and run commands. Deck quality and cost depend on that agent's model. AI images need a host image tool or provider key; stock search works without keys through Openverse and Wikimedia, with optional Pexels or Pixabay keys. Legacy document formats need Pandoc.

PowerPoint itself is required to verify native behavior that other office suites do not promise. Quick mode trades resumability and design confirmation for speed. The v5.0.0 release moved examples to another repository and rewrote Git history, so existing clones and forks need deliberate migration rather than a normal pull.

Editable PowerPoint is the point

Many AI slide tools produce screenshots with text on top or fill a rigid template. PPT Master aims deeper into the PowerPoint file format. It draws each slide as SVG, then converts that work into editable DrawingML shapes. Text, pictures, fills, effects, connectors, charts, and tables can remain objects a user can select and change. A structured template route can preserve slide masters and layouts from an existing deck.

That choice solves a practical problem. Generated decks are rarely finished. A claim needs correction, a chart needs a new figure, legal wants a footnote, or the chief executive dislikes the cover. Editable objects make those changes possible without sending every revision back through a model. PPT Master explicitly tells users to expect polishing, which is more honest than promising a final presentation from one prompt.

The tradeoff is complexity. Native PowerPoint has many object types and application-specific behaviors. The project deliberately omits SmartArt, and formulas are promised as editable OMML in PowerPoint 2010 or later, not in Keynote, WPS, or LibreOffice. Native charts and tables can render differently across applications. Visual consistency and native data editing sometimes pull in opposite directions, so the exporter offers separate choices.

The agent owns the editorial workflow

PPT Master is installed as a skill for Claude Code, Codex, Cursor, Kimi, and other agents that can work with files and shell commands. A normal run reads source material, confirms a design specification, plans the story, obtains visuals, authors slides, checks them, and exports a PPTX. Files on disk preserve the plan and intermediate SVG previews.

This is a better interaction than asking a general chatbot for ten slide titles, but the model remains the ceiling. The README recommends a large-context model and strong image generation for its best examples. A cheaper model may ignore visual rules, choose weak evidence, or require more correction. Issue 249 reports that a newer workflow produced plainer output than an older version for one user, with the agent itself identifying missing enforcement between specifications and execution.

Quick mode removes the confirmation round trip and several durable planning artifacts. It still converts sources, researches gaps, creates assets, exports, and runs a final check, but it cannot resume after losing context and does not create the normal preview stage. That mode fits a throwaway first draft. A client presentation or board deck deserves the regular path, where story and design decisions can be challenged before rendering.

What happened when we ran it

We cloned commit 613e0d1 into a clean, unprivileged Python 3.12 Bookworm container with three CPUs, 8 GB of RAM, and no secrets. The checkout was unusually large at 721.1 MB, with 14,250 files and about 165,217 lines of source. Installation succeeded in 46 seconds, adding 108 packages and using 301 MB. The build completed successfully in 6 seconds. Pip-audit found no known vulnerabilities.

There was no test script or target, and the checkout had no tests directory, so our harness skipped testing. It did contain one CI workflow file. A successful package build proves the Python code can be packaged in that environment; it does not verify SVG conversion, PowerPoint rendering, charts, templates, animations, or an end-to-end agent run. Those paths require sample decks and application-level inspection.

The size result belongs to the measured commit. Release v5.0.0, published on August 24, 2026, says the project moved its examples into a separate repository and rewrote all Git history to reduce clone size. Existing clones and forks cannot fast-forward normally because the histories have no shared ancestor. New users should start from the current repository, while anyone with local changes should preserve them before migration.

Sources and images require editorial judgment

Input can be a PDF, DOCX, web page, existing PPTX, or pasted text. Modern formats are handled through Python, while older document types need Pandoc. When factual gaps remain, the agent can research them. That is useful only if the reviewer checks whether citations support the slide's claim and whether the visual treatment preserves context. A polished chart can still encode a weak comparison.

Images can come from the user's files, the agent host's native generator, configured image APIs, or web search. Zero-key search uses Openverse and Wikimedia Commons. Pexels and Pixabay keys expand stock results. The workflow can add small credits for licenses that require attribution, but the operator still owns brand rights, subject consent, and any restrictions attached to generated media.

An existing corporate deck can serve as a template to fill with new text, charts, and tables. This route is valuable for teams whose brand system already lives in PowerPoint. Test slides with unusual fonts, master inheritance, grouped objects, and animations before using it at scale; preservation promises are only meaningful against the actual templates your organization uses.

Health is strong, validation is still your job

The repository was pushed on August 25, 2026, one day after v5.0.0. GitHub listed seven open issues and pull requests, and recent threads received maintainer replies. Documentation is extensive: separate guides cover getting started, Windows setup, templates, project positioning, technical design, source conversion, image acquisition, and PowerPoint-to-SVG mapping. An English README appears first, with a Chinese translation linked beside it.

The missing test target remains the largest engineering reservation. Presentation software is vulnerable to visual regressions that unit tests alone would not catch, but repeatable fixtures and export checks still matter. Until those are part of the upstream path we measured, keep a reference set of documents and templates, open every generated file in the target PowerPoint version, and inspect text overflow, missing assets, chart data, notes, and animation behavior.

PPT Master is best for users who want an agent to do the first heavy editorial and layout pass while retaining the right to fix every object afterward. It saves labor, not judgment. For fixed weekly reporting, direct PptxGenJS or python-pptx code may be easier to test and reproduce.

Alternatives

ProjectWhat it isPick it when
PptxGenJSA JavaScript library for generating editable PowerPoint files directly from code.pick this instead when developers want deterministic slide generation and will design the content workflow themselves.
python-pptxA Python library for creating and modifying PowerPoint files through a programmatic object model.pick this instead when you need precise automation in Python without an agent deciding the story or design.
MarpA Markdown-based presentation ecosystem for reproducible, developer-friendly slide decks.pick this instead when text-first authoring and version control matter more than native PowerPoint object depth.

What people are saying

  1. [github-trending] hugohe3/ppt-master

Sources

  1. PPT Master README
  2. PPT Master repository facts
  3. PPT Master v5.0.0 release
  4. Version output-quality report
  5. Cost comparison discussion
  6. PPT Master examples

More ai tools reviews

gallery · undress-service · khazix-skills · nobodywho · desktop-cc-gui · langextract · the whole board →