Guizang PPT Skill Review 2026: AI Decks, Tested

What Guizang PPT Skill Is

Guizang PPT Skill is a skill file, not an app. You drop a folder into your agent's skill directory, and from then on the agent can generate HTML slide decks on request. The repository at github.com/op7418/guizang-ppt-skill shows 27,727 stars, which puts it in rare company for a single-purpose skill file. The docs describe it as an agent skill that produces polished HTML slide decks with editorial magazine and Swiss layouts.

The distinction matters. Gamma, Tome, and most of the deck-builder category are hosted products. You sign in, you type a prompt, the service renders slides on its servers, and you export. Guizang PPT Skill inverts that. There is no server. There is no account. The skill is a set of instructions and template assets that your local agent reads and executes. The output is HTML files sitting in your project folder, and you own them outright.

What ships in the folder

Based on the repository structure, the skill folder contains a SKILL.md file that defines the agent's behavior, a templates directory with layout definitions, and theme assets covering typography, color, and spacing. The SKILL.md is the load-bearing piece. It tells the agent which layouts exist, when to pick each one, how to handle text density, and what the output HTML should look like. The templates are the raw material the agent assembles into a deck.

This is a thin architecture by design. There is no rendering engine, no layout solver, no font subsetting pipeline. The agent does the layout reasoning, and the skill file constrains that reasoning toward a specific visual language. Editorial magazine layouts lean on large display type, asymmetric columns, and generous whitespace. Swiss layouts lean on grid discipline, sans-serif type, and restrained color. Both are achievable in plain HTML and CSS, which is why the skill can get away with shipping no runtime.

Which hosts support it

Skill support is the gating factor. The skill format originated with Claude Code and has since been adopted by other agent hosts that read the same directory convention. Codex and similar CLI agents that support skill files can load it. Hosted chat interfaces generally cannot, because they do not have filesystem access to a skill directory. If your agent cannot read a local folder of instructions, this skill does nothing for you.

The practical implication: Guizang PPT Skill is for people already running a coding agent locally. If you are paying for Claude Code or an equivalent, the marginal cost of this skill is zero. That is the core pitch, and it holds up. You are not buying another subscription. You are extending a tool you already have.

Install and first deck: step by step

The install path is a git clone into the skills directory. The exact location depends on your host, but the convention is a skills folder inside your agent's config directory. For Claude Code, that is typically ~/.claude/skills/. The repository README documents the exact path for supported hosts.

cd ~/.claude/skills
git clone https://github.com/op7418/guizang-ppt-skill.git

After cloning, the folder layout looks like this:

guizang-ppt-skill/
  SKILL.md
  templates/
  themes/
  assets/

No build step. No dependency install. No config file to edit. The agent discovers the skill on next launch and can invoke it when a prompt matches.

The prompt that produces a deck

A working prompt names the skill, states the topic, specifies slide count, and picks a theme. Something like: Use the guizang-ppt-skill to build a 10-slide deck on quarterly infrastructure costs. Use the Swiss theme. Output to ./deck/.

The agent reads SKILL.md, selects layouts from the templates folder, writes HTML files into the output directory, and links them with a simple index. From there you open the HTML in a browser. There is no preview pane inside the agent. You see the result when you open the file.

That last point is the biggest workflow difference from app-based builders. Gamma shows you the deck as it generates. Guizang PPT Skill writes files and stops. If a slide overflows, you find out in the browser, then go back and ask the agent to fix it. The loop is slower per iteration but the artifact is cleaner.

Folder layout after generation

Output is plain HTML plus a CSS file and whatever assets the theme references. You can open index.html directly, or serve the folder with any static server. Because it is static HTML, you can also drop it into a repo, commit it, and diff changes across revisions. That is a real advantage over binary PPTX files, which do not diff usefully.

Output quality: layout, fonts, overflow

Quality here means three things: does the layout hold, do the fonts render, and does the text fit. The skill's design targets are editorial magazine and Swiss, both of which are forgiving of sparse content and punishing of dense content. A deck with three bullets per slide looks great. A deck with three paragraphs per slide will fight the layout.

Layout

The templates encode real layout decisions rather than generic slide grids. Editorial layouts use display type at large sizes, often with a single dominant element per slide. Swiss layouts use a strict grid with consistent margins and a restrained palette. The agent picks between them based on the theme you specify and the content density it infers. When the content does not fit the chosen layout, the agent's default behavior is to split across slides, which is usually the right call but occasionally produces awkward breaks.

Fonts and CJK fallback

This is the sharpest edge. The skill's themes assume a font stack, and if the target machine lacks those fonts, the browser falls back. For Latin text, fallback is usually tolerable. For CJK text, fallback is frequently ugly, because the system default CJK font may have different metrics, different weight rendering, and different line height than the theme expects. The docs do not ship webfonts by default, so CJK decks depend on what is installed locally. If you are producing Chinese, Japanese, or Korean decks, verify the font stack on the machine that will present the deck, not just the machine that generated it.

Overflow

Text overflow is the most common defect. HTML does not auto-shrink text to fit a box the way PowerPoint does. If the agent writes more text than the layout accommodates, the text either clips or pushes the layout apart. The skill mitigates this by instructing the agent to keep slides sparse, but it cannot guarantee fit. Expect to iterate on dense slides. The fix is usually to ask the agent to split the slide or trim the copy, not to hand-edit CSS.

Charts

Chart rendering depends on what the agent chooses to emit. Plain HTML and CSS can produce bar and line charts, and inline SVG works well for simple data. Complex charts generally require a library, and the skill does not bundle one by default. If your deck needs real charts, plan to either keep them simple or add a charting library to the output yourself. This is a gap relative to hosted builders that render charts natively.

Guizang PPT Skill vs PPT Master vs Gamma

The comparison that matters is not feature count. It is where the artifact lives and what you can do with it afterward.

Dimension	Guizang PPT Skill	PPT Master	Gamma
Input format	Prompt inside your agent	Prompt in a hosted tool	Prompt in a hosted tool
Editability	Full HTML/CSS source	Tool-dependent	In-app editor
Export	HTML (native), PDF via browser print	Varies by tier	PPTX, PDF, HTML
Offline	Yes, fully local	No	No
Price	$0/mo for the skill itself	See vendor pricing page	See vendor pricing page

The offline column is the one that decides most cases. Guizang PPT Skill runs entirely on your machine. Nothing leaves your laptop. For decks containing internal financials, unreleased product plans, or anything under NDA, that is not a nice-to-have. It is the reason to pick this over a hosted builder.

The export column is the tradeoff. Gamma exports PPTX, which matters if your organization lives in PowerPoint and expects an editable .pptx file. Guizang PPT Skill produces HTML. You can print to PDF from a browser, and the result is clean, but there is no native PPTX path. If your stakeholders need to open the deck in PowerPoint and move boxes around, this skill is the wrong tool.

PPT Master sits in the middle. It is a hosted tool with its own workflow, and the specifics of its export and pricing live on its own page rather than in this review. The honest framing: if you want a hosted tool with a familiar editor, compare PPT Master and Gamma directly. If you want a local skill that extends an agent you already pay for, Guizang PPT Skill is the only one of the three that fits.

Pricing and limits

The skill itself is free. The repository is public and the pricing starts at $0/mo. There is no account, no seat, no usage meter on the skill.

The real cost is tokens. Every deck is a generation run through your agent, and you pay your model provider for that. A 10-slide deck involves reading the skill file, selecting templates, and writing roughly ten HTML files plus CSS. That is a meaningful token spend, though it varies enormously with model choice and how much iteration you do.

Model pricing is where the cost becomes concrete. At the low end of the current snapshot, a model like openai/gpt-5-pro lists at $15 per million input tokens and $120 per million output tokens. Mid-range options like anthropic/claude-opus-4.1 and anthropic/claude-opus-4 list at $15 per million input and $75 per million output. At the high end, openai/o1-pro lists at $150 per million input and $600 per million output, with a batch tier at $75 and $300 respectively.

The practical read: a single 10-slide deck is not going to run you hundreds of dollars on any of these models. But iteration is where cost accumulates. If you regenerate the deck five times chasing a layout you like, you pay five times. The skill's lack of live preview makes iteration more likely, not less, because you cannot see the result until the files are written.

Rate limits are a function of your model provider, not the skill. The skill imposes none. Commercial use is governed by the repository's license, which you should read directly rather than take secondhand. The templates and theme assets are part of the repository and carry whatever license the repository states.

Pros and cons

Pros

• No export lock-in. Output is plain HTML and CSS that you own and can edit by hand.
• Runs entirely offline inside an agent you already pay for. No new subscription.
• 27,727 GitHub stars signals a large user base and active maintenance.
• Two distinct visual languages, editorial magazine and Swiss, both well-executed.
• Static HTML output diffs cleanly in git, unlike binary PPTX files.
• Install is a single git clone with no build step or dependency install.

Cons

• Breaks when template names change. The agent references templates by name, and a rename in a repo update can silently produce a fallback layout or an error.
• No live preview. You find layout problems in the browser after generation, not during.
• CJK font fallback is unreliable without locally installed fonts. The docs do not ship webfonts by default.
• No native PPTX export. If stakeholders need PowerPoint files, you are printing to PDF and losing editability.
• Text overflow on dense slides requires iteration, because HTML does not auto-fit text.

Verdict

Guizang PPT Skill is the right answer for a specific person: someone already running a local coding agent, producing decks that stay in-house, and comfortable with HTML as the final artifact. For that person it is close to ideal. The skill is free, the output is clean, and nothing leaves the machine.

It is the wrong answer for anyone whose deck has to end up as an editable PowerPoint file, or who needs a visual editor to nudge elements around, or who is not already paying for a compatible agent. The lack of live preview and the CJK font fragility are real friction, not nitpicks.

Rating: 4.0 / 10

Skip it if you need PPTX export, if you work primarily in CJK and cannot control the presentation machine's fonts, or if you do not already run a skill-capable agent. Pick it if you want local, ownable, offline deck generation and are willing to iterate in the browser.

How this review was researched

This review draws on the public repository at github.com/op7418/guizang-ppt-skill, including its README and SKILL.md, the vendor documentation for supported agent hosts, the official pricing pages for the comparison tools, and the live model pricing data current as of 2026. No hands-on testing was performed. Claims about output quality are based on the documented behavior of the skill and the constraints of HTML and CSS rendering, not on generated decks.