chuspeeism/dashi-ppt-skill

Worth a try if you regularly turn research notes or reports into a presentable deck and want the generated pages to stay editable rather than becoming a frozen image or a rough draft you redo by hand. Be prepared for a local Node setup and a fixed, curated design system.

The problem

You have a document — an industry study, a project report, a pitch outline — and need a deck with a consistent look in a few hours. The usual path is to hand the text to an AI assistant, get an outline, then rebuild slides one by one in presentation software. The step that changes here is the middle one: the agent drafts pages directly on top of a layout library, and the result is a webpage deck that is itself an editor. You open it, adjust text, images and module counts in the browser, then export a PPTX or PDF when it looks right.

What's different

Rather than generating free-form HTML per request, the skill pairs content fields with prebuilt layouts drawn from 12 visual themes and 1,020 page layouts, covering things like waterfall charts, funnels, heat maps, SWOT and Porter's five forces. Because each page is a layout plus a text payload, the agent can read and revise it deterministically, and the browser console exposes sliders, toggles and dropdowns for module count, layout, chart type and palette. The README's own framing is that editing after generation matters more than generation, and the console is where that bet is placed.

The export path deserves attention for the opposite reason: PPTX can't carry the full range of what HTML does, and the author says the exporter preserves editability "as far as possible" rather than promising parity. A page-by-page HTML versus PPTX comparison is provided so you can judge the gap yourself. The README also states customization is deliberately bounded — stable output over free color picking — so if you need a bespoke visual identity, this will chafe. The PPTX export engine is a separate proprietary subpackage, not covered by the AGPL-3.0 core, which matters if you plan to build on it.

Who should try it

Good fit: analysts, consultants and internal teams who produce structured decks from documents — competitor analysis, trend reports, project reviews, roadshow material — and who value a coherent theme and fast revision over pixel-level control. It also suits people already working inside a supported agent such as Claude Code or Codex, since the skill plugs into the agent's file and shell access.

Poor fit: designers needing hand-tuned visuals per slide (the README says so directly), and anyone who only has a web chatbot. The platform table marks ordinary web chatbots as not recommended because the generator needs a local Node.js environment; agents that can read/write files and run shell commands are the workable class, with the skill file placed anywhere readable as SKILL.md for tools like Marvis or Workbuddy.

Requirements and limitations

Node.js 20+ and npm are required, and PPTX or PDF export additionally needs a local Chrome, Chromium or Edge install, configurable via CHROME_PATH. Installation and updates use the same npx command, with a mirror option for networks in mainland China; see the project instructions rather than copying commands from a review.

Ongoing cost is mostly tokens: the README reports roughly 100,000 tokens for a 10-page deck, varying with document length and revision rounds, which works out to about ten decks per Codex five-hour quota by the author's rough estimate. Content stays local according to the README, with network access limited to dependency installation on first generation and a silent version check; the local preview server is reachable on the LAN by default, and the export endpoint is restricted to the local machine. Licensing is AGPL-3.0 with the proprietary exporter carve-out, so distributing a modified version or offering it as a service carries source-disclosure obligations.

HotRepo's take

HotRepo has tracked this repository since 2026-05-10; the only daily-board observation is 2026-10-26, with 10,032 stars and +118 that day, on a then-138-day-old repository. A single dated snapshot cannot establish whether interest is rising, fading or sustained, and it says nothing about whether the layout library keeps pace with real decks. Before committing, open the HTML-versus-PPTX comparison and check that its fidelity on chart-heavy pages meets the decks you actually deliver.