Design & Frontend presentation-generatorhtml-to-pptxslide-deckscodexagent-skillvisual-themesbrowser-editing

Dashi PPT Skill — AI-Powered Presentation Generator

Turn documents into browser-editable slide decks with 12 themes and one-click PPTX export.

FollowAgents review · FARS-2.1
Not recommended
41/ 100 5-point scale 2.1 / 5
1 2 3 4 5 6
1Trust7 / 29 · 1.2/5

Evidence: README claims zero content upload, all generation, editing, and export run locally, with only npm dependency installation and a silent version check touching the network, and the local preview server is LAN-only for viewing, export endpoints local-only. This shows data flow transparency, but lacks user confirmation mechanisms (e.g., explicit prompts before install or export), and no specific least-privilege details (e.g., required file system access scope). Dependency security lacks a dependency list or security audit info. External effects (network requests) are described but no user control options. Rollback mechanism not mentioned. Source attribution via copyright and GitHub link, but publisher unverified. Thus, data_flow_transparency scores 2, others 0-1 due to insufficient evidence.

2Reliability6 / 14 · 2.1/5

Evidence: README is consistent in feature descriptions, no contradictions found, but no tests or verification results provided. Dependency availability requires Node.js 20+ and Chrome, but no dependency list or version pinning. Failure messages only mention PPTX export failure requiring local Chrome, but no detailed error handling or user guidance. Thus, self_consistency scores 2, dependency_availability and failure_messages each 1.

3Adaptability10 / 18 · 2.8/5

Evidence: README clearly defines suitable scenarios (industry research, funding reviews, etc.) and non-fit (pixel-perfect hand-crafted design), and lists supported platforms (Claude Code, Codex, etc.) with requirements (Node.js, Chrome). Capability boundaries clear, but trigger precision lacks specific trigger words or command examples beyond install command. Environment fit requires Node.js 20+ and Chrome, but no other environment variables or config. Thus, audience_and_scenarios, capability_boundaries, environment_fit each 2, trigger_precision 1.

4Convention9 / 18 · 2.5/5

Evidence: README has clear structure with install, usage, FAQ, license sections, good information architecture. Install notes detailed with command and parameters. Naming stability not mentioned (no version naming rules or API stability). Examples and FAQ provide usage examples and common questions. Known limitations clearly state non-fit scenarios and customization limits. License is AGPL-3.0 with proprietary component exception, note. Versioning changelog not provided. Maintenance responsibility: copyright to author, but no maintenance commitment or contribution guide. Thus, information_architecture, install_notes, examples_and_faq, known_limitations, license each 2, naming_stability and maintenance_responsibility each 1, versioning_changelog 0.

5Effectiveness7 / 13 · 2.7/5

Evidence: Output usability: README claims editable HTML and PPTX with export, but no actual output samples or user reviews. Marginal value: provides 12 themes, 1020 layouts, 8576 tunable controls, feature-rich, but no comparison with other tools. Cost-benefit: mentions ~100k tokens for 10 pages, but no detailed cost analysis or comparison. Thus, output_usability and marginal_value each 2, cost_benefit 1.

6Verifiability2 / 8 · 1.3/5

Evidence: Claims (e.g., theme count, layout count) lack verifiable tests or data sources, only images. Cross-source corroboration: no third-party verification or independent testing. Fact-inference separation: README distinguishes feature descriptions and suitable scenarios, but does not explicitly separate facts from inferences. Thus, claim_traceability 1, cross_source_corroboration 0, fact_inference_separation 1.

Evidence confidence: Low Reviewed Aug 11, 2026 Reviewed revision 7cb23347f91c
Safety controls not found in source: confirmation before acting, dependency security, rollback or recovery path
Before you use it
  • Publisher unverified, identity unknown, proceed with caution.
  • Dependency security lacks list or audit, check dependencies before install.
  • Proprietary component exception exists, confirm license terms before use.
  • No tests or verification results provided, claims need independent verification.
Review evidence [1][2]
See the full review method →

What does this agent do, and when should you use it?

Dashi PPT Skill is an AI agent skill that enables coding agents like Claude Code and Codex to generate professional, structure-complete presentations from a user's document. It includes 12 visual themes, 1020 layout variants, and 8576 configurable components. The output is an HTML-based deck that opens as a web editor: users can edit text in place, replace media by drag-and-drop, and adjust layouts via an on-page control panel. The deck can be exported as a self-contained HTML file, PDF, or an editable PPTX file. Everything runs locally with Node.js; content is never uploaded to a server.

The skill instructs the agent (via SKILL.md) to consume a user document, infer the presentation scope, and propose a structured outline with a chosen theme from 12 options. The agent then generates an HTML deck where each slide is composed of reusable layouts plus content fields. The generated HTML includes a control console (sliders, switches, dropdowns) for adjusting module counts, layout, and color palette, plus click-to-edit text and media slots. For export, the skill provides an npm-based tool that converts the HTML to PPTX/PDF (requires local Chrome/Chromium/Edge). Installation is done via npx dashi-ppt-skill@latest.

  1. A market researcher needs a quick industry report deck — feed the agent a research note, get a themed output with relevant charts.
  2. A startup founder prepares investor pitch materials — use the 12 themes to create visually consistent slides for a fundraising review.
  3. A product manager performs a competitive analysis — the agent can generate SWOT, Porter's Five Forces, and other analysis models.
  4. An internal trainer creates course slides — the browser editor lets them tweak details and export an editable PPTX for further changes.
  5. A project lead puts together a status report — the control panel adjusts the number of module cards to fit the speaking time.

What are this agent's strengths and limitations?

Pros
  • Comes with 12 professional themes and 1020 layout variations spanning charts, analysis models, and common content pages.
  • Output is a live web editor with an intuitive control console, enabling non-technical users to tweak without code.
  • One-click export to editable PPTX (with Chrome/Edge) fills the gap between HTML presentations and office tools.
  • Works with mainstream coding agents like Claude Code and Codex, and installation is a single npm command.
Limitations
  • PPTX/PDF export depends on a local Chrome/Chromium/Edge install; Node.js 20+ is required throughout.
  • Styling customization is deliberately limited to keep output consistent, which may frustrate users needing pixel-perfect design.
  • The export engine (html-deck-to-pptx) is proprietary and cannot be extracted for independent use, creating a legal constraint.
  • Interactive refinement loops can consume significant tokens (roughly 100k per 10-slide deck), impacting cost for heavy users.

How do you install or deploy this agent?

  1. Ensure Node.js 20+ and npm are installed.\n2. Run: npx dashi-ppt-skill@latest (for China network: npx --registry=https://registry.npmmirror.com dashi-ppt-skill@latest).\n3. The same command updates the skill in place.

How do you use this agent?

  1. After installation, provide a document to a supported agent (Claude Code, Codex) and specify topic, audience, page count, and key messages.\n2. The agent will show previews of the 12 themes for you to choose, then generate the deck.\n3. Open the generated HTML in a browser to edit text, replace images, or adjust layout via the console.\n4. Once satisfied, ask the agent to export to HTML, PDF, or editable PPTX.

FAQ

How many tokens does generating a deck consume?
A 10-slide deck uses approximately 100k tokens, depending on document length and revision rounds.
Is my content safe? Does it require internet?
Content stays local — generation, editing, and export happen on your machine. Internet is only used for installing dependencies and silent version checks.
Can it export an editable PPTX?
Yes, but a local Chrome/Chromium/Edge is required for the export process.
Can I use this with a standard web chatbot?
No, the generator requires a local Node.js environment, so it only works with agents that can execute shell commands.

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related agents