AI for PPT is no longer just “enter a title and apply a template.” In AI coding environments such as Claude Code, Codex, and Cursor, PPT generation is becoming a set of installable, reusable Agent Skills: some output web presentations, some generate truly editable .pptx files, some use image models to turn each slide into a visual draft, and some let AI operate PowerPoint files through MCP.
This article looks at a group of mainstream PPT-related Skills. The useful part is not only the list itself, but the way these tools can be separated by delivery format. Before choosing a tool, ask one question first: who will edit the final deliverable, where will it be presented, and does it need ongoing collaboration?
Several Routes
1. HTML Web Presentations
Representative projects include frontend-slides, guizang-ppt-skill, and html-ppt-skill.
The strength of this route is visual expressiveness. CSS animations, Canvas, WebGL, and responsive layouts are all available. The result can be opened directly in a browser, making it suitable for technical talks, product launches, Demo Day presentations, and talks with a strong personal style.
The trade-off is also clear: after delivery, it is not ideal for clients who need to edit text line by line. If the client receives HTML instead of a PowerPoint file, later changes often need to go back through the generation workflow.
If you only care about HTML presentations, frontend-slides feels like a high-star general entry point, guizang-ppt-skill is stronger in aesthetic constraints and themed style, and html-ppt-skill stands out for its number of themes, layout options, and presenter mode.
2. Native PPTX
Representative projects include mckinsey-pptx, ppt-agent-skills, claude-office-skills, and ppt-master.
This is the most stable route for business delivery. As long as the client asks to “edit text, change images, and apply a company template in PowerPoint,” the final output needs to land in .pptx.
ppt-master is especially worth a separate look. Its idea is to have the LLM generate SVG first, then convert it into native PowerPoint DrawingML objects. The goal is to keep text boxes, shapes, and charts editable inside PPTX. It also supports generating PPTX from PDF, DOCX, URL, and Markdown, as well as template replication, animation, narration, and local preview.
This route works well for consulting deliverables, company reports, white paper presentations, and turning long reports into PPT decks. The downside is that the visual ceiling is usually limited by PowerPoint itself, so complex effects are not as free as HTML or image-based routes.
3. AI Image-Driven Workflows
Representative projects include NanoBanana-PPT-Skills, gpt_image_2_skill, and ppt-image-first.
This route treats each slide as a visual image first, then places the images into PPTX or another container. Its advantage is a high level of visual completion, especially for covers, social media graphics, visual proposals, and communication-oriented content.
The problem is poor editability. A page is essentially an image. If you later need to change a title, replace a paragraph, or move an icon, you may need to regenerate it. It is good for “it needs to look good,” but not for “the client will revise it repeatedly.”
4. MCP / Protocol Layer
Representative projects include Office-PowerPoint-MCP-Server and PPTAgent.
These tools do not necessarily generate a complete PPT directly. Instead, they give AI an interface for operating PowerPoint. After connecting through MCP, the model can read, modify, and write .pptx files.
This route fits workflows where a PPT file already exists and AI is needed to help revise it. Examples include batch format changes, rearranging pages based on feedback, or asking the model to check whether each slide matches the goal. PPTAgent emphasizes reflective generation, meaning it checks back after generating each slide. That direction is useful for reducing the “AI PPT feels rough” problem.
5. Integrated Design Platforms
Representative projects include open-design and docsagent.
These projects go beyond PPT generation itself. open-design is more like a local-first design platform that can generate prototypes, slides, images, and videos, with support for multiple export formats. docsagent is not a PPT tool, but it can index and chat with local documents, making it useful as a material organization layer before generating PPT.
If your need is not a one-off PPT, but a fuller workflow from materials, design, and prototypes to delivery, this type of platform is more worth watching.
Skill Metadata
Star counts come from the original crawl result on 2026-05-15. They are only useful as a popularity reference. Before actual use, open the repositories again to confirm maintenance status, README, and LICENSE.
| Skill | Author | Links | Star | Language | Route |
|---|---|---|---|---|---|
| frontend-slides | @zarazhangrui | https://github.com/zarazhangrui/frontend-slides | 17,530 | Shell | HTML web presentation |
| guizang-ppt-skill | @op7418 (Guizang) | Site article GitHub |
8,832 | HTML | HTML web presentation |
| html-ppt-skill | @lewislulu | https://github.com/lewislulu/html-ppt-skill | 3,834 | HTML/CSS/JS | HTML web presentation |
| mckinsey-pptx | @seulee26 | https://github.com/seulee26/mckinsey-pptx | 426 | Python | Native PPTX |
| ppt-agent-skills | @sunbigfly | https://github.com/sunbigfly/ppt-agent-skills | 714 | Python | Native PPTX |
| claude-office-skills | @tfriedel | https://github.com/tfriedel/claude-office-skills | 631 | Python | Native PPTX |
| ppt-master | @hugohe3 | https://github.com/hugohe3/ppt-master | 16,626 | Python | Native PPTX |
| NanoBanana-PPT-Skills | @op7418 (Guizang) | https://github.com/op7418/NanoBanana-PPT-Skills | 2,668 | Python | AI image-driven |
| gpt_image_2_skill | @wuyoscar | https://github.com/wuyoscar/gpt_image_2_skill | 2,102 | Python | AI image-driven |
| ppt-image-first | @NyxTides | https://github.com/NyxTides/ppt-image-first | 799 | Python | AI image-driven |
| Office-PowerPoint-MCP-Server | @GongRzhe | https://github.com/GongRzhe/Office-PowerPoint-MCP-Server | 1,708 | Python | MCP / protocol layer |
| PPTAgent | @icip-cas | https://github.com/icip-cas/PPTAgent | 4,354 | Python | MCP / protocol layer |
| open-design | @nexu-io | Site article GitHub |
40,822 | TypeScript | Integrated design platform |
| docsagent | @docsagent | https://github.com/docsagent/docsagent | 687 | TypeScript | Integrated design platform |
How to Choose
If the client needs to continue editing, prioritize the native PPTX route, especially ppt-master, mckinsey-pptx, and ppt-agent-skills.
If you are presenting yourself and visual expression matters more than later editing, prioritize the HTML route, especially frontend-slides, guizang-ppt-skill, and html-ppt-skill.
If the goal is a poster-like, cover-like, or shareable visual, prioritize the image route, such as ppt-image-first, gpt_image_2_skill, and NanoBanana-PPT-Skills.
If you already have a PPT file and only want AI to help read, edit, and rearrange it, look at the MCP route.
For explicit scenarios such as academic talks, marketing, translation, or compressing long reports into slides, you can also look for vertical Skills instead of forcing a general-purpose PPT generator to do everything.
Final Notes
Open source projects should not be judged by Star count alone. Before actual use, confirm three things:
- Whether the LICENSE allows your use case.
- Whether the generated output meets delivery requirements, especially editability.
- Whether the cost is acceptable, including model calls, image generation, large-context models, and possible cloud service fees.
These tools change quickly. Star counts will change, and project maintenance status will change too. But the selection logic is relatively stable: decide the delivery format first, then look at specific tools. Whether a PPT is for speaking, editing, or viewing often narrows the choices by more than half.