Install
https://github.com/op7418/guizang-ppt-skillWho it's for
Use this skill when you need a single-file HTML landscape-paging deck inside an agent environment such as Claude Code or Codex, plus optional PPT images and multi-platform covers, and you also want the built-in rehearsal and presenter modes. What it produces is a web slideshow, not a desktop slide format that the notes never name.
Pick a visual system first. Style A, “digital magazine × e-ink,” leans toward narrative, opinion, sharing, and a personal voice. Style B, “Swiss International Style,” leans toward facts, product, analysis, and method. If the topic and the style do not match, change the topic or change the style. Do not mix in a third skin the notes never describe.
The notes only name Claude Code / Codex and similar agent environments. They give no install command and no on-disk directory. You must already be able to attach skills in that kind of agent. Do not invent an installer that never appears, and do not stretch “and similar” into a full roster of unnamed clients.
First try in 3 minutes
Official page:
https://github.com/op7418/guizang-ppt-skill
The way to obtain it is this repository itself. Open the page first, confirm the current agent belongs to the named Claude Code / Codex class of environments, then attach the skill the way that environment already does. The notes copy no ready-to-run install command. If the command fails or the agent does not recognize the skill, stop.
The first pass should not write a full HTML file, and should not start with multi-platform covers. Pick a small fact-or-analysis topic, name Style B explicitly, and ask only for a landscape-paging structure of about three pages: title per page, the fact to emphasize, and what in the grid is the anchor color. After that structure is acceptable, allow it to generate the single-file HTML, then open that file in a browser at once and check that landscape paging works.
Success signals: the reply shows Swiss International Style grid, a single high-saturation anchor color, or type-size contrast, and you can open one single-file HTML and page it sideways. If it starts writing cover images or switches to Style A, stop it and return to this page structure.
Use cases
Case 1: make a rehearsable single-file HTML landscape-paging deck. After you pick Style A or Style B, let the skill generate that one HTML file, then walk it with the built-in rehearsal and presenter modes. Style A fits narrative and personal sharing; Style B fits product and method. Run only one system per pass. The notes never demonstrate export to other formats and never write presenter shortcuts. What you can check is only this: the file is single-file HTML, and rehearsal / presenter mode can open.
Case 2: add images and multi-platform covers for the same deck. That is a different product. Do not mix it with slide body text into one unconfirmed batch write. First let it say what image this page needs and which already-named uses the covers must cover; generate files only after you confirm, then open each one and check. The notes only write “PPT images and multi-platform covers.” They list no platform names and no image sizes. Do not invent the missing specs.
Boundaries
Evidence only reaches single-file HTML landscape-paging decks, PPT images, multi-platform covers, and rehearsal plus presenter mode. Do not assume it can export formats that never appear.
Visual systems are only Style A and Style B. A maps to narrative and personal expression; B maps to facts, product, analysis, and method. Do not invent a third style.
Environments are written only as Claude Code / Codex and similar agent environments. Do not infer that only those two work, and do not invent steps for unnamed platforms.
The notes give no install command, on-disk directory, language range, or pricing. Keep unknown items unknown. Do not invent operations.