Help us improve
Share bugs, ideas, or general feedback.
From pm-delivery
Audits PowerPoint presentations for layout issues, text overflow, visual hierarchy problems, and consistency gaps. Produces a slide-by-slide report with ranked issues and fixes.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-deliveryHow this skill is triggered — by the user, by Claude, or both
Slash command
/pm-delivery:pptx-slide-auditorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Runs a systematic visual and structural audit of a PowerPoint presentation — identifying layout issues, text overflow, inconsistent styling, weak visual hierarchy, and slides that will cause problems in a presentation setting. Built to leverage Opus 4.7 vision improvements for pixel-level layout analysis.
Audits PowerPoint decks for layout bugs, design inconsistencies, accessibility issues, AI-generation tells, and silent generator failures. Run after creating presentations or when reviewing uploaded .pptx files.
Evaluates presentation slides with 12-point checklist for cognitive load, one idea per slide, assertions titles, element limits, accessibility, and TED/MIT best practices.
Handles .pptx files: extracts text with markitdown, generates thumbnails, edits via unpack/pack XML workflow, creates decks with pptxgenjs.
Share bugs, ideas, or general feedback.
Runs a systematic visual and structural audit of a PowerPoint presentation — identifying layout issues, text overflow, inconsistent styling, weak visual hierarchy, and slides that will cause problems in a presentation setting. Built to leverage Opus 4.7 vision improvements for pixel-level layout analysis.
Ask the user for these if not provided:
| Metric | Result |
|---|---|
| Total slides | N |
| Overall status | Ready / Minor fixes needed / Major revisions required |
| Readability score | /10 |
| Visual consistency score | /10 |
| Most common issue | [Pattern observed across multiple slides] |
For each slide with issues:
Slide N: [Slide title]
Slides with no issues: just list the slide numbers. Do not write anything else about them.
Issues that repeat across multiple slides:
[Pattern title — e.g. "Inconsistent body text size"]
| Dimension | Status | Notes |
|---|---|---|
| Title consistency (size, font, colour) | Pass / Fail | |
| Body text readability at presentation distance | Pass / Fail | |
| Image placement alignment | Pass / Fail | |
| Whitespace and breathing room | Pass / Fail | |
| Data visualisation clarity | Pass / Fail / N/A |
Based on the stated audience:
| # | Fix | Slide | Effort | Impact |
|---|---|---|---|---|
| 1 | [Specific fix] | Slide N | Low/Med/High | High |
Order by: fixes before handoff (critical) > consistency fixes (high) > polish (medium).
Earlier models struggled with precise spatial analysis of slide layouts — they would hallucinate issues or miss obvious overflow problems. Opus 4.7 vision improvements mean coordinates map 1:1 to pixels, making slide-level issue detection reliable without manual screenshot annotation.