Skip to content
Back to search

deck-builder

MarketplaceWorks with Claude CodeGitHub

The deck-builder skill for Claude Code: editable PowerPoint decks that pass measured checks.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/coffeedroplabs--deck-builder/badge.svg)](/listings/coffeedroplabs--deck-builder)

HTML

<a href="/listings/coffeedroplabs--deck-builder"><img src="/api/listings/coffeedroplabs--deck-builder/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code:

/plugin marketplace add coffeedroplabs/deck-builder
/plugin install deck-builder@deck-builder

Or clone it into your personal skills folder:

git clone https://github.com/coffeedroplabs/deck-builder ~/.claude/skills/deck-builder

Use one or the other, then start a new Claude Code session.

Requirements

| Needs | Why | |---|---| | [uv](https://docs.astral.sh/uv/getting-started/installation/) | Runs every script with its pinned dependencies (python-pptx, Pillow). Nothing is installed globally, and uv fetches Python 3.11 or newer if you do not have it. | | Linux, macOS or WSL | Native Windows is not supported yet: the render lock uses `fcntl`. | | PowerPoint on Windows, reached from WSL | For measured fit, the heart of the skill. Without it, renders fall back to LibreOffice (`soffice` and `pdftoppm`), which draws the slides but cannot measure them, so overflow is predicted from font metrics and the lint says so. PowerPoint for Mac is not driven. The LibreOffice path is untested. | | Fonts, on Linux and WSL | Liberation, Carlito and Caladea, the metric-compatible stand-ins for Arial, Calibri and Cambria that the builder measures with. |

On Linux and WSL, install the fonts with:

sudo apt-get install fontconfig fonts-liberation fonts-dejavu-core \
  fonts-crosextra-carlito fonts-crosextra-caladea

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 17 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "deck-builder",
  4. "description": "The deck-builder skill for Claude Code: editable PowerPoint decks that pass measured checks.",
  5. "owner": {
  6. "name": "CoffeeDrop Labs"
  7. },
  8. "plugins": [
  9. {
  10. "name": "deck-builder",
  11. "source": "./",
  12. "description": "Build editable PowerPoint decks that pass measured checks.",
  13. "category": "productivity",
  14. "tags": ["powerpoint", "pptx", "presentations", "slides"]
  15. }
  16. ]
  17. }
README.md · README · 271 lines
  1. <div align="center">
  2. # deck-builder
  3. **PowerPoint decks from Claude that pass measured checks, not an eyeball.**
  4. A [Claude Code](https://code.claude.com/docs/en/overview) skill that turns your notes and data into editable .pptx decks:
  5. a story you can follow from the titles alone, text measured to fit in PowerPoint, font floors, contrast,
  6. alt text and sourced numbers, in a clean default theme or your company's own template.
  7. [![CI](https://github.com/coffeedroplabs/deck-builder/actions/workflows/ci.yml/badge.svg)](https://github.com/coffeedroplabs/deck-builder/actions/workflows/ci.yml)
  8. [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
  9. [![Claude Code plugin](https://img.shields.io/badge/Claude%20Code-plugin-D97757.svg)](#install)
  10. [![Python 3.11+](https://img.shields.io/badge/python-3.11%2B-3776AB.svg)](#requirements)
  11. <img src="docs/hero.png" alt="Six slides built by deck-builder. Top row, in the default theme: a line chart of response times against a 4-hour target, a column chart of order-tracking tickets and the closing ask. Bottom row, in a company template: a pitch's problem slide, a results table and the closing ask." width="100%">
  12. <sub>Top: a support review in the default theme. Bottom: a sales pitch built inside a company's .potx template.<br>
  13. Every slide is native PowerPoint: editable text, real charts with their data, no pictures of text.</sub>
  14. </div>
  15. ## Why
  16. Ask a model for slides and it writes the XML, guesses where the text fits and tells you the deck looks
  17. great. It cannot see the deck. Text runs out of its box, labels collide, titles name a topic instead of
  18. making a point, the template's logo vanishes under a chart, and a round "40% faster" turns up that is
  19. nowhere in your material.
  20. deck-builder takes the guessing out. Claude writes a JSON spec, a deterministic builder lays it out from
  21. locked layouts, PowerPoint itself measures every text box, and a lint writes the verdict to
  22. `gate_result.json`. Claude is told not to call a deck finished unless that file says it passed.
  23. ## What you get
  24. - **The story first.** Before a single slide is built you see the *ghost deck*: the titles alone, in
  25. order. Each one is a claim ("Customer satisfaction fell from 91% to 79%"), not a topic ("Customer
  26. satisfaction"). You approve or change it in chat.
  27. - **Text that really fits.** Every text box is laid out and measured by PowerPoint. The builder refuses
  28. a slide rather than shrink type below the floor or let it overflow, and names the slide and field to fix.
  29. - **Three profiles.** `live` for a room or a call (18 pt floor, at most 4 bullets, speaker notes on
  30. every content slide), `pitch` for presented-then-sent (16 pt floor) and `read-ahead` for decks read
  31. alone (more detail, a source line on every data slide).
  32. - **Native, editable output.** Real PowerPoint charts with their data embedded (bar, column, stacked,
  33. line, pie, waterfall, scatter), real tables and the real title placeholder. No SmartArt, effects or
  34. embedded fonts, the things that cause repair prompts.
  35. - **Your template, kept intact.** Give it a .pptx or .potx. It reads the layouts, maps each slide type
  36. to one, and the lint fails any slide whose content covers the template's logo or artwork.
  37. - **Numbers you can stand behind.** Charts, tables and quantities carry a source line, and Claude is
  38. told never to invent, round or estimate a figure.
  39. - **Accessibility built in.** WCAG 2.2 contrast (4.5:1 for text, 3:1 for chart marks), alt text on
  40. every picture, chart and table, and a font floor for each profile.
  41. - **An independent review.** Once the gate passes, a blind reader who sees only the slide pictures and
  42. three critics look for what scripts cannot: a chart that does not show what its title claims, a
  43. number that does not match its source, a deck that reads as generic.
  44. ## Install
  45. In Claude Code:
  46. ```
  47. /plugin marketplace add coffeedroplabs/deck-builder
  48. /plugin install deck-builder@deck-builder
  49. ```
  50. Or clone it into your personal skills folder:
  51. ```bash
  52. git clone https://github.com/coffeedroplabs/deck-builder ~/.claude/skills/deck-builder
  53. ```
  54. Use one or the other, then start a new Claude Code session.
  55. ### Requirements
  56. | Needs | Why |
  57. |---|---|
  58. | [uv](https://docs.astral.sh/uv/getting-started/installation/) | Runs every script with its pinned dependencies (python-pptx, Pillow). Nothing is installed globally, and uv fetches Python 3.11 or newer if you do not have it. |
  59. | Linux, macOS or WSL | Native Windows is not supported yet: the render lock uses `fcntl`. |
  60. | PowerPoint on Windows, reached from WSL | For measured fit, the heart of the skill. Without it, renders fall back to LibreOffice (`soffice` and `pdftoppm`), which draws the slides but cannot measure them, so overflow is predicted from font metrics and the lint says so. PowerPoint for Mac is not driven. The LibreOffice path is untested. |
  61. | Fonts, on Linux and WSL | Liberation, Carlito and Caladea, the metric-compatible stand-ins for Arial, Calibri and Cambria that the builder measures with. |
  62. On Linux and WSL, install the fonts with:
  63. ```bash
  64. sudo apt-get install fontconfig fonts-liberation fonts-dejavu-core \
  65. fonts-crosextra-carlito fonts-crosextra-caladea
  66. ```
  67. ## Use it
  68. Just ask. The skill picks up any request for slides, a deck or a .pptx:
  69. > I've got 15 minutes at Thursday's ops meeting to present the Q3 support review and ask for two more
  70. > agents. It'll be on the big screen. Can you make the slides from my notes and the Zendesk export?
  71. > Make the H1 board pack from the memo and the financials. The board reads it on their own a week
  72. > before the meeting.
  73. > Turn my pitch notes into a deck in our company template (fernhill.potx). We present it on their
  74. > screen and then send it to them afterwards.
  75. Claude asks only for what it cannot find in your files (the audience, the ask, how the deck will be
  76. used), shows you the ghost deck, and builds once you approve it. You get the .pptx, a contact sheet
  77. of every slide, the gate result with any warnings it kept and why, and what the review changed.
  78. ## How it works
  79. 1. **Brief.** Profile, audience and the ask, material, template and length, written to `brief.md`.
  80. 2. **Outline and your yes.** Titles only, in `outline.json`. `check_story.py` checks them and prints
  81. the ghost deck for you to approve.
  82. 3. **Spec.** `deck.json` gives each slide a layout (statement, bullets, two-column, chart, table,
  83. image, big-number, quote, process or conclusion) and its content. Never coordinates.
  84. 4. **Build.** `build_deck.py` fits every text at the profile's sizes and writes the .pptx, or refuses
  85. and names the slide, field and reason.
  86. 5. **Render and measure.** `render.py` opens the deck in PowerPoint, read-only and without a window,
  87. exports every slide and measures each text box's real bounds and line count. It never touches the
  88. decks you have open.
  89. 6. **Lint.** `lint_deck.py` checks measured overflow, overlap, the safe area, font floors, contrast,
  90. alt text, leftover placeholder text, filler words, em dashes and the story, then writes
  91. `gate_result.json`.
  92. 7. **Review.** A blind reader, then three critics, never more than three agents at a time.
  93. 8. **Fix ladder.** Cut words, move detail to the notes or an appendix, split the slide, change the
  94. layout. Never shrink the text, never edit the .pptx by hand. Then back to step 4.
  95. Here is the ghost deck `check_story.py` printed for the support review above, with no warnings. Read
  96. only the titles; they carry the whole argument:
  97. | # | Layout | Title |
  98. |--:|---|---|
  99. | 1 | cover | Support is missing its 4-hour SLA and needs two more agents in Q4 |
  100. | 2 | chart | Monthly tickets rose from 1,820 in January to 2,840 in September |
  101. | 3 | chart | Where-is-my-order tickets grew from 18% to 41% of volume between January and September |
  102. | 4 | chart | First response has missed the 4-hour SLA every month since April |
  103. | 5 | chart | Customer satisfaction fell from 91% to 79% between January and September |
  104. | 6 | chart | Customers waiting over 24 hours for a first reply churn at double the 90-day rate |
  105. | 7 | two&#8209;column | Macros and a weekend rota helped but did not fix weekday backlogs |
  106. | 8 | table | We recommend hiring over a three-month chatbot build or per-ticket outsourcing |
  107. | 9 | conclusion | Approve two agents for Q4 and ask ops to push the courier on tracking emails |
  108. And the verdict once that deck was built, rendered and linted:
  109. ```
  110. PASSED: 0 error(s), 0 warning(s), text measured in PowerPoint, outline approved.
  111. Verdict: gate_result.json
  112. ```
  113. ### The scripts
  114. They live in `scripts/` and run on their own too. Each prints what to do next, writes a JSON report,
  115. and exits 0 when all is well, 1 for a problem to fix in the spec and 2 for a crash or unreadable input.
  116. | Script | Does |
  117. |---|---|
  118. | `check_story.py` | The story gate, on the titles in `outline.json` alone. `--approve --by` records who approved them |
  119. | `inspect_template.py` | Reads a company template (.potx or .pptx) and suggests how to map its layouts |
  120. | `build_deck.py` | Checks `deck.json`, fits every text and writes the .pptx; refuses rather than shrink or overflow |
  121. | `render.py` | Renders PNGs and a contact sheet, and measures every text box in PowerPoint |
  122. | `lint_deck.py` | The gate: checks the deck against its spec and the measurements, then writes `gate_result.json` |
  123. ```bash
  124. uv run -q scripts/build_deck.py deck.json -o deck.pptx
  125. ```
  126. ### Rules it never trades away
  127. - No invented numbers. Every figure is in your material or carries a source line.
  128. - No text in images, no emoji, no Markdown on slides, no em dashes.
  129. - No "Thank you" or "Questions?" slide. The deck ends on the conclusion and the ask, which stays up
  130. during questions, so it carries the decision, the cost and the date on its own.
  131. - No grids of big-number tiles: they are where made-up round figures hide.
  132. - The gate's verdict is not Claude's to override. If a rule is wrong for your deck, Claude says so
  133. instead of working around it.
  134. ### Where the thresholds come from
  135. Every threshold lives in `scripts/themes.py`, and `references/design-rules.md` grades the evidence
  136. behind each one. The 18 pt floor and the 4-bullet limit are strong (Kosslyn et al. 2012, plus UK ONS
  137. and Microsoft guidance), as is contrast (WCAG 2.2). Direct chart labels and claim titles are moderate:
  138. one study each. The 15-word title limit and the read-ahead sizes are weak, conventions only, so they
  139. are warnings. Popular rules with no evidence behind them, such as 10/20/30 and 6x6, are not used.
  140. ## Results
  141. Three eval cases, each run once with the skill and once without it, with the same model (Claude Opus
  142. 5.5), prompt and files. Each case has 10 checks: the deck opens in PowerPoint, nothing overflows when
  143. PowerPoint lays it out, small text stays in the footer, nothing collides, charts are native, titles
  144. are claims, every number matches the material and carries a source, and the ask is right.
  145. | Case | With deck-builder | Without | What the deck without the skill missed |
  146. |---|:-:|:-:|---|
  147. | Support review, presented live | **10/10** | 8/10 | Text overflowed its boxes in PowerPoint; the closing slide's figures had no source line |
  148. | Board pack, read alone | **10/10** | 9/10 | Two slides with figures had no source line |
  149. | Pitch in a company template | **8/10** | 6/10 | 14 pt text above the footer, two topic titles, unsourced figures, an ask without its price |
  150. | **Mean** | **93%** | **77%** | |
  151. The with-skill pitch failed two checks too: plain counts and dates went without a source, and the
  152. pilot's price was not in the final ask.
  153. The cost is time. Runs with the skill took about 4.3 times as long (302 s against 70 s on average) and
  154. used 1.6 times the tokens (115k against 71k). Part of the time gap is queuing, because the runs
  155. shared one PowerPoint render lock.
  156. Read these numbers with care:
  157. - One run per configuration over three cases is a small sample, not a benchmark.
  158. - Both configurations passed opening in PowerPoint, no collisions, native charts and number accuracy.
  159. Claude is already good at those; the skill earns its keep on measured fit, sources, titles and the ask.
  160. - Three fixes landed after the runs and have not been re-run: the template statement footer, what the
  161. ask must carry, and bar axes starting at zero.
  162. - Scripts graded what they could; the author's own agent graded the rest, not blind.
  163. ## Limitations
  164. - The lint does not catch plain counts and dates without a source ("5 stores for 12 weeks"), only
  165. money, percentages, multipliers, decimals and thousands. The skill tells Claude to source them
  166. anyway, and the eval above shows it does not always.
  167. - Line charts labelled at every point can put labels on the line.
  168. - Slides with little content sit at the top of the body instead of the middle.
  169. - A bullet whose last line is a single word is not flagged.
  170. - `two-column` has no way to highlight the winning side.
  171. - Template mode has no wide layout to map to.
  172. - Chart fills in a light accent colour are not shaded darker.
  173. - Builds spend 3.5 to 5.5 s scanning system fonts.
  174. - Changing any title after approval means approving the ghost deck again.
  175. - Measured fit needs PowerPoint on Windows. Elsewhere you get LibreOffice pictures and predicted fit,
  176. an untested path. Keynote and Google Slides are untested too.
  177. - It builds new decks. To read, extract from or lightly edit a deck someone else made, use
  178. Anthropic's `pptx` skill.
  179. ## Repository layout
  180. ```
  181. SKILL.md the skill: workflow, rules, and when to read each reference
  182. scripts/ story check, template inspector, builder, renderer and lint
  183. references/ spec format, design rules, template mode, review, compatibility
  184. reviewers/ prompts for the blind reader and the critics
  185. evals/ three eval cases in the `claude plugin eval` format
  186. tests/ unit and end-to-end tests
  187. .claude-plugin/ plugin and marketplace manifests
  188. ```
  189. ## Development
  190. With the fonts from [Requirements](#requirements) installed:
  191. ```bash
  192. uv run -q tests/run_tests.py -q # skips the PowerPoint test
  193. DECK_BUILDER_RENDER=1 uv run -q tests/run_tests.py -q # runs it too (WSL with PowerPoint)
  194. uvx ruff@0.15.0 check scripts tests
  195. claude plugin validate . --strict
  196. ```
  197. The eval cases run with `claude plugin eval . --scaffold --allow-tools Bash Write Edit --runs 1`. They
  198. are slow (up to 40 minutes a case), spend your own Claude usage, and need PowerPoint for the measured
  199. checks.
  200. ## Contributing
  201. Issues and pull requests are welcome. A bug report helps most with the `deck.json`, the script's output
  202. and `gate_result.json`. To change a threshold or add a rule, say where it comes from:
  203. `references/design-rules.md` grades every rule by its evidence, and new ones should be graded the same
  204. way. Run the tests, ruff and the plugin validator before opening a pull request.
  205. ## License
  206. [MIT](LICENSE) © CoffeeDrop Labs Pty Ltd.
  207. The eval fixture `evals/template-pitch/files/fernhill.potx` is a template for a fictional company. Its
  208. design is PowerPoint's built-in Facet theme, which belongs to Microsoft and is not covered by this
  209. license.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.