Generate Browser-Editable Decks and Export Real PPTX With Dashi PPT

Most agent-generated decks are a one-shot render: the moment you want one fewer bullet on slide 7, you are back to prompting. Dashi PPT is a 10k-star skill built, in the README's words, for people who actually present at work — hand a document to your agent and get back a deck where every page carries its own editing console, fix what you dislike in the browser, then export a real, editable PPTX with one click.

Why This Skill Matters

The README's headline numbers are 12 visual themes, 1,020 layout pages, and 8,576 tunable controls. Each theme has its own page structures and visual language across 20 page roles, including cover, table of contents, metrics, trends, comparison, flow, risks, and ending. Charts and analysis frameworks ship as ready-made layouts — radar, waterfall, treemap, funnel, heatmap, Sankey, Gantt, plus SWOT, Porter's Five Forces, PEST, Business Model Canvas, Double Diamond, and more.

The part the README itself calls more important than generation is what happens after: every page has a console with sliders, toggles, and dropdowns to switch layouts, tune module counts, change palettes, and shift the page's emphasis. Any text is click-to-edit in place; media slots fill by click or drag, and text-only source material automatically reserves image placeholders. Output is an offline HTML bundle, a PDF, or a PPTX reconstructed node by node with text still editable. The README's framing is that the output is the editor: a web-based deck that is ready the moment it opens.

Installation

One command installs or updates. It detects common skills directories, installs into every one it finds, and keeps already-installed dependencies:

npx dashi-ppt-skill@latest

Use --dir <path> to target a specific skills directory, such as --dir ~/.claude/skills; re-running the same command updates in place. Requirements are Node.js 20 or later and npm; exporting PPTX or PDF additionally needs Chrome, Chromium, or Edge installed locally. The README's platform table — which it describes as platforms actually tested, not an exhaustive list — marks Claude Code and Codex as supported, notes that Codex can call image generation to fill visuals, lists Doubao as supported with office mode, and marks Cursor and other local agents as usable when they can read and write files and run shell commands. Plain web chatbots are not recommended because the generator needs a local Node.js environment.

Real Workflow: Turn a Quarterly Review Into a Deck

Describe the ask the way the README's first step lists it — topic, audience, page count, the conclusions to highlight:

用 dashi-ppt 把这份季度复盘文档做成一份 10 页左右的汇报 PPT，受众是管理层，重点突出营收增长和两个风险点，需要预留图片位。

The documented flow has five steps. You describe the ask; the skill shows previews of the 12 themes for you to pick and confirms whether you need images or video; it structures your content and designs the deck around it; you edit as you go — text, images, module counts, palettes — with every change auto-saving; then you ask the agent to restyle or fine-tune and export the format you need. The skill's own SKILL.md fills in two defaults: when you do not specify a page count it targets about 10 pages and not fewer than 8, and when you do not name a style it asks before generating.

The render step starts a local preview server and reports a http://127.0.0.1:<port>/ address. Edit there — the SKILL.md is explicit that a static server such as python -m http.server cannot replace it, because the export and auto-save endpoints live in the preview service, and a page opened over file:// does not auto-save. When the deck is right, export with one click, or skip the HTML stage entirely by telling the agent to produce a PPT file directly; the README also documents a command-line path:

npm --prefix <project-dir> run export:pptx -- <deck-output-dir>/ppt out.pptx

Tips

• Drag the sliders on the right-hand console to add or remove modules on a page; the README documents 20-plus dimensions of editing room covering content, layout, module counts, page emphasis, preset palettes, and transitions, with 9 transition styles.
• The thumbnail rail on the left supports drag-to-reorder, and pages can be skipped, deleted, or duplicated; the top bar has one-click presentation mode, light/dark switching, and reset-all.
• Budget tokens: the FAQ measures a 10-page deck at around 100k tokens, varying with document length and editing rounds — roughly 10 decks per Codex 5-hour quota window.
• Content never leaves your machine: generation, editing, and export run locally. The two network touches are npm dependency installation on first generation and a silent version check that fetches only the latest version number. The preview server is reachable on your LAN for viewing only; export endpoints are local-only.
• If PPTX export fails, point CHROME_PATH at a local Chrome, Chromium, or Edge binary.

When Not to Use This

The README names the boundary: it is not a fit for pixel-by-pixel hand-crafted visual design, and custom styling is intentionally limited to a defined range because stable output matters more than free-form color picking. Check the license before building a product on it — the project is AGPL-3.0, and the export engine subpackage project/packages/html-deck-to-pptx is a proprietary component licensed only as an integrated part of the skill, so it cannot be extracted or redistributed separately. And if your deck is three slides of plain text, a 1,020-layout pipeline with a console on every page is more machinery than the job needs.

See the leaderboard for more skills.