Skip to content
Back to search

pptx-nova

PowerPoint, rebuilt for agents. Not another slide generator. Create, edit, translate, and refurbish truly editable decks with DeckKit design systems, template-aware workflows, and visual QA. Powered by xdoc.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/hustcer/pptx-nova with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/hustcer/pptx-nova'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/hustcer--pptx-nova/badge.svg)](/listings/hustcer--pptx-nova)

HTML

<a href="/listings/hustcer--pptx-nova"><img src="/api/listings/hustcer--pptx-nova/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 507 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # pptx-nova
  2. English | [简体中文](README.zh-CN.md)
  3. `pptx-nova` is an agent skill for creating, editing, refurbishing, translating, and checking
  4. PowerPoint slides, presentations, and slide decks. Use it as an AI slide generator or
  5. presentation editor. It is designed to deliver real, editable `.pptx`
  6. files, not slide screenshots pasted into a deck.
  7. Use it when you want an AI agent to turn a brief, outline, Markdown/text
  8. document, pasted table, CSV/JSON data, reference deck, or existing presentation
  9. into an editable PowerPoint file. The primary target is PowerPoint; Keynote and
  10. other compatible office suites can usually open the result, subject to their
  11. PPTX compatibility.
  12. ## See the results
  13. Compare source and result side by side, with synchronized slides:
  14. - [Refurbishment showcase](https://structurify.io/en/showcases/refurbish-001/) — see an original math presentation alongside its redesigned version.
  15. - [Translation showcase](https://structurify.io/en/showcases/i18n-001/) — compare the Chinese original with English, French, and German translations.
  16. [![Copper Motion — native PPTX playback](docs/images/copper-motion-playback.gif)](https://structurify.io/en/showcases/copper-motion/)
  17. A 20-second recording of native PPTX playback in the browser. Click the preview for the full interactive showcase.
  18. Explore presentations created with `pptx-nova` directly in your browser:
  19. - [Quiet Canvas](https://structurify.io/en/showcases/quiet-canvas/) · [PPTX source](showcases/D1-Quiet-Canvas.pptx)
  20. - [Electric Stage](https://structurify.io/en/showcases/electric-stage/) · [PPTX source](showcases/D2-Electric-Stage.pptx)
  21. - [Copper Motion](https://structurify.io/en/showcases/copper-motion/) · [PPTX source](showcases/D5-Copper-Motion.pptx)
  22. - [Signal Depth](https://structurify.io/en/showcases/signal-depth/) · [PPTX source](showcases/D6-Signal-Depth.pptx)
  23. Tip: Click the triangular play button in the bottom-right corner of a showcase to see it in action.
  24. **These are real, native, editable PPTX files!**
  25. ## Let your AI assistant install it
  26. Open an AI assistant that supports local skills and can install dependencies
  27. and access files, such as Claude Code or Codex. Send it this request:
  28. ```text
  29. Install the pptx-nova skill from hustcer/pptx-nova and its required dependencies.
  30. After installation, check that it is ready to use.
  31. ```
  32. Let the assistant choose the installation method for your environment, install
  33. the skill and the `xdoc` runtime that handles PowerPoint files, and check the
  34. setup. Ask it to confirm:
  35. - `pptx-nova` is available in the assistant you are using.
  36. - The required runtime is installed and can run in that assistant's environment.
  37. <details>
  38. <summary>Manual installation (optional)</summary>
  39. For these npm-based installation steps, use Node.js 22.20 or newer, as required
  40. by the [skills CLI](https://github.com/vercel-labs/skills#install-a-skill).
  41. Install only the user-facing `pptx-nova` skill from this repository:
  42. ```bash
  43. npx skills add hustcer/pptx-nova --skill pptx-nova
  44. ```
  45. The default scope is the current project. For a global installation to a specific Agent:
  46. ```bash
  47. # Claude Code
  48. npx skills add hustcer/pptx-nova --skill pptx-nova -g -a claude-code -y
  49. # Codex
  50. npx skills add hustcer/pptx-nova --skill pptx-nova -g -a codex -y
  51. ```
  52. `-g` installs at user scope, `-a` selects the Agent, and `-y` skips confirmation prompts.
  53. To list the repository's skills without installing them, run
  54. `npx skills add hustcer/pptx-nova --list`. The `deckkit-maker` skill is for DeckKit
  55. development and is not required to use `pptx-nova`.
  56. The skill installer does not install the `xdoc` runtime. Real PPTX creation, editing,
  57. conversion, and preview workflows also require `xdoc` on the Agent's `PATH`.
  58. Install the documented runtime release separately:
  59. ```bash
  60. npm i -g @s8fy/xdoc@0.25.0
  61. xdoc --version
  62. ```
  63. See the [xdoc installation guide](docs/xdoc-installation.md) for native archives,
  64. platform requirements, and runtime verification.
  65. </details>
  66. ## Make your first presentation
  67. Once the setup checks pass, send this request to the same assistant:
  68. ```text
  69. Use pptx-nova to create a 3-slide Chinese presentation about getting started
  70. with remote work. Use a clean style and save it as demo.pptx in the current
  71. working folder.
  72. ```
  73. When creating PPTX files, you can use a DeckKit for consistent colors, typography,
  74. and page layouts. Browse the [DeckKit preview gallery](https://structurify.io/en/deckkits/)
  75. to choose one that suits your content and presentation setting, then include its
  76. name in your request to the assistant.
  77. When the task succeeds, the assistant should provide the location or a link to
  78. the editable PPTX file. You can continue in the same conversation:
  79. ```text
  80. Make the title on slide 2 shorter. Keep the other content unchanged.
  81. ```
  82. To edit an existing presentation, give the assistant access to the `.pptx`
  83. file or its local path, describe the changes, and choose a new output filename.
  84. See [Typical requests](#typical-requests) for editing, translation, and export examples.
  85. ## Licenses and plans
  86. Free works without an account or license for single-user local noncommercial
  87. tasks: up to 10 slides and 5 MiB of compressed PPTX inputs combined per task,
  88. with a `structurify.io` watermark on PPTX, PDF, and PNG outputs.
  89. Personal is currently free for personal local noncommercial use. Installing
  90. its license removes these plan-level slide and input-size limits and adds no
  91. new plan watermark; format, resource, and existing watermark rules still apply.
  92. [Apply for Personal](https://structurify.io/en/commerce/?product=runtime-personal),
  93. then ask your assistant to install and check the downloaded file.
  94. The standard automated visual checks need a license that supports unwatermarked
  95. conversion, such as Personal. See the application page for validity and usage
  96. terms, and the [licensing guide](pptx-nova/references/runtime/licensing.md)
  97. for installation, renewal, and other deployment scenarios.
  98. ## Get help from your AI assistant
  99. Share the original error message with your assistant and ask it to diagnose the
  100. problem. You can use these requests:
  101. | Problem | What to say to your assistant |
  102. | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
  103. | The skill is unavailable or installation did not complete | Check whether pptx-nova is installed for this assistant and verify its dependencies. Help me fix the setup. |
  104. | A task reports an error | Check the original error message, explain the cause, and help me continue the task. |
  105. | You cannot find the generated file | Tell me where the final PPTX was saved and provide a file link or full path. |
  106. ## What pptx-nova can do
  107. - Create a new presentation from a short brief, structured outline,
  108. Markdown/text document, PDF, web page, pasted table, or CSV/JSON data.
  109. - Rebuild editable PPTX files from structured JSON deck sources, making decks
  110. easier to version, review, replay, and regenerate with visual checks.
  111. - Refurbish an existing deck with the goal of preserving the original content
  112. while making the visual system cleaner and more consistent, and deliver
  113. source-vs-final comparison images covering every slide for review.
  114. - Translate an existing `.pptx` into another language while aiming to preserve
  115. original deck structure, layout, styles, objects, notes, animations, and
  116. visual hierarchy, and deliver source-vs-translation comparison images
  117. covering every slide for review.
  118. - Edit existing decks, including titles, copy, slide order, visuals, colors,
  119. charts, tables, and selected page elements.
  120. - Preserve explicit current-deck follow-up rules, such as applying the same
  121. title color to slides added later, and verify supported rules in the final PPTX.
  122. - Inspect real PPTX structure, select exact target objects, dry-run edits, and
  123. apply changes to validated candidates before publishing a final file.
  124. - Use a company template or reference deck as a guide while avoiding
  125. unapproved reuse of private or non-redistributable assets.
  126. - Fill supported content into an existing PPTX template or copy selected slides
  127. between decks, subject to template, slide-size, and resource checks.
  128. - Apply or check brand, theme, and visual-system changes through DeckKit and
  129. `xdoc` workflows where supported.
  130. - Generate data-driven slides from CSV/JSON data, using editable tables,
  131. charts, diagrams, and shapes where supported.
  132. - Create or safely edit supported PPTX animations and transitions.
  133. - Convert existing or generated PPTX decks to high-fidelity PDF, and render PNG
  134. previews for visual review.
  135. - Extract supported deck content and metadata as Markdown, text, or JSON,
  136. including notes, links, fonts, and resources; run preflight checks for fonts,
  137. links, compatibility, or accessibility.
  138. - Run quality checks that look for overlap, clipped text, layout drift,
  139. template violations, content-preservation issues, visual defects, and
  140. before/after drift.
  141. ## Typical requests
  142. You can start with a plain-language instruction:
  143. ```text
  144. Use pptx-nova to create an 8-slide English product strategy deck for a SaaS
  145. leadership team. Use a clean consulting style and save it as strategy-review.pptx.
  146. ```
  147. Or ask it to refurbish an existing deck:
  148. ```text
  149. Refurbish qbr.pptx. Keep the content and slide count, make the visual design more
  150. consistent and executive-ready, and export qbr-refined.pptx plus PNG previews.
  151. ```
  152. Or make a precise edit:
  153. ```text
  154. Update sales-review.pptx: change the title on slide 2, replace the KPI table on
  155. slide 5 with data from metrics.csv, and write the result to sales-review-v2.pptx.
  156. ```
  157. Or translate a presentation while retaining the source:
  158. ```text
  159. Translate product-launch.pptx from Chinese to English. Preserve the original
  160. layout, formatting, charts, speaker notes, animations, and slide count. Use
  161. concise US English terminology and write product-launch-en.pptx.
  162. ```
  163. Or export an existing presentation:
  164. ```text
  165. Convert proposal.pptx to a high-fidelity PDF and save it as proposal.pdf.
  166. ```
  167. Or reuse an existing template:
  168. ```text
  169. Fill company-template.pptx with the quarterly results in metrics.csv. Keep the
  170. company's visual style and save the new presentation as quarterly-results.pptx.
  171. ```
  172. ## What to provide
  173. You can give a single sentence, but results are usually better when you include:
  174. - Purpose: pitch, board update, QBR, sales deck, training, proposal, lecture, or
  175. workshop.
  176. - Audience: executives, customers, investors, sales teams, students, internal
  177. teams, or public conference attendees.
  178. - Length: exact slide count or an approximate range.
  179. - Language: English, Chinese, bilingual, or another target language.
  180. - Source material: outline, notes, Markdown/text content, existing PPTX, PDF,
  181. CSV/JSON, screenshots, links, product copy, brand assets, or a template deck.
  182. - Translation target, when translating: source language if mixed or ambiguous,
  183. target language and locale, terminology preferences, tone, and whether chart
  184. labels, alt text, link text/tooltips, or speaker notes should be localized.
  185. - Style direction: formal, minimal, consulting, technical, editorial, product
  186. marketing, training-oriented, or strict brand template.
  187. - Constraints: content that must not change, slides that must be preserved,
  188. whether restructuring is allowed, and the required output path.
  189. By default, pptx-nova should not overwrite your original deck. Ask for a new
  190. output filename unless you intentionally want to replace a file.
  191. HTML, web pages, and PDFs are treated as source material. They are first
  192. normalized into text or Markdown and then routed through the deck workflow;
  193. pptx-nova does not promise to copy their original page layout, imagery, or
  194. styles into PowerPoint one-to-one. PDF extraction quality depends on the source;
  195. scans or embedded fonts can result in missing characters or incorrect reading
  196. order, so check the extracted content. CSV and JSON can provide tabular data;
  197. arbitrary JSON, Excel workbooks, and Word documents are not direct deck inputs.
  198. ## Outputs
  199. A normal run can produce:
  200. - A final editable `.pptx` file.
  201. - A high-fidelity PDF export and optional per-slide PNG previews.
  202. - Optional validation reports for visual checks, template checks, and
  203. content-preservation checks.
  204. - For translation or refurbishment runs, side-by-side comparison images that
  205. cover each source slide and its delivered result. Decks up to 20 slides use
  206. one image; larger decks use numbered images and a coverage manifest.
  207. - For translation runs, optional source-language/target-language review notes
  208. that show what was translated, what was intentionally shortened, and any
  209. layout risks that still deserve human review.
  210. - A short summary of what changed and any remaining review risks.
  211. Run evidence is normally retained under `.pptx-nova/<run>/`, including the
  212. capability snapshot, relevant plans or patches, validation reports, and visual
  213. review artifacts. Successful runs may be slimmed while retaining their essential
  214. evidence; failed or interrupted runs are kept for inspection or resumption.
  215. For high-stakes decks, treat the generated file as a strong draft and still do a
  216. human review of facts, claims, numbers, brand compliance, and legal language.
  217. External pages, PDFs, and document text are treated as untrusted source material. The workflow
  218. requires agents to distinguish content from instructions, keep retrieval within the user's task,
  219. and review extracted material before authoring. Unknown sources should be processed in a host-enforced
  220. sandbox with limited file/network access; the skill itself does not create one. These measures
  221. reduce indirect prompt-injection risk but cannot guarantee immunity or removal of Snyk's W011
  222. exposure warning. See the [source-content safety policy](pptx-nova/references/policies/source-content-safety.md).
  223. ## Powered by [`xdoc`](docs/xdoc-introducution.md)
  224. xdoc is an agent-native document execution runtime for native, editable PPTX work.
  225. > **xdoc is a high-performance, agent-first, headless PPTX runtime built for high-fidelity creation and editing.**
  226. The verified release is `0.25.0 (838a61af)`. It exposes runtime discovery,
  227. native editable creation and modification, dry-runs, preservation diagnostics,
  228. rendering, validation, and auditable evidence. Support is specific to each
  229. object and operation; it does not imply complete PowerPoint feature parity.
  230. pptx-nova is built on `xdoc`, an in-house PPTX engine for AI agents. It can inspect
  231. the real PowerPoint file structure, validate declarative JSON patches with
  232. dry-runs, apply native editable changes, render previews, compare source and
  233. candidate decks, export existing or generated presentations to high-fidelity
  234. PDF, and leave replayable sidecar evidence.
  235. All of this runs through a single lightweight native CLI with integrated
  236. rendering backends: previews, PDF export, and visual checks require no
  237. PowerPoint, office suite, or headless browser. The current `v0.25.0` native
  238. archives download as approximately 8.4–10.3 MB (decimal), depending on the target, and need no
  239. separate server or always-on background service. Native builds are available
  240. for Linux x64/ARM64, macOS 13+ ARM64, and Windows x64. Rendering still depends
  241. on the available fonts and the support status of the requested feature.
  242. Install the published CLI with `npm i -g @s8fy/xdoc@0.25.0` (Node.js 22+), or
  243. use a [native release archive](docs/xdoc-installation.md).
  244. That changes the workflow: pptx-nova can plan a deck with DeckKits, edit real
  245. PPTX objects instead of screenshots, check selectors before writing, preserve
  246. the original deck by default, and produce review artifacts that make the result
  247. auditable. It is closer to a structured PPTX build/edit pipeline than a
  248. one-shot slide generator.
  249. ### Targeted edits to the original PPTX
  250. `xdoc` applies targeted changes to objects and related PPTX structures in the
  251. original file, without rebuilding the entire presentation. Untouched OOXML
  252. parts, relationships, and extension data are preserved where possible. The
  253. source remains read-only by default, and the result is published as a
  254. separately validated candidate.
  255. ## How it works
  256. Describe the result you need. pptx-nova creates or edits the deck, checks it,
  257. and uses machine findings and visual review to guide the next revision.
  258. Fixes return to validation; delivery follows the required checks and review.
  259. <p align="center">
  260. <img src="docs/images/pptx-workflow-overview.svg" alt="Agent feedback loop: create or edit a deck, check structure, scope and visuals, use findings to fix and recheck it, and deliver an editable PPTX only after the required checks and visual review pass" />
  261. </p>
  262. New decks use DeckKits: reusable visual systems with page types, typography,
  263. layout rules, and quality checks. Existing decks are edited through scoped
  264. changes to their native objects, with the original file kept read-only by
  265. default.
  266. See the [full creation and editing workflows](docs/workflows.md) for the
  267. detailed steps, validation gates, and retry paths.
  268. ### Capability and playback boundaries
  269. pptx-nova discovers capabilities from the installed `xdoc` runtime for each
  270. run. Creating, editing, preserving, rendering, and verifying an object are
  271. separate capabilities: a feature that can be preserved or rendered is not
  272. necessarily editable. Complex animations and other unsupported regions may
  273. need to remain untouched or require a different workflow. See the
  274. [compatibility reference](docs/xdoc-compatibility.md) for current boundaries.
  275. PNG and PDF previews show static slides; they do not prove that animations or
  276. transitions play correctly in PowerPoint. When playback matters, review it in
  277. the intended presentation environment and treat unavailable playback evidence
  278. as a remaining review risk.
  279. ### Scoped edit safety
  280. For localized edits, pptx-nova records the intended scope before writing and
  281. publishes the candidate only after a deterministic gate confirms that:
  282. - requested targets were covered without reliable out-of-scope changes;
  283. - source, candidate, and validation evidence still belong together; and
  284. - relevant formatting and visual-regression checks passed.
  285. Failures are blocked with a specific next action instead of being silently
  286. delivered. Complex or uncertain PPTX regions can still require specialized
  287. checks or human review.
  288. ### Reliable follow-up rules
  289. For multi-turn work on the same deck, pptx-nova can preserve explicit
  290. future/carryover instructions instead of relying on temporary chat memory. It
  291. records the rule against the current deck revision, resolves conflicts and
  292. one-time overrides, and verifies supported style rules in the final PPTX before
  293. delivery.
  294. The current scope is deliberately narrow and deterministic. It does not infer
  295. long-term preferences from vague feedback, create a cross-project user profile,
  296. or allow a session rule to bypass template and quality checks. Rules that do not
  297. apply to the current edit add no extra edit target or delivery evidence.
  298. This is the part that makes pptx-nova different from many generic slide
  299. generators, screenshot pipelines, or small PowerPoint scripting snippets:
  300. - It aims to produce native editable PPTX objects, not a deck made of flattened
  301. slide images.
  302. - It keeps a durable plan (`outline.json`, `deck_lock.json`, `content.json`, or
  303. `patch.json`) so the work can be reviewed, replayed, and continued.
  304. - It uses `xdoc`'s `inspect`, `select`, `dry-run`, `apply`, `preview`,
  305. `vision-check`, `diff`, and sidecar/replay capabilities as guardrails around
  306. the actual file write.
  307. - It treats the original deck as read-only by default and writes validated
  308. candidates before publishing a final file.
  309. - It leaves a small audit trail of reports and previews so users can see what
  310. changed, what was checked, and what still deserves human review.
  311. The result is still a document that should be reviewed like any business
  312. presentation, especially for facts, numbers, legal wording, and brand approval.
  313. The workflow is designed to make that review easier: the deck stays editable,
  314. the changes are traceable, and visual defects are looked for before delivery.
  315. ## Translating presentations
  316. Translation is handled as a style-preserving edit, not as deck recreation. The
  317. source deck stays read-only, and the translated file is written to a separate
  318. output path.
  319. For translation requests, provide at least:
  320. - Source `.pptx` path.
  321. - Target language, and source language when the deck is mixed-language or
  322. ambiguous.
  323. - Output `.pptx` path.
  324. - Terminology, locale, tone, or brand wording requirements.
  325. Translation aims to preserve bold, italic, underline, strikethrough, colors,
  326. fonts, alignment, bullets, indentation, text box geometry, table and chart
  327. styling, hyperlinks, notes, animations, and transitions unless you explicitly
  328. ask for a broader redesign.
  329. Because translated text often expands or wraps differently, fitting fixes should
  330. be conservative: first use shorter wording without changing the meaning, then
  331. make small font-size adjustments if needed, and only change text box geometry
  332. when the slide clearly has room.
  333. Translation checks should cover more than ordinary slide text. Chart titles,
  334. series names, category labels, data labels, table cells, alt text, hyperlink
  335. tooltips, and speaker notes can also contain user-visible text and may need
  336. translation.
  337. Do not treat a translated deck as complete just because text replacement
  338. succeeded. The final review must confirm that the target-language deck still
  339. looks like the source deck, has no remaining source-language visible text that
  340. should have been translated, and has no new clipping, overlap, broken chart
  341. labels, lost formatting, or PowerPoint repair issues.
  342. ## Repository layout
  343. ```text
  344. .
  345. +-- pptx-nova/ # The main publishable pptx-nova skill
  346. | +-- README.md # English user guide
  347. | +-- README.zh-CN.md # Chinese user guide
  348. | +-- SKILL.md # Agent instructions and task routing
  349. | +-- assets/ # DeckKits, examples, themes, icons, schemas
  350. | +-- benchmarks/visual/ # Visual benchmark cases and baselines
  351. | +-- references/ # Workflow references for agents and maintainers
  352. | +-- scripts/ # Skill runtime scripts and helper gates
  353. | `-- evals/ # Skill evaluation metadata
  354. +-- deckkit-maker/ # Developer-side helper skill for DeckKit creation
  355. `-- tools/ # Repository-level smoke and public-release checks
  356. ```
  357. ## DeckKit previews
  358. When creating PPTX files, you can use a DeckKit for consistent colors, typography,
  359. and page layouts. Browse the [DeckKit preview gallery](https://structurify.io/en/deckkits/)
  360. to choose one that suits your content and presentation setting, then include its
  361. name in your request to the assistant.
  362. ## About deckkit-maker
  363. `deckkit-maker` is included as a companion developer skill. It exists to create,
  364. repair, and benchmark new DeckKits for pptx-nova from a reference `.pptx` file
  365. or an HTML slide template.
  366. It is not the main user-facing deck generation path. For normal presentation
  367. creation, editing, refurbishment, and QA, use `pptx-nova`. Use `deckkit-maker`
  368. only when the existing DeckKits are not enough and the reusable visual system
  369. itself needs to be built or extended.
  370. ## Our other products
  371. - **[xdoc Runtime](https://structurify.io/en/products/pptx-runtime/)** — An Agent-ready native
  372. CLI to inspect, create, edit, render, and verify PowerPoint files.
  373. - **[PPTX Viewer](https://structurify.io/en/products/pptx-viewer/)** — A browser SDK for
  374. PowerPoint preview and supported animation playback, with Web Component and framework integrations.
  375. - **[PPTX Converter](https://structurify.io/en/products/pptx-converter/)** — An SDK for local
  376. PPTX-to-PDF and Markdown conversion in browsers, Node.js, Bun, and Deno.
  377. - **[PPTX API Service](https://structurify.io/en/products/pptx-api/)** — An HTTP service designed
  378. for **private deployment via Docker images**, with PPTX conversion, extraction, and checks.
  379. Currently a loopback-only development preview; production deployment is not yet available.
  380. ## Acknowledgments
  381. - [Tabler Icons](https://github.com/tabler/tabler-icons)
  382. - [PPT Master](https://github.com/hugohe3/ppt-master)
  383. - [Beautiful HTML Templates](https://github.com/zarazhangrui/beautiful-html-templates)
  384. - [PPTAgent: Generating and Evaluating Presentations Beyond Text-to-Slides](https://arxiv.org/abs/2501.03936)
  385. ## More documentation
  386. - [pptx-nova user guide](pptx-nova/README.md)
  387. - [pptx-nova 中文使用指南](pptx-nova/README.zh-CN.md)
  388. - [xdoc introduction and architecture](docs/xdoc-introducution.md)
  389. - [Install the xdoc CLI](docs/xdoc-installation.md)
  390. - [xdoc compatibility reference](docs/xdoc-compatibility.md)
  391. - [DeckKit preview gallery](https://structurify.io/en/deckkits/)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.