Install
npx skills add https://github.com/lewislulu/html-ppt-skillWho it's for
If you want an Agent to produce an HTML deck you can open directly, instead of walking another packaging toolchain, this AgentSkill fits better. It targets professional HTML decks: themes, full-deck templates, single-page layouts, animation, and a presenter mode with preview, speaker notes, and a timer. The result is pure static HTML/CSS/JS with no build step.
You need an Agent runtime that supports AgentSkills, and you accept registering the skill with npx. If you only want to hand-write a few HTML pages and do not plan to let an Agent write them, the benefit is limited. Chinese notes:
https://github.com/lewislulu/html-ppt-skill/blob/main/README.zh-CN.md
The page also writes the license as MIT. It does not write one chat product as the only client, so do not invent a limit that it can only be used in one house.
First try in 3 minutes
The official install command is only this one:
npx skills add https://github.com/lewislulu/html-ppt-skill
It registers the skill with your Agent runtime. This changes the runtime skill list; it is not a read-only view. First confirm this machine has npx and this is the environment you want to write into, then execute.
After install, do one low-risk trial write: have an Agent that supports AgentSkills generate a static HTML deck as short as possible. Before writing files, have it state the path and page count it will create; you nod, then allow a write to disk. Success has two layers: you get HTML that opens in a browser with no build step in between; after opening, press S and a separate presenter window pops up. If the Agent starts changing your existing site project or appending build scripts, stop first.
The page writes that after install you can proceed “by asking things like”, but this excerpt gives no concrete ask sentence. So the first time do not invent a phrase set; only require "short, static, openable, confirm the path first".
Use cases
Case 1: Have the Agent make a deck by theme and layout. The page gives the scale as 36 themes, 15 full-deck templates, 31 single-page layouts, with resources in assets/themes/*.css, templates/full-decks/<name>/, templates/single-page/*.html. Animation is 27 CSS animations plus 20 canvas FX. The excerpt does not write each theme name, and it does not write how the Agent will pick a template. So you can ask for: produce a static HTML deck and reuse these ready resources where possible. You cannot, from this material, demand "must use one theme name that was never written". Still confirm the output path before generation.
Case 2: Check presenter mode. After any finished deck is open, press S and a dedicated presenter window pops up with four magnetic cards you can drag and scale: current page, next-page preview, speaker notes, timer. The two windows stay in sync via BroadcastChannel. The page writes no browser roster and does not write what to do if there is no second window. So acceptance only sees: after S, the four blocks above appear, and preview and notes follow when you change pages. Do not have the Agent keep changing the HTML at this step.
Boundaries
Counts follow the page table: themes 36, full-deck templates 15, single-page layouts 31, CSS animations 27, canvas FX 20. Do not change these counts with possibly older numbers from the repository title. Paths are written at directory level; there is no complete file inventory.
The install path is the npx skills add above. There is no second installer beside it. After registration, only a runtime that supports AgentSkills is written as able to make decks; do not assume tools that do not support that standard already work.
A finished file has no build step, which is not the same as never writing disk. The first time, finish a static file of one page or a few pages, and press S to check the presenter window. Any action that would overwrite an existing deck, batch-generate dozens of pages, or bring in an external build must first have the Agent recite the files it will change; you confirm, then continue.