PPT on KnightLi Blog

A Survey of Mainstream AI PPT Tools: How to Choose Between Auto Generation, Web Slides, PPTX, and Image-Based Workflows

Mon, 18 May 2026 22:29:43 +0800

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	GitHub: zarazhangrui/frontend-slides	17,530	Shell	HTML web presentation
guizang-ppt-skill	@op7418 (Guizang)	Site article: guizang-ppt-skill GitHub: op7418/guizang-ppt-skill	8,832	HTML	HTML web presentation
html-ppt-skill	@lewislulu	GitHub: lewislulu/html-ppt-skill	3,834	HTML/CSS/JS	HTML web presentation
mckinsey-pptx	@seulee26	GitHub: seulee26/mckinsey-pptx	426	Python	Native PPTX
ppt-agent-skills	@sunbigfly	GitHub: sunbigfly/ppt-agent-skills	714	Python	Native PPTX
claude-office-skills	@tfriedel	GitHub: tfriedel/claude-office-skills	631	Python	Native PPTX
ppt-master	@hugohe3	GitHub: hugohe3/ppt-master	16,626	Python	Native PPTX
NanoBanana-PPT-Skills	@op7418 (Guizang)	GitHub: op7418/NanoBanana-PPT-Skills	2,668	Python	AI image-driven
gpt_image_2_skill	@wuyoscar	GitHub: wuyoscar/gpt_image_2_skill	2,102	Python	AI image-driven
ppt-image-first	@NyxTides	GitHub: NyxTides/ppt-image-first	799	Python	AI image-driven
Office-PowerPoint-MCP-Server	@GongRzhe	GitHub: GongRzhe/Office-PowerPoint-MCP-Server	1,708	Python	MCP / protocol layer
PPTAgent	@icip-cas	GitHub: icip-cas/PPTAgent	4,354	Python	MCP / protocol layer
open-design	@nexu-io	Site article: open-design GitHub: nexu-io/open-design	40,822	TypeScript	Integrated design platform
docsagent	@docsagent	GitHub: 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.

From PPT to Prototypes: Use Cases for Guizang PPT Skill and Huashu Design

Sat, 09 May 2026 08:34:23 +0800

Two design-oriented Agent Skills made by Chinese developers are worth looking at side by side: guizang-ppt-skill by Guizang, and huashu-design by Huashu.

They are not “design tools” in the traditional sense. Instead, they turn a design process, aesthetic preferences, checklists, and engineering templates into Skills that an Agent can execute. You are not opening a UI and slowly dragging elements around. You hand the requirement to an Agent such as Claude Code, Codex, or Cursor, and let it generate HTML, PPT, animation, or prototypes through a fixed workflow.

The value of these projects is not that they let AI improvise. It is that they turn “how to make this not look bad” into a repeatable process.

guizang-ppt-skill: focused on magazine-style web PPT

Guizang’s guizang-ppt-skill has a clear positioning: it generates single-file HTML, horizontally paged PPTs with a visual baseline of “digital magazine x e-ink.” It feels more like a layout system prepared for talks than a general-purpose design framework.

The repository README lists these core capabilities:

Single-file HTML output, with no build step or server required. Open it directly in a browser.
Horizontal page navigation, with support for keyboard, mouse wheel, touch swipes, bottom dots, and an ESC index.
5 preset theme palettes, including Ink Classic, Indigo Porcelain, Forest Ink, Kraft Paper, and Dune.
10 page layouts, including opening cover, section divider, big-number data poster, text-left-image-right, image grid, Pipeline, suspense question, large quote, Before/After comparison, and mixed text-image layout.
Built-in templates, component notes, layout skeletons, theme configuration, and quality checklists.

It is suitable for offline sharing, internal industry talks, private salons, AI product launches, demo days, and presentation decks with a strong personal style. It is less suited to large tables, training courseware, or multi-person collaborative editing.

This project makes a good tradeoff: it does not try to cover every design scenario, but narrows itself to “magazine-style PPT.” Theme colors are chosen from presets, and layouts have clear skeletons. That actually reduces the chance of the Agent drifting off course.

If you often need to turn opinions, industry observations, or product launch content into a presentation deck, it can be highly practical.

The install command is straightforward:

`1`	`npx skills add https://github.com/op7418/guizang-ppt-skill --skill guizang-ppt-skill`

huashu-design: a fuller HTML-native design workflow

Huashu’s huashu-design has broader coverage. Its goal is not just to make PPTs, but to treat HTML as a native design canvas and let an Agent produce deliverable design assets.

The repository README lists these capabilities:

Clickable App or Web prototypes.
HTML slides, plus editable PPTX export.
Product launch animations, MP4, GIF, and versions with music.
Multiple design directions shown side by side for comparison.
Infographics, data visualizations, and PDF, PNG, SVG export.
5-dimensional expert review, covering philosophical consistency, visual hierarchy, execution craft, functionality, and innovation.

Its core idea is to let the Agent understand the brand and assets first, then produce high-fidelity design. The project emphasizes a Core Asset Protocol: when dealing with a specific brand, first confirm the logo, product images, UI screenshots, color palette, fonts, and brand guidelines instead of guessing from memory.

This matters. Many AI-generated designs look “like design,” but they do not look like a real product or brand. huashu-design tries to solve that problem up front: find real assets first, then design.

The install command is:

`1`	`npx skills add alchaincyf/huashu-design`

It is better suited to people who want to complete a fuller design delivery from the terminal: product prototypes, launch animations, presentations, infographics, and design reviews can all be handled inside one Agent workflow.

The biggest difference between the two

In simple terms, guizang-ppt-skill is a narrower and steadier presentation deck generator; huashu-design is a broader and more complete HTML-native design system.

If you only look at PPT:

guizang-ppt-skill emphasizes magazine feel, rhythm, layout, and single-file browser presentations.
huashu-design emphasizes general design capability, editable PPTX, brand assets, export paths, and review workflows.

If you look at overall design capability:

guizang-ppt-skill has clearer boundaries and is suitable for quickly making a stylish horizontal presentation.
huashu-design is more comprehensive and is suitable for breaking a product or brand design task into prototypes, animations, slides, and infographics.

These two projects also represent two different ways to write Skills. The former is like a highly constrained set of templates and aesthetic rules. The latter is like a workflow manual for a small design team.

Why this kind of Skill matters

A common problem with Agents is that they “can do it, but not consistently.” The same request may produce a strong result once, then drift into purple gradients, rounded cards, fake icons, and a pile of fancy-sounding empty copy the next time.

Skills are a way to add stability. They lock down things such as:

Reusable templates.
Executable checklists.
Clear aesthetic preferences.
Rules for avoiding common mistakes.
Output formats and validation flows.
When to ask questions and when to start directly.

This is far more reliable than simply writing “please make it look more premium.”

This is especially true for design tasks. Aesthetics cannot be reproduced reliably by a single prompt. What really helps is process: confirm assets first, decide the direction, build the structure, work on the visuals, then inspect the output. When this process is written as a Skill, the Agent becomes more like a collaborative executor rather than a one-shot image generator.

Usage recommendations

If you just want to turn a topic into an offline talk or sharing deck, try guizang-ppt-skill first. Its output boundary is narrow, and single-file HTML is also easy to distribute and preview.

If you want an Agent to take on a more complete design task, such as App prototypes, launch animations, branded slides, exportable PPTX, or infographics, look at huashu-design first. Its workflow is longer and better suited to tasks that need multiple rounds of iteration and exported deliverables.

If you are already writing your own Codex or Claude Code Skill, both projects are worth studying:

To learn “how to make a narrow scenario stable,” look at guizang-ppt-skill.
To learn “how to break a complex workflow into executable protocols,” look at huashu-design.

Summary

What Guizang and Huashu have in common is that both turn “design capability” from a one-time prompt into a repeatable process.

guizang-ppt-skill focuses on magazine-style HTML PPT and works well for highly stylized presentations. huashu-design focuses on an HTML-native design system covering prototypes, animations, slides, infographics, and reviews. The problem they solve is not “can AI generate design,” but “can AI generate deliverable design through a stable method.”

This may become an important type of open-source project in the Agent tooling ecosystem: not just code templates, but packaged human experience, aesthetics, and working methods as Skills.

Reference links: