pptx-slide-auditor
The pptx-slide-auditor skill systematically analyzes PowerPoint presentations to identify layout issues, text overflow, visual hierarchy problems, and styling inconsistencies. Use it when reviewing a deck before presenting, sending to stakeholders, or sharing with external audiences. It delivers a detailed slide-by-slide report with issues ranked by severity, pattern analysis across the deck, and audience-specific recommendations for fixes.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/pptx-slide-auditor && cp -r /tmp/pptx-slide-auditor/plugins/pm-delivery/skills/pptx-slide-auditor ~/.claude/skills/pptx-slide-auditorSKILL.md
# PPTX Slide Auditor 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. ## Required Inputs Ask the user for these if not provided: - **The deck** (upload the .pptx file or individual slide screenshots) - **Audience** (internal team / executive / external client / conference / investor) - **Presentation mode** (presented live / sent to read / shared async on video) - **Areas of concern** (optional — e.g. "I think slide 12 is overcrowded") ## Output Structure ### 1. Deck Overview | 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] | ### 2. Slide-by-Slide Audit For each slide with issues: **Slide N: [Slide title]** - Status: Ready / Fix before sending / Major revision - Issues found: - [Specific issue with exact location — e.g. "Body text extends beyond the text frame on the right side"] - [Issue 2] - Suggested fix: [Specific action — move element, reduce text, resize] Slides with no issues: just list the slide numbers. Do not write anything else about them. ### 3. Pattern Issues Across the Deck Issues that repeat across multiple slides: **[Pattern title — e.g. "Inconsistent body text size"]** - Slides affected: [list] - Root cause: [master slide issue / manual overrides / mixed templates] - Fix: [Single action to resolve across all affected slides] ### 4. Visual Hierarchy Check | 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 | | ### 5. Audience-Specific Flags Based on the stated audience: - **Executive audience:** flag slides with too much text, complex tables, or unclear bottom-line messages - **External client:** flag slides with internal jargon, unfinished placeholder text, or confidentiality concerns - **Live presentation:** flag slides that will be hard to read from the back of a room - **Async/video:** flag slides that assume a presenter voiceover ### 6. Prioritised Fix List | # | Fix | Slide | Effort | Impact | |---|---|---|---|---| | 1 | [Specific fix] | Slide N | Low/Med/High | High | Order by: fixes before handoff (critical) > consistency fixes (high) > polish (medium). ## Quality Checks - [ ] Every issue references a specific slide number and location on the slide - [ ] Pattern issues are identified separately from slide-specific issues - [ ] Fix list is ordered by impact, not by slide order - [ ] Audience-appropriate concerns flagged explicitly - [ ] Slides without issues are listed briefly, not ignored ## Anti-Patterns - [ ] Do not flag stylistic preferences as issues — only report genuine layout problems, overflow, and consistency errors - [ ] Do not produce a flat list of issues — group by severity (Critical / Major / Minor) so fixes can be prioritised - [ ] Do not skip slides without commenting — every slide must have an explicit pass or issue status - [ ] Do not suggest redesigning content — the audit scope is layout, consistency, and readability, not messaging - [ ] Do not report the same issue type repeatedly across slides without summarising the pattern — consolidate repeated issues ## Example Trigger Phrases - "Audit this slide deck before my board meeting" - "Review this PowerPoint for layout issues" - "Check this presentation for consistency problems" - "QA my deck before I send it to the client" - "What is wrong with slide 7 in this deck?" ## Why This Works Better on Opus 4.7 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.
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.