Slide Wright Presentation Builder
Review a two-slide design preview, approve the direction, then build a complete deck for export or web deployment.
- Source repo
- arifszn/slide-wright
- Stars
- ★ 62
- Last updated
- 7d ago
- License
- MIT
- Primary language
- JavaScript
- FA score
- 48/100 · Major gaps
At a glance
- How it runs
- Works with
- Universal · cross-platformCodex · Claude Code
- Setup effort
- Medium · a few setup steps
- You'll need
- Typical use
- A startup team preparing a quarterly board update can turn a topic or rough notes into a deck after reviewing its initial design.
- Not a fit if
- Teams that need to edit slide charts, shapes, and images individually in PowerPoint
- Source review
- 48/100 · Major gaps 1 safety controls not found
What does this agent do, and when should you use it?
Slide Wright is a standalone skill for coding agents that support the SKILL.md format, and it is also available through the Claude Code plugin marketplace. Give it a topic, notes, or an outline; it creates a theme with a color palette and typography, then opens a two-slide preview for review. After approval, it builds the full presentation as a self-contained HTML file displayed with Reveal.js. The deck can be exported to PDF or PowerPoint, or deployed through Surge, Vercel, Netlify, or another static host. In PowerPoint exports, text remains editable and includes speaker notes, while shapes, charts, and images are baked into slide backgrounds.
Invoke /slide-wright with a topic, rough notes, or an outline. The skill creates a theme and two-slide preview; users can request a different direction and review another preview before approving the full deck. It then produces a self-contained HTML presentation. Users can ask the agent to export PDF or PowerPoint, or run node slide-wright/scripts/export-pptx.mjs deck.html themselves; that script needs Node 18+ and Chrome, and installs dependencies on first run. For web sharing, users can ask the agent to deploy through Surge, Vercel, or Netlify, or place index.html on a static host.
- A startup team preparing a quarterly board update can turn a topic or rough notes into a deck after reviewing its initial design.
- A marketer building a customer or product presentation can request a visual direction, such as a yellow theme, before generating the full deck.
- A consultant turning meeting or research notes into slides can iterate on both content and design before approval.
- A technical speaker with a prepared outline can submit it, inspect the two-slide preview, and then generate a complete presentation.
- A team sharing a presentation by link can deploy the self-contained HTML file to a static hosting service.
How do you install or deploy this agent?
For Claude Code, add the marketplace and install the plugin:
/plugin marketplace add arifszn/slide-wright
/plugin install slide-wrightFor other agents that support SKILL.md, install with npx:
npx skills add arifszn/slide-wrightThe repository also provides INSTALL.md with per-agent skill paths. The README does not specify API keys or service credentials. Manually running the PowerPoint export script requires Node 18+ and Chrome.
How do you use this agent?
After installation, invoke the skill with a topic:
/slide-wright Make me a slide deck about <your topic>It creates a theme and a two-slide preview first; approve the direction to generate the complete deck. To export PowerPoint, ask the agent or run:
node slide-wright/scripts/export-pptx.mjs deck.htmlFor PDF, ask the agent to guide the export or add ?print-pdf to the deck URL, then use the browser print dialog and save as PDF. For deployment, ask the agent to use Surge, Vercel, or Netlify. For manual deployment, place the deck in an empty folder as index.html and push it to a static host.
What are this agent's strengths and limitations?
- Shows a two-slide preview and waits for approval, so users can change the design direction before the full deck is built.
- Accepts a topic, rough notes, or a full outline, accommodating different levels of prepared content.
- Produces a single self-contained HTML file and documents PDF, PowerPoint, and static-host deployment paths.
- PowerPoint exports retain editable text boxes and speaker notes.
- Shapes, charts, and images in PowerPoint exports are baked into slide backgrounds and cannot be edited individually.
- Fonts are not embedded in PowerPoint files, so another machine may substitute similar fonts.
- Manual PowerPoint export requires Node 18+ and Chrome; manual web deployment assumes the user has a static host.
- The README does not specify model costs, required API keys, or data handling.
How does this agent compare with similar options?
Key facts side by side with the most closely related agents.
| Agent | Source review | Form / cost | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|---|
| Slide Wright Presentation Builder This agent | 48 · Major gaps | Agent plugin / skill | ★ 62 | 7d ago | JavaScript | Codex · Claude Code |
| Dashi PPT Skill — AI-Powered Presentation Generator | 41 · Major gaps | CLIFree + model costs | ★ 9.8k | 1mo ago | JavaScript | Codex · Claude Code |
| Frontend Slides — Web Slide Generation Skill | 46 · Major gaps | Agent plugin / skillFree | ★ 31k | 4mo ago | JavaScript | Claude Code |
| Guizang PPT Skill | 40 · Major gaps | Agent plugin / skillFree + model costs | ★ 28k | 2mo ago | HTML | Codex · Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
README shows a preview-approve-build flow, so user confirmation exists (user_confirmation=2). Deployment to Surge/Vercel/Netlify introduces third-party logins and public publishing, but data flow is only one sentence with no detail on what is sent, credential handling, or CDN font/engine requests (data_flow_transparency=1). Least privilege is undefined: exporter needs Node 18+ and Chrome, deployment needs third-party login, and scope is not bounded (least_privilege=1). Sensitive data (decks may contain confidential material) has no handling policy (sensitive_data_handling=0). Dependency security only notes pptxgenjs/playwright-core installed on first run, with no pinning or audit (dependency_security=1). External effects (public URL) are mentioned but no takedown/removal guidance (external_effects=1). Rollback is only implicit via regenerating a preview, no versioning or undo (rollback=1). Source attribution has MIT and author, but no third-party asset/font licensing notes (source_attribution=1).
README, package.json, and CI workflow are consistent (no build step, exporter self-installs deps), so self-consistency is decent (self_consistency=2). Dependency availability relies on CDN and first-run network install; offline or CDN failure behavior is undocumented (dependency_availability=1). Failure messages have no examples; CI only notes render tests skip (failure_messages=1).
Targets multiple SKILL.md agents (Claude Code, Codex, Gemini, Cursor, etc.) and accepts topic/outline/notes input (audience_and_scenarios=2). Capability boundaries are clear: PPTX shapes/charts/images are non-editable, fonts not embedded, PDF for exact typography (capability_boundaries=2). Trigger precision explains naming the skill avoids built-in slide builders (trigger_precision=2). Environment fit lists Node 18+, Chrome, and per-agent install paths (environment_fit=2).
README is well structured with install, usage, shortcuts, export, deploy, license (information_architecture=2). Install notes cover plugin marketplace, npx, and INSTALL.md pointer (install_notes=2). Naming is stable as slide-wright (naming_stability=2). Examples are rich with three screenshot sets and prompts (examples_and_faq=2). Known limitations explicitly list PPTX editability and font issues (known_limitations=2). MIT license is complete (license=3). No version number or changelog (versioning_changelog=0). Maintenance responsibility is only author attribution, no governance or contact (maintenance_responsibility=1).
Output is self-contained HTML, exportable to PPTX/PDF, deployable, so usability is good (output_usability=2). Compared to raw agent slide generation, theme preview and multi-format export add marginal value (marginal_value=2). Cost requires Chrome, Node, first-run network install, and third-party deploy login; cost-benefit is only partly addressed (cost_benefit=1).
README claims partially map to package.json and CI workflow (claim_traceability=1). Cross-source corroboration is limited to README, LICENSE, package.json, and CI (cross_source_corroboration=1). Fact/inference separation is moderate; screenshot examples cannot be statically verified (fact_inference_separation=1).
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Deploying to Surge/Vercel/Netlify publishes deck content publicly and involves third-party logins; the docs do not describe what is sent or how credentials are handled, so confidential decks need caution.
- The exporter installs pptxgenjs, playwright-core, and other deps on first run without version pinning, creating supply-chain risk.
- Decks may contain confidential enterprise material, and the repo provides no sensitive-data handling or retention policy.
- No version number or changelog makes updates and regressions hard to track.
- No takedown/removal guidance after public deployment, and rollback is weak.
FAQ
Can I review the design before the full deck is generated?
Which parts of a PowerPoint export can I edit?
Are fonts embedded in PowerPoint exports?
What services or credentials are needed to deploy?
index.html file.