florianbonnet14/ThePowerOfAnalytics_ClaudeSkills / presentation-builder
presentation-builder
VerifiedTransform analysis documents into structured presentation slide plans. Use when users need to convert markdown analysis documents into presentation decks, create slide-by-slide breakdowns with specific slide types and content structure, or plan presentation flow from analytical content. Outputs detailed slide specifications including slide types (Cover, Executive Summary, Text, Chart, Section) and all required content elements for each slide.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 6.5 KB |
| presentation-builder-tutorial.md | markdown | 3.6 KB |
| references/example-analysis-mobile-conversion.md | markdown | 8.3 KB |
| references/example-presentation-output.md | markdown | 8.2 KB |
| references/presentation-architect-agent.md | markdown | 5.6 KB |
references/example-presentation-output.md
View on GitHub# Example Presentation Slide Plan
## Mobile App Conversion Rate Drop Analysis
*This is an example of what the Presentation Builder skill produces*
---
SLIDE 1: Cover Slide
Title: Mobile App Conversion Rate Drop: Root Cause & Recovery Plan
Date: October 15, 2024
Analyst: Sarah Chen
---
SLIDE 2: Executive Summary
MOTIVE:
• Mobile app conversion rate dropped from 24% to 16% in Q3 2024 (8pp decline)
Supporting points:
• Represents $2.4M in lost quarterly revenue
• Sudden drop beginning mid-August, persisting through September
• Critical to address for Q4 revenue targets
ANSWER:
• Root cause: New onboarding flow (launched Aug 15) requires phone verification before browsing
Supporting points:
• Creates "wall" effect causing 45% of new users to abandon during onboarding
• Users who complete are 20% less likely to make first purchase
• Issue isolated to mobile app; desktop and mobile web unaffected
IMPACT:
• $2.4M lost in Q3; $3.2M projected loss in Q4 if unresolved
Supporting points:
• 180K fewer new accounts created vs. target
• 15% lower 30-day retention for recent cohorts
• App store rating dropped from 4.7 to 4.3
NEXT-STEPS:
• Roll back to previous onboarding flow → Engineering team → Oct 18
Supporting points:
• Conduct user research on verification preferences → UX Research → Oct 25
• Redesign onboarding with optional verification → Product team → Nov 15
• Implement A/B testing framework → Data team → Nov 30
---
SLIDE 3: Section Slide
Section: 1
Title: Problem Definition & Scope
---
SLIDE 4: Simple Chart Slide
Action Title: Conversion Rate Declined Sharply Starting Mid-August
Bullet points:
• Drop from 24% to 16% represents 33% decline in conversion performance
• Timing coincides exactly with August 15 onboarding flow deployment
Chart: [Conversion Rate | Week (Q2-Q3) | Line chart]
---
SLIDE 5: Simple Chart Slide
Action Title: Revenue Impact of $2.4M in Q3 With Further Risk in Q4
Bullet points:
• Lost revenue accelerating as user base compounds
• Q4 projection assumes no intervention; recovery plan can prevent loss
Chart: [Lost Revenue | Month | Waterfall chart]
---
SLIDE 6: Section Slide
Section: 2
Title: Root Cause Analysis
---
SLIDE 7: Text Slide
Action Title: Conversion Decline is Isolated to New Users, Not Platform-Wide Issue
Bullet points:
• New users (<7 days) dropped from 24% to 16% (-8pp)
• Returning users (7+ days) maintained at 44-45% (no change)
• Issue specific to new user experience, not broader product problem
• Core product remains strong for engaged users
---
SLIDE 8: Double Chart Slide
Action Title: Onboarding Abandonment Rate Tripled After August 15 Change
Chart 1: [Onboarding Completion Rate | Week | Line chart]
Chart 2: [Drop-off by Step | Onboarding Step | Funnel chart]
Callout: 78% of abandonment occurs specifically at phone verification step, showing clear friction point
---
SLIDE 9: Simple Chart Slide
Action Title: Users Who Complete New Onboarding Still Convert 25% Less Than Previous Cohorts
Bullet points:
• July cohort (old flow): 28% first-purchase conversion
• August-September cohorts (new flow): 21-22% conversion
• Even "successful" users show reduced engagement and trust
Chart: [First Purchase Rate by Cohort | Month | Bar chart]
---
SLIDE 10: Section Slide
Section: 3
Title: Validation & Evidence
---
SLIDE 11: Text Slide
Action Title: Issue is Mobile App-Specific; Other Platforms Maintain Performance
Bullet points:
• Mobile app: -8pp conversion rate decline
• Mobile web: -1pp (within normal variance)
• Desktop web: No change (22% maintained)
• Confirms mobile app onboarding change as isolated root cause
---
SLIDE 12: Simple Chart Slide
Action Title: App Store Reviews Confirm User Frustration With Phone Verification
Bullet points:
• App rating dropped from 4.7 to 4.3 stars
• 450+ reviews mentioning phone verification vs. 12 in previous month
• Common themes: "Too intrusive," "Don't trust," "Want to browse first"
Chart: [App Rating Over Time | Week | Line chart with annotation]
---
SLIDE 13: Text Slide
Action Title: Impact is Consistent Across All Geographies and Device Types
Bullet points:
• US: -8pp, Europe: -7pp, Asia: -9pp conversion decline
• iOS: -8pp, Android: -8pp (identical impact)
• Confirms issue is fundamental flow design, not technical implementation
• Universal negative reaction to verification requirement
---
SLIDE 14: Section Slide
Section: 4
Title: Recovery Plan & Recommendations
---
SLIDE 15: Text Slide
Action Title: Immediate Rollback Will Recover 6-7pp Within One Week
Bullet points:
• Revert to proven previous flow that allows browsing before verification
• Execution timeline: Oct 16-18 (3 days)
• Minimal risk: returning to known-good state
• Expected to reduce abandonment from 45% to ~12%
---
SLIDE 16: Text Slide
Action Title: User Research Will Inform Redesigned Onboarding With Optional Verification
Bullet points:
• Conduct interviews and surveys (Oct 19-25) to understand verification attitudes
• Design new flow allowing browsing first, verification at checkout
• A/B test new approach to validate before full rollout
• Timeline: Redesign complete by Nov 15
---
SLIDE 17: Simple Chart Slide
Action Title: Recovery Timeline Shows Full Conversion Rate Restoration by December
Bullet points:
• Rollback phase: 6-7pp recovery in 1 week (Oct 18-25)
• Redesign phase: Additional 1-2pp recovery with new flow (Nov 15-30)
• Full recovery to 24%+ by early December
Chart: [Conversion Rate Projection | Week | Line chart with phases]
---
SLIDE 18: Text Slide
Action Title: A/B Testing Framework Will Prevent Similar Issues in Future
Bullet points:
• Current incident occurred due to 100% rollout without testing
• New framework enables gradual rollout to 10-20% of users first
• Catches problems early with minimal business impact
• Builds experimentation culture for data-driven decisions
---
SLIDE 19: Text Slide
Action Title: Next Steps and Owners
Bullet points:
• Rollback to previous flow → Mike Rodriguez (Engineering) → Oct 18
• User research on verification → Emily Watson (UX Research) → Oct 25
• Redesigned onboarding flow → Lisa Park (Product) → Nov 15
• A/B testing platform → James Liu (Data) → Nov 30
---
SLIDE 20: Section Slide
Section: 5
Title: Q&A
---
## Appendix Slides (Optional Deep Dives)
SLIDE A1: Text Slide
Action Title: Detailed Cohort Performance Comparison
Bullet points:
• June cohort: 88% completion, 28% purchase, 52% retention
• July cohort: 87% completion, 28% purchase, 51% retention
• August cohort: 55% completion, 22% purchase, 44% retention
• September cohort: 56% completion, 21% purchase, 43% retention
---
SLIDE A2: Text Slide
Action Title: Methodology and Data Sources
Bullet points:
• Data sources: Mobile app analytics (Amplitude), app store reviews
• Time period: Q2-Q3 2024 (April-September)
• Sample size: 2.4M user sessions, 180K new users
• Conversion measured as % making purchase within 30 days
---
SLIDE A3: Text Slide
Action Title: Risk Assessment and Mitigation
Bullet points:
• Risk: Rollback may expose previous technical issues (LOW - no issues in past)
• Risk: User research may not yield clear direction (MEDIUM - mitigate with large sample)
• Risk: Redesign timeline may slip (MEDIUM - build in buffer time)
• Risk: Competition may gain users during recovery (HIGH - execute quickly)
---
## Presentation Plan Summary
**Total Slides:** 20 main slides + 3 appendix slides
**Estimated Duration:** 25-30 minutes with Q&A
**Audience:** Executive leadership + Product/Engineering stakeholders
**Delivery Format:** In-person with printed appendix for reference
**Key Success Factors:**
1. Lead with the answer (Executive Summary) - don't build suspense
2. Use data to tell story, not overwhelm with numbers
3. Focus on clear narrative arc: Problem → Root Cause → Solution
4. End with specific actions and owners
5. Have appendix ready for detailed questions
**Presentation Tips:**
- Spend 3-4 minutes on Executive Summary slide
- Use chart annotations to highlight key points during presentation
- Pause for questions after Root Cause Analysis section
- Emphasize speed and confidence in recovery plan
- Keep Q&A focused on execution details, not re-litigating the problem
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |