deck
/deck
Turn a website, a code project, documents or a brief into a polished, on-brand PowerPoint deck — native and fully editable (real text boxes, shapes, editable charts and tables, speaker notes), plus a PDF and an HTML version, checked in a real office renderer. Use when someone asks for a deck, slides, a presentation, a pitch deck, a sales deck, a PowerPoint/.pptx, investor slides, a client presentation, or says "/deck", "make slides from this site/repo/doc", "turn this into a presentation".
- Author
- MBGrao ↗
- Repository
- deck-skill ↗
- Licence
- MIT
- Last repository change
- 05.11.2026
Assessment and security
- Files in this package
- 28
- Scripts
- 11
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 11 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: assets/deck.js, scripts/deck2video.mjs, scripts/fonts.mjs, scripts/html2pptx.mjs, scripts/inspect.mjs, scripts/lib/chrome.mjs, scripts/lib/inpage.js, scripts/new.mjs, scripts/qa.mjs, tests/fixture/deck.js, tests/run.mjs
What it does and when to use it
Turn a website, a code project, documents or a brief into a polished, on-brand PowerPoint deck — native and fully editable (real text boxes, shapes, editable charts and tables, speaker notes), plus a PDF and an HTML version, checked in a real office renderer. Use when someone asks for a deck, slides, a presentation, a pitch deck, a sales deck, a PowerPoint/.pptx, investor slides, a client presentation, or says "/deck", "make slides from this site/repo/doc", "turn this into a presentation".
Triggers from the description
Original author description
Turn a website, a code project, documents or a brief into a polished, on-brand PowerPoint deck — native and fully editable (real text boxes, shapes, editable charts and tables, speaker notes), plus a PDF and an HTML version, checked in a real office renderer. Use when someone asks for a deck, slides, a presentation, a pitch deck, a sales deck, a PowerPoint/.pptx, investor slides, a client presentation, or says "/deck", "make slides from this site/repo/doc", "turn this into a presentation".
How it works
- 0. Setup (once per machine, ~30 s)
- 1. Inspect — gather real material
- 2. Brand
- 3. Plan the story
- 4. Design in HTML
- 5. Export + lint
- 6. Office check (the step image-based tools skip)
- 7. Deliver
- Quality bar
SKILL.md preview
---
name: deck
description: Turn a website, a code project, documents or a brief into a polished, on-brand PowerPoint deck — native and fully editable (real text boxes, shapes, editable charts and tables, speaker notes), plus a PDF and an HTML version, checked in a real office renderer. Use when someone asks for a deck, slides, a presentation, a pitch deck, a sales deck, a PowerPoint/.pptx, investor slides, a client presentation, or says "/deck", "make slides from this site/repo/doc", "turn this into a presentation".
---
# /deck
You make the whole deck yourself: read the source, find the story, design every slide in HTML on a strict grid, then export it to a **native, editable .pptx** with this skill's converter and check it. Free, local tools only.
Usage: `/deck [input] [options]` — flags or plain language.
| Option | Default |
|---|---|
| input | URL, project folder (default: current dir), file(s) (md, pdf text, docx text, notes), or a topic + facts |
| `--type` | inferred: `pitch` · `sales` · `launch` · `update` · `case-study` · `training` · `talk` |
| `--slides N` | by type (usually 8–12) |
| `--audience` | inferred from type (investors, buyers, team, students…) |
| `--brand NAME\|FILE` | a remembered brand (`~/.deck/brands/`) or a brand.json; else extracted from the source |
| `--theme light\|dark\|mixed` | mixed (dark cover/section/close, light content) |
| `--transition fade\|morph\|none` | fade |
| `--notes` | full speaker notes (default on) |
Output: `deck-output/` in the current directory (timestamped `deck-output-YYYY-MM-DD-HHmm/` if it exists): `deck.pptx`, `deck.pdf`, `deck.html` (+ css/js/fonts/img), `deck-plan.md`, `facts.md`, `brand.json`, `previews/`, `qa/`. Keep scratch in `deck-output/work/`.
`<skill-dir>` = the folder containing this SKILL.md. Scripts live in `<skill-dir>/scripts/`.
## 0. Setup (once per machine, ~30 s)
```bash
cd <skill-dir>/scripts && [ -d node_modules ] || npm install
```
Needs Node ≥ 18 and any Chrome/Chromium (system Chrome, or `npx playwright install chromium`). The office check needs LibreOffice (free) and optionally poppler for PNG renders — if missing, say so and offer the install command; never skip QA silently.
## 1. Inspect — gather real material
Read [references/inputs.md](references/inputs.md). By input:
- **Website:** `node <skill-dir>/scripts/inspect.mjs <url> --out deck-output/work/site` → read `summary.md`, `text.txt`, `brand-candidates.json`, look at `shots/`.
- **Project folder:** read README, landing page, routes, key components, package metadata, real copy. If it has a UI, run or capture it for screenshots (`inspect.mjs` on a local URL works).
- **Documents / brief:** read them fully; extract claims, numbers, names, structure.
Write `facts.md`: every number, claim and quote you might use, each with its source (URL/file + date). **Never invent** metrics, customers, team, prices, quotes or logos. Missing but needed → `{{placeholder}}` on the slide + flagged in the summary. Never carry secrets, tokens, internal hostnames, personal data or customer names into slides; swap in labelled stand-ins.
Gate: you can state in one sentence what it is, who the deck is for, and what the audience should do after the last slide.
## 2. Brand
Read [references/brand.md](references/brand.md). Check memory first: `ls ~/.deck/brands/`. Otherwise build `brand.json` from the inspection (exact colours, fonts, logo — prefer SVG; voice words; banned words). Fonts must be Google Fonts or system fonts so PowerPoint can show them.
## 3. Plan the story
Read [references/story.md](references/story.md). Write `deck-plan.md`: angle, audience, the arc for the deck type, then one row per slide — **action title** (a full-sentence takeaway), the evidence/visual, layout, speaker-note gist, source. Reading only the titles must tell the whole story. One idea per slide.
## 4. Design in HTML
```bash
node <skill-dir>/scripts/new.mjs deck-output --brand deck-output/brand.json --remember
```
Then write `deck-output/deck.html`. Read [references/design.md](references/design.md) (design system, 20 layout recipes) and [references/conversion.md](references/conversion.md) (what becomes editable vs. a picture). Rules that matter most:
- Canvas 1280×720 per `<section class="slide">`; keep content inside the 80/64 px margins.
- Use the type scale and brand tokens only; weights **400 and 700** (PowerPoint has no 800/900).
- Real visuals: product screenshots in `.browser`/`.phone` frames, the real logo, native charts (`.chart[data-chart]`), real tables. No stock photos, no emoji as icons, no decorative filler.
- Speaker notes in `<aside class="notes">` on every slide; a `.source` line on every slide with a number.
## 5. Export + lint
```bash
node <skill-dir>/scripts/html2pptx.mjs deck-output/deck.html --out-dir deck-output --name deck
```
Fix every ✗ error and every ⚠ warning it prints (overflow, contrast, tiny text, overlaps, generic phrases, unsourced claims). Then **look at `deck-output/qa/contact.png`** and judge each slide like a designer: hierarchy, alignment, spacing, balance, nothing crammed, nothing empty without intent. Re-export after each fix.
## 6. Office check (the step image-based tools skip)
```bash
node <skill-dir>/scripts/qa.mjs deck-output/deck.pptx
```
Renders the .pptx in LibreOffice with the deck's own fonts and compares every text box to the browser layout. Fix any `reflow`/`office-overflow` (shorten, widen, or step the font size down), re-export, re-check. Look at `qa/compare.png` (browser | office) before delivering. Read [references/qa.md](references/qa.md) for fixes.
## 7. Deliver
Tell the user: where `deck.pptx` / `deck.pdf` are, the angle in one sentence, the slide titles in order, anything that needs their input (`{{placeholders}}`, missing facts), the fonts to install for exact type in PowerPoint (`deck-output/fonts/`), and that every text box, chart and table is editable. Offer: another deck type from the same plan, a shorter version, a different theme, or edits by slide number.
Optional extras when asked: a narrated video of the deck (`node <skill-dir>/scripts/deck2video.mjs deck-output` — uses the local Kokoro voice if `DECK_KOKORO_DIR` points to its model files, else macOS `say`/espeak; needs ffmpeg), a light/dark variant, a 1-page PDF summary.
## Quality bar
- **Clear to a stranger:** after slide 2 they know what this is and why it matters to them.
- **Specific:** this deck could only be about this company/project — its own words, numbers, screenshots.
- **Honest:** every number traceable to `facts.md`; no fabricated logos or testimonials.
- **Editable:** text stays text; pictures only where PowerPoint can't draw (gradients, SVG, effects).
- **Consistent:** one grid, one type scale, one accent colour, same position for titles and footers.
Files in this package (28)
- SKILL.md 7 KB
- assets/deck.css 7 KB
- assets/deck.js 9 KB
- references/brand.md 3 KB
- references/conversion.md 3 KB
- references/design.md 8 KB
- references/inputs.md 3 KB
- references/qa.md 3 KB
- references/story.md 4 KB
- scripts/deck2video.mjs 5 KB
- scripts/fonts.mjs 3 KB
- scripts/html2pptx.mjs 21 KB
- scripts/inspect.mjs 13 KB
- scripts/new.mjs 8 KB
- scripts/package-lock.json 15 KB
- scripts/package.json 1 KB
- scripts/qa.mjs 9 KB
- scripts/lib/chrome.mjs 3 KB
- scripts/lib/inpage.js 31 KB
- tests/run.mjs 4 KB
- tests/fixture/deck.css 7 KB
- tests/fixture/deck.html 7 KB
- tests/fixture/deck.js 9 KB
- tests/fixture/fonts.css 1 KB
- tests/fixture/fonts/Inter-400.ttf 317 KB
- tests/fixture/fonts/Inter-700.ttf 319 KB
- tests/fixture/fonts/OFL-Inter.txt 4 KB
- tests/fixture/img/app.png 9 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · MBGrao/deck-skill | 100 | MIT |
| zauberzeug/game-of-cards | 100 | MIT |
| zauberzeug/game-of-cards | 100 | MIT |
| zauberzeug/game-of-cards | 100 | MIT |
| octavehq/lfgtm | 100 | MIT |
| ramonk2o/storymaker | 100 | MIT |
| wookiya1364/scv-claude-code | 100 | MIT |
| roaldnefs/deckfile | 100 | MIT |
| prmvanschie/deck-skill | 100 | MIT |
Database snapshot: 13.11.2026 · package version d26d4b21afae (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100kinsy
Create a finished, editable PowerPoint (.pptx) deck from a brief, notes or documents with the Kinsy CLI. Use when the user asks for slides, a deck, a presentation, a pitch, a lecture or a board update; it returns a .pptx that opens in PowerPoint as designed, plus a web link to… - 87html-first-deck
Build a polished, on-brand PowerPoint deck the reliable way: PROTOTYPE the design in HTML/CSS first (fast to iterate on layout, hierarchy, spacing, color), then generate a NATIVE, fully EDITABLE .pptx with python-pptx (real text boxes, shapes, and tables — NOT slide images and… - 100deck-pptx
Build an editable PowerPoint (.pptx) presentation from a topic or an outline. Use it when the user asks for a deck, slides or a presentation and wants a .pptx file they can open and edit. - 100brief-to-slides
Builds a visual, editable PowerPoint (.pptx) deck with speaker-ready notes, exact timing, citations and a layout-checked design from a topic, an audience and a length, using only the user's own material (strict mode) or adding web research (extended mode). Use when the user asks… - 100slide-deck-from-doc
Convert any document (DOCX, PDF, or Markdown) into a professional PowerPoint presentation with smart layout selection and visual hierarchy. Use when asked to 'turn this into slides', 'make a deck from this doc', 'convert to presentation', 'document to powerpoint', 'create slides… - 100ppt-master
PPT Master turns a PDF, Word file, web page or pasted text into a natively editable PowerPoint (.pptx) deck, with real shapes, slide masters, optional animations and speaker-note narration, by running a workflow inside a coding agent. Use when someone says "make a PPT from this…