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.
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
Markdown
[](/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
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.
- # pptx-nova
- English | [简体中文](README.zh-CN.md)
- `pptx-nova` is an agent skill for creating, editing, refurbishing, translating, and checking
- PowerPoint slides, presentations, and slide decks. Use it as an AI slide generator or
- presentation editor. It is designed to deliver real, editable `.pptx`
- files, not slide screenshots pasted into a deck.
- Use it when you want an AI agent to turn a brief, outline, Markdown/text
- document, pasted table, CSV/JSON data, reference deck, or existing presentation
- into an editable PowerPoint file. The primary target is PowerPoint; Keynote and
- other compatible office suites can usually open the result, subject to their
- PPTX compatibility.
- ## See the results
- Compare source and result side by side, with synchronized slides:
- - [Refurbishment showcase](https://structurify.io/en/showcases/refurbish-001/) — see an original math presentation alongside its redesigned version.
- - [Translation showcase](https://structurify.io/en/showcases/i18n-001/) — compare the Chinese original with English, French, and German translations.
- [](https://structurify.io/en/showcases/copper-motion/)
- A 20-second recording of native PPTX playback in the browser. Click the preview for the full interactive showcase.
- Explore presentations created with `pptx-nova` directly in your browser:
- - [Quiet Canvas](https://structurify.io/en/showcases/quiet-canvas/) · [PPTX source](showcases/D1-Quiet-Canvas.pptx)
- - [Electric Stage](https://structurify.io/en/showcases/electric-stage/) · [PPTX source](showcases/D2-Electric-Stage.pptx)
- - [Copper Motion](https://structurify.io/en/showcases/copper-motion/) · [PPTX source](showcases/D5-Copper-Motion.pptx)
- - [Signal Depth](https://structurify.io/en/showcases/signal-depth/) · [PPTX source](showcases/D6-Signal-Depth.pptx)
- Tip: Click the triangular play button in the bottom-right corner of a showcase to see it in action.
- **These are real, native, editable PPTX files!**
- ## Let your AI assistant install it
- Open an AI assistant that supports local skills and can install dependencies
- and access files, such as Claude Code or Codex. Send it this request:
- ```text
- Install the pptx-nova skill from hustcer/pptx-nova and its required dependencies.
- After installation, check that it is ready to use.
- ```
- Let the assistant choose the installation method for your environment, install
- the skill and the `xdoc` runtime that handles PowerPoint files, and check the
- setup. Ask it to confirm:
- - `pptx-nova` is available in the assistant you are using.
- - The required runtime is installed and can run in that assistant's environment.
- <details>
- <summary>Manual installation (optional)</summary>
- For these npm-based installation steps, use Node.js 22.20 or newer, as required
- by the [skills CLI](https://github.com/vercel-labs/skills#install-a-skill).
- Install only the user-facing `pptx-nova` skill from this repository:
- ```bash
- npx skills add hustcer/pptx-nova --skill pptx-nova
- ```
- The default scope is the current project. For a global installation to a specific Agent:
- ```bash
- # Claude Code
- npx skills add hustcer/pptx-nova --skill pptx-nova -g -a claude-code -y
- # Codex
- npx skills add hustcer/pptx-nova --skill pptx-nova -g -a codex -y
- ```
- `-g` installs at user scope, `-a` selects the Agent, and `-y` skips confirmation prompts.
- To list the repository's skills without installing them, run
- `npx skills add hustcer/pptx-nova --list`. The `deckkit-maker` skill is for DeckKit
- development and is not required to use `pptx-nova`.
- The skill installer does not install the `xdoc` runtime. Real PPTX creation, editing,
- conversion, and preview workflows also require `xdoc` on the Agent's `PATH`.
- Install the documented runtime release separately:
- ```bash
- npm i -g @s8fy/xdoc@0.25.0
- xdoc --version
- ```
- See the [xdoc installation guide](docs/xdoc-installation.md) for native archives,
- platform requirements, and runtime verification.
- </details>
- ## Make your first presentation
- Once the setup checks pass, send this request to the same assistant:
- ```text
- Use pptx-nova to create a 3-slide Chinese presentation about getting started
- with remote work. Use a clean style and save it as demo.pptx in the current
- working folder.
- ```
- When creating PPTX files, you can use a DeckKit for consistent colors, typography,
- and page layouts. Browse the [DeckKit preview gallery](https://structurify.io/en/deckkits/)
- to choose one that suits your content and presentation setting, then include its
- name in your request to the assistant.
- When the task succeeds, the assistant should provide the location or a link to
- the editable PPTX file. You can continue in the same conversation:
- ```text
- Make the title on slide 2 shorter. Keep the other content unchanged.
- ```
- To edit an existing presentation, give the assistant access to the `.pptx`
- file or its local path, describe the changes, and choose a new output filename.
- See [Typical requests](#typical-requests) for editing, translation, and export examples.
- ## Licenses and plans
- Free works without an account or license for single-user local noncommercial
- tasks: up to 10 slides and 5 MiB of compressed PPTX inputs combined per task,
- with a `structurify.io` watermark on PPTX, PDF, and PNG outputs.
- Personal is currently free for personal local noncommercial use. Installing
- its license removes these plan-level slide and input-size limits and adds no
- new plan watermark; format, resource, and existing watermark rules still apply.
- [Apply for Personal](https://structurify.io/en/commerce/?product=runtime-personal),
- then ask your assistant to install and check the downloaded file.
- The standard automated visual checks need a license that supports unwatermarked
- conversion, such as Personal. See the application page for validity and usage
- terms, and the [licensing guide](pptx-nova/references/runtime/licensing.md)
- for installation, renewal, and other deployment scenarios.
- ## Get help from your AI assistant
- Share the original error message with your assistant and ask it to diagnose the
- problem. You can use these requests:
- | Problem | What to say to your assistant |
- | --------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
- | 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. |
- | A task reports an error | Check the original error message, explain the cause, and help me continue the task. |
- | You cannot find the generated file | Tell me where the final PPTX was saved and provide a file link or full path. |
- ## What pptx-nova can do
- - Create a new presentation from a short brief, structured outline,
- Markdown/text document, PDF, web page, pasted table, or CSV/JSON data.
- - Rebuild editable PPTX files from structured JSON deck sources, making decks
- easier to version, review, replay, and regenerate with visual checks.
- - Refurbish an existing deck with the goal of preserving the original content
- while making the visual system cleaner and more consistent, and deliver
- source-vs-final comparison images covering every slide for review.
- - Translate an existing `.pptx` into another language while aiming to preserve
- original deck structure, layout, styles, objects, notes, animations, and
- visual hierarchy, and deliver source-vs-translation comparison images
- covering every slide for review.
- - Edit existing decks, including titles, copy, slide order, visuals, colors,
- charts, tables, and selected page elements.
- - Preserve explicit current-deck follow-up rules, such as applying the same
- title color to slides added later, and verify supported rules in the final PPTX.
- - Inspect real PPTX structure, select exact target objects, dry-run edits, and
- apply changes to validated candidates before publishing a final file.
- - Use a company template or reference deck as a guide while avoiding
- unapproved reuse of private or non-redistributable assets.
- - Fill supported content into an existing PPTX template or copy selected slides
- between decks, subject to template, slide-size, and resource checks.
- - Apply or check brand, theme, and visual-system changes through DeckKit and
- `xdoc` workflows where supported.
- - Generate data-driven slides from CSV/JSON data, using editable tables,
- charts, diagrams, and shapes where supported.
- - Create or safely edit supported PPTX animations and transitions.
- - Convert existing or generated PPTX decks to high-fidelity PDF, and render PNG
- previews for visual review.
- - Extract supported deck content and metadata as Markdown, text, or JSON,
- including notes, links, fonts, and resources; run preflight checks for fonts,
- links, compatibility, or accessibility.
- - Run quality checks that look for overlap, clipped text, layout drift,
- template violations, content-preservation issues, visual defects, and
- before/after drift.
- ## Typical requests
- You can start with a plain-language instruction:
- ```text
- Use pptx-nova to create an 8-slide English product strategy deck for a SaaS
- leadership team. Use a clean consulting style and save it as strategy-review.pptx.
- ```
- Or ask it to refurbish an existing deck:
- ```text
- Refurbish qbr.pptx. Keep the content and slide count, make the visual design more
- consistent and executive-ready, and export qbr-refined.pptx plus PNG previews.
- ```
- Or make a precise edit:
- ```text
- Update sales-review.pptx: change the title on slide 2, replace the KPI table on
- slide 5 with data from metrics.csv, and write the result to sales-review-v2.pptx.
- ```
- Or translate a presentation while retaining the source:
- ```text
- Translate product-launch.pptx from Chinese to English. Preserve the original
- layout, formatting, charts, speaker notes, animations, and slide count. Use
- concise US English terminology and write product-launch-en.pptx.
- ```
- Or export an existing presentation:
- ```text
- Convert proposal.pptx to a high-fidelity PDF and save it as proposal.pdf.
- ```
- Or reuse an existing template:
- ```text
- Fill company-template.pptx with the quarterly results in metrics.csv. Keep the
- company's visual style and save the new presentation as quarterly-results.pptx.
- ```
- ## What to provide
- You can give a single sentence, but results are usually better when you include:
- - Purpose: pitch, board update, QBR, sales deck, training, proposal, lecture, or
- workshop.
- - Audience: executives, customers, investors, sales teams, students, internal
- teams, or public conference attendees.
- - Length: exact slide count or an approximate range.
- - Language: English, Chinese, bilingual, or another target language.
- - Source material: outline, notes, Markdown/text content, existing PPTX, PDF,
- CSV/JSON, screenshots, links, product copy, brand assets, or a template deck.
- - Translation target, when translating: source language if mixed or ambiguous,
- target language and locale, terminology preferences, tone, and whether chart
- labels, alt text, link text/tooltips, or speaker notes should be localized.
- - Style direction: formal, minimal, consulting, technical, editorial, product
- marketing, training-oriented, or strict brand template.
- - Constraints: content that must not change, slides that must be preserved,
- whether restructuring is allowed, and the required output path.
- By default, pptx-nova should not overwrite your original deck. Ask for a new
- output filename unless you intentionally want to replace a file.
- HTML, web pages, and PDFs are treated as source material. They are first
- normalized into text or Markdown and then routed through the deck workflow;
- pptx-nova does not promise to copy their original page layout, imagery, or
- styles into PowerPoint one-to-one. PDF extraction quality depends on the source;
- scans or embedded fonts can result in missing characters or incorrect reading
- order, so check the extracted content. CSV and JSON can provide tabular data;
- arbitrary JSON, Excel workbooks, and Word documents are not direct deck inputs.
- ## Outputs
- A normal run can produce:
- - A final editable `.pptx` file.
- - A high-fidelity PDF export and optional per-slide PNG previews.
- - Optional validation reports for visual checks, template checks, and
- content-preservation checks.
- - For translation or refurbishment runs, side-by-side comparison images that
- cover each source slide and its delivered result. Decks up to 20 slides use
- one image; larger decks use numbered images and a coverage manifest.
- - For translation runs, optional source-language/target-language review notes
- that show what was translated, what was intentionally shortened, and any
- layout risks that still deserve human review.
- - A short summary of what changed and any remaining review risks.
- Run evidence is normally retained under `.pptx-nova/<run>/`, including the
- capability snapshot, relevant plans or patches, validation reports, and visual
- review artifacts. Successful runs may be slimmed while retaining their essential
- evidence; failed or interrupted runs are kept for inspection or resumption.
- For high-stakes decks, treat the generated file as a strong draft and still do a
- human review of facts, claims, numbers, brand compliance, and legal language.
- External pages, PDFs, and document text are treated as untrusted source material. The workflow
- requires agents to distinguish content from instructions, keep retrieval within the user's task,
- and review extracted material before authoring. Unknown sources should be processed in a host-enforced
- sandbox with limited file/network access; the skill itself does not create one. These measures
- reduce indirect prompt-injection risk but cannot guarantee immunity or removal of Snyk's W011
- exposure warning. See the [source-content safety policy](pptx-nova/references/policies/source-content-safety.md).
- ## Powered by [`xdoc`](docs/xdoc-introducution.md)
- xdoc is an agent-native document execution runtime for native, editable PPTX work.
- > **xdoc is a high-performance, agent-first, headless PPTX runtime built for high-fidelity creation and editing.**
- The verified release is `0.25.0 (838a61af)`. It exposes runtime discovery,
- native editable creation and modification, dry-runs, preservation diagnostics,
- rendering, validation, and auditable evidence. Support is specific to each
- object and operation; it does not imply complete PowerPoint feature parity.
- pptx-nova is built on `xdoc`, an in-house PPTX engine for AI agents. It can inspect
- the real PowerPoint file structure, validate declarative JSON patches with
- dry-runs, apply native editable changes, render previews, compare source and
- candidate decks, export existing or generated presentations to high-fidelity
- PDF, and leave replayable sidecar evidence.
- All of this runs through a single lightweight native CLI with integrated
- rendering backends: previews, PDF export, and visual checks require no
- PowerPoint, office suite, or headless browser. The current `v0.25.0` native
- archives download as approximately 8.4–10.3 MB (decimal), depending on the target, and need no
- separate server or always-on background service. Native builds are available
- for Linux x64/ARM64, macOS 13+ ARM64, and Windows x64. Rendering still depends
- on the available fonts and the support status of the requested feature.
- Install the published CLI with `npm i -g @s8fy/xdoc@0.25.0` (Node.js 22+), or
- use a [native release archive](docs/xdoc-installation.md).
- That changes the workflow: pptx-nova can plan a deck with DeckKits, edit real
- PPTX objects instead of screenshots, check selectors before writing, preserve
- the original deck by default, and produce review artifacts that make the result
- auditable. It is closer to a structured PPTX build/edit pipeline than a
- one-shot slide generator.
- ### Targeted edits to the original PPTX
- `xdoc` applies targeted changes to objects and related PPTX structures in the
- original file, without rebuilding the entire presentation. Untouched OOXML
- parts, relationships, and extension data are preserved where possible. The
- source remains read-only by default, and the result is published as a
- separately validated candidate.
- ## How it works
- Describe the result you need. pptx-nova creates or edits the deck, checks it,
- and uses machine findings and visual review to guide the next revision.
- Fixes return to validation; delivery follows the required checks and review.
- <p align="center">
- <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" />
- </p>
- New decks use DeckKits: reusable visual systems with page types, typography,
- layout rules, and quality checks. Existing decks are edited through scoped
- changes to their native objects, with the original file kept read-only by
- default.
- See the [full creation and editing workflows](docs/workflows.md) for the
- detailed steps, validation gates, and retry paths.
- ### Capability and playback boundaries
- pptx-nova discovers capabilities from the installed `xdoc` runtime for each
- run. Creating, editing, preserving, rendering, and verifying an object are
- separate capabilities: a feature that can be preserved or rendered is not
- necessarily editable. Complex animations and other unsupported regions may
- need to remain untouched or require a different workflow. See the
- [compatibility reference](docs/xdoc-compatibility.md) for current boundaries.
- PNG and PDF previews show static slides; they do not prove that animations or
- transitions play correctly in PowerPoint. When playback matters, review it in
- the intended presentation environment and treat unavailable playback evidence
- as a remaining review risk.
- ### Scoped edit safety
- For localized edits, pptx-nova records the intended scope before writing and
- publishes the candidate only after a deterministic gate confirms that:
- - requested targets were covered without reliable out-of-scope changes;
- - source, candidate, and validation evidence still belong together; and
- - relevant formatting and visual-regression checks passed.
- Failures are blocked with a specific next action instead of being silently
- delivered. Complex or uncertain PPTX regions can still require specialized
- checks or human review.
- ### Reliable follow-up rules
- For multi-turn work on the same deck, pptx-nova can preserve explicit
- future/carryover instructions instead of relying on temporary chat memory. It
- records the rule against the current deck revision, resolves conflicts and
- one-time overrides, and verifies supported style rules in the final PPTX before
- delivery.
- The current scope is deliberately narrow and deterministic. It does not infer
- long-term preferences from vague feedback, create a cross-project user profile,
- or allow a session rule to bypass template and quality checks. Rules that do not
- apply to the current edit add no extra edit target or delivery evidence.
- This is the part that makes pptx-nova different from many generic slide
- generators, screenshot pipelines, or small PowerPoint scripting snippets:
- - It aims to produce native editable PPTX objects, not a deck made of flattened
- slide images.
- - It keeps a durable plan (`outline.json`, `deck_lock.json`, `content.json`, or
- `patch.json`) so the work can be reviewed, replayed, and continued.
- - It uses `xdoc`'s `inspect`, `select`, `dry-run`, `apply`, `preview`,
- `vision-check`, `diff`, and sidecar/replay capabilities as guardrails around
- the actual file write.
- - It treats the original deck as read-only by default and writes validated
- candidates before publishing a final file.
- - It leaves a small audit trail of reports and previews so users can see what
- changed, what was checked, and what still deserves human review.
- The result is still a document that should be reviewed like any business
- presentation, especially for facts, numbers, legal wording, and brand approval.
- The workflow is designed to make that review easier: the deck stays editable,
- the changes are traceable, and visual defects are looked for before delivery.
- ## Translating presentations
- Translation is handled as a style-preserving edit, not as deck recreation. The
- source deck stays read-only, and the translated file is written to a separate
- output path.
- For translation requests, provide at least:
- - Source `.pptx` path.
- - Target language, and source language when the deck is mixed-language or
- ambiguous.
- - Output `.pptx` path.
- - Terminology, locale, tone, or brand wording requirements.
- Translation aims to preserve bold, italic, underline, strikethrough, colors,
- fonts, alignment, bullets, indentation, text box geometry, table and chart
- styling, hyperlinks, notes, animations, and transitions unless you explicitly
- ask for a broader redesign.
- Because translated text often expands or wraps differently, fitting fixes should
- be conservative: first use shorter wording without changing the meaning, then
- make small font-size adjustments if needed, and only change text box geometry
- when the slide clearly has room.
- Translation checks should cover more than ordinary slide text. Chart titles,
- series names, category labels, data labels, table cells, alt text, hyperlink
- tooltips, and speaker notes can also contain user-visible text and may need
- translation.
- Do not treat a translated deck as complete just because text replacement
- succeeded. The final review must confirm that the target-language deck still
- looks like the source deck, has no remaining source-language visible text that
- should have been translated, and has no new clipping, overlap, broken chart
- labels, lost formatting, or PowerPoint repair issues.
- ## Repository layout
- ```text
- .
- +-- pptx-nova/ # The main publishable pptx-nova skill
- | +-- README.md # English user guide
- | +-- README.zh-CN.md # Chinese user guide
- | +-- SKILL.md # Agent instructions and task routing
- | +-- assets/ # DeckKits, examples, themes, icons, schemas
- | +-- benchmarks/visual/ # Visual benchmark cases and baselines
- | +-- references/ # Workflow references for agents and maintainers
- | +-- scripts/ # Skill runtime scripts and helper gates
- | `-- evals/ # Skill evaluation metadata
- +-- deckkit-maker/ # Developer-side helper skill for DeckKit creation
- `-- tools/ # Repository-level smoke and public-release checks
- ```
- ## DeckKit previews
- When creating PPTX files, you can use a DeckKit for consistent colors, typography,
- and page layouts. Browse the [DeckKit preview gallery](https://structurify.io/en/deckkits/)
- to choose one that suits your content and presentation setting, then include its
- name in your request to the assistant.
- ## About deckkit-maker
- `deckkit-maker` is included as a companion developer skill. It exists to create,
- repair, and benchmark new DeckKits for pptx-nova from a reference `.pptx` file
- or an HTML slide template.
- It is not the main user-facing deck generation path. For normal presentation
- creation, editing, refurbishment, and QA, use `pptx-nova`. Use `deckkit-maker`
- only when the existing DeckKits are not enough and the reusable visual system
- itself needs to be built or extended.
- ## Our other products
- - **[xdoc Runtime](https://structurify.io/en/products/pptx-runtime/)** — An Agent-ready native
- CLI to inspect, create, edit, render, and verify PowerPoint files.
- - **[PPTX Viewer](https://structurify.io/en/products/pptx-viewer/)** — A browser SDK for
- PowerPoint preview and supported animation playback, with Web Component and framework integrations.
- - **[PPTX Converter](https://structurify.io/en/products/pptx-converter/)** — An SDK for local
- PPTX-to-PDF and Markdown conversion in browsers, Node.js, Bun, and Deno.
- - **[PPTX API Service](https://structurify.io/en/products/pptx-api/)** — An HTTP service designed
- for **private deployment via Docker images**, with PPTX conversion, extraction, and checks.
- Currently a loopback-only development preview; production deployment is not yet available.
- ## Acknowledgments
- - [Tabler Icons](https://github.com/tabler/tabler-icons)
- - [PPT Master](https://github.com/hugohe3/ppt-master)
- - [Beautiful HTML Templates](https://github.com/zarazhangrui/beautiful-html-templates)
- - [PPTAgent: Generating and Evaluating Presentations Beyond Text-to-Slides](https://arxiv.org/abs/2501.03936)
- ## More documentation
- - [pptx-nova user guide](pptx-nova/README.md)
- - [pptx-nova 中文使用指南](pptx-nova/README.zh-CN.md)
- - [xdoc introduction and architecture](docs/xdoc-introducution.md)
- - [Install the xdoc CLI](docs/xdoc-installation.md)
- - [xdoc compatibility reference](docs/xdoc-compatibility.md)
- - [DeckKit preview gallery](https://structurify.io/en/deckkits/)
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.