From presentation-review
Review MARP markdown presentations for "Death by PowerPoint" issues. Use when asked to review, critique, or improve a presentation, check slides for clarity, or when terms like "Death by PowerPoint," "slide review," "too much text," or "presentation feedback" appear. Applies David JP Phillips' principles for cognitive optimization of slides.
How this skill is triggered — by the user, by Claude, or both
Slash command
/presentation-review:death-by-pptThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review MARP presentations using David JP Phillips' "Death by PowerPoint" principles.
Review MARP presentations using David JP Phillips' "Death by PowerPoint" principles.
Apply these six principles when reviewing. Frame feedback as suggestions with rationale.
Each slide should convey a single, clear message.
Why: Multiple messages split audience focus, reducing comprehension and retention.
Check: Can you identify one takeaway? Could this slide be split?
Count: headings, bullets, images, code blocks, icons, diagrams.
Why: Exceeding six objects increases cognitive load ~500%. Audience shifts from seeing to counting.
MARP notes:
- bullet = 1 object*) still count on final render<!-- -->) don't countUse short phrases, keywords, or visuals — not full sentences.
Why: The redundancy effect — brains can't read and listen simultaneously. Text and speech compete; audience retains neither.
Suggest: Move sentences to speaker notes, reduce bullets to keywords.
Most important element should be largest/highest contrast.
Why: Attention follows: moving objects, signaling colors, contrast, size. In static slides, size and contrast guide the eye.
MARP notes:
)![bg opacity:0.3]**bold** and headings highlight what mattersDark backgrounds shift focus to presenter, reduce glare.
Why: Bright slides act as light source drawing attention away from speaker.
MARP notes:
theme: default is light)<!-- _class: invert --> for dark modesection { background: #1a1a2e; color: #eee; }50 clean slides > 10 cluttered slides.
Why: "Keep it to 10 slides" causes cramming. Audience experiences pace, not page count.
Flag these even when design is solid:
| Issue | Flag When |
|---|---|
| Reading slides | Text that presenter will likely read verbatim |
| Projector dependency | Critical info only on slides, no verbal equivalent |
| Pacing | Multiple dense slides without breathing room |
marp: true present, theme declared--- used consistently![w:400], ![bg right:40%])<!-- notes --> formatpaginate: true doesn't clutter minimal slidesDefault: Slide-by-slide breakdown.
### Slide [N]: [Headline or first line]
**Objects:** [count] (list if over 6)
**Message:** [Clear / Unclear / Multiple]
**Suggestions:**
- [Actionable suggestion with rationale]
Offer alternatives:
<!-- REVIEW: ... --> inserted### Slide 4: Why Static Sites?
**Objects:** 8 (heading, 6 bullets, image)
**Message:** Multiple — covers speed, security, and cost
**Suggestions:**
- Split into three slides (one per benefit). Single ideas land better than lists.
- Image is small (`w:200`) relative to bullets. Enlarge or remove to reduce objects.
- Bullets are full sentences. Shorten to keywords — you'll expand verbally.
Per slide:
Principles from David JP Phillips' TEDx talk "How to Avoid Death by PowerPoint" and multimedia learning research (Mayer, 2005).
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub heyitsgilbert/marketplace --plugin presentation-review