borghei/Claude-Skills / documents/pptx-toolkit
pptx-toolkit
VerifiedAudit PowerPoint (.pptx) decks for slide count, text density, embedded images and fonts, hidden slides, speaker notes, and animation density. Use when reviewing a board deck, sales deck, or conference talk before sending.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.4 KB |
| assets/deck_handoff_checklist.md | markdown | 1.8 KB |
| references/deck_density_rubric.md | markdown | 3.5 KB |
| scripts/pptx_auditor.py | script | 7.8 KB |
references/deck_density_rubric.md
View on GitHub# Deck Density Rubric
Different deck types tolerate different amounts of text per slide. The auditor reports words per slide; this rubric tells you what good looks like for the deck you're holding.
---
## Words-Per-Slide Targets by Deck Purpose
| Deck purpose | Target words/slide | Notes |
|--------------|---------------------|-------|
| Conference talk (live, in person) | 5-15 | Visuals do most of the work; speaker notes carry the script |
| Investor pitch deck (live, sent later) | 15-30 | Has to read on its own when forwarded |
| Board deck (review-then-discuss) | 25-50 | Read offline, discussed live; can be denser |
| Sales deck (live demo accompaniment) | 10-25 | Often forwarded; needs to make sense without you |
| Internal review deck | 30-60 | Nobody is going to listen to a narration; let the deck carry the argument |
| Training material | 40-80 | Designed to read standalone post-session |
If your audit shows words/slide max well above the target for the deck purpose, the slide is doing too much work.
---
## One Idea Per Slide
Test: **can you summarize the slide's argument in one sentence?**
- Yes → keep
- "It shows X *and* Y" → split into two slides
- "It's a financial table" → tables get an exception, but the table should answer one specific question
---
## Speaker Notes Pattern
Treat speaker notes as the **canonical narrative**, the slide as the **visual support**.
For each slide, notes should answer:
1. What is the one thing this slide is for?
2. What's the talk-track in 30 seconds?
3. What's the transition to the next slide?
For board / investor decks specifically: notes are how the deck stays useful when forwarded post-meeting. Decks without notes are 50% lossier on forwarding.
---
## Animations: Less is More
Every animation:
- Adds a place where live presentation can desync
- Adds a place where a remote viewer (Zoom render of slide-as-image) sees the wrong state
- Adds a place where exporting to PDF loses information
Guidance:
- Conference talks: < 1 animation per slide on average. Reveal-by-reveal builds are usually a hint that the slide should be split.
- Investor decks: zero animations. They will break when the VC opens it on a different version of PowerPoint.
- Sales decks: only animations that actively narrate (e.g., revealing a chart bar after stating its number).
A deck-wide animation count over 100 is almost always over-animated.
---
## Hidden Slides
Hidden slides are pre-cut content kept "just in case." Reasons to remove them before sending:
- Outdated narrative, may contain prior pricing or claims
- Confusion if the recipient unhides them
- Bloats file size and audit signal
- If you might need them, save a separate "extended" version
Auditor flag: any hidden slide → review and either ship or remove.
---
## Themes and Brand Compliance
The auditor reports the theme name. Quick check:
- Does the theme match the current brand template?
- For external decks, is it the externally-shippable theme (vs. the internal placeholder)?
- For partner-co-branded decks, is the partner's logo embedded correctly?
If the theme is "Office Theme" or "Default Design", the deck wasn't built from the brand template — fix before sending.
---
## Quick Triage Decision Tree
After running the auditor:
1. Words/slide max > 60 → trim or split
2. Hidden slides > 0 → review and remove or unhide
3. Speaker-notes coverage < 70% on a forwardable deck → add notes
4. Animations > 100 → cut by half
5. Theme is generic → switch to brand template
If all five pass, you're shippable.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |