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-analysis-mobile-conversion.md
View on GitHub# Example Analysis: Mobile App Conversion Rate Drop
## Analysis Context
**Question:** Why did our mobile app conversion rate drop 8 percentage points in Q3?
**Analyst:** Sarah Chen
**Date:** October 15, 2024
**Period Analyzed:** Q3 2024 (July-September)
## Executive Summary
### Motive
Our mobile app conversion rate dropped from 24% to 16% in Q3 2024, representing an 8 percentage point decline. This translates to approximately $2.4M in lost quarterly revenue. The drop was sudden (beginning mid-August) and has persisted through September. Understanding and addressing this issue is critical to Q4 revenue targets.
### Answer
The conversion rate drop is primarily caused by a new onboarding flow launched on August 15th that introduced friction in the account creation process. Specifically, the new flow requires phone verification before allowing users to browse products, whereas the old flow allowed browsing first. This "wall" effect is causing 45% of new users to abandon during onboarding. Additionally, users who do complete onboarding are 20% less likely to make a first purchase compared to previous cohorts.
### Impact
- **Revenue:** $2.4M lost in Q3; $3.2M projected loss in Q4 if not addressed
- **User Base:** 180K fewer new accounts created vs. target
- **Retention:** Early signals suggest 15% lower 30-day retention for August/September cohorts
- **Competitive Position:** App store rating dropped from 4.7 to 4.3 due to onboarding complaints
### Next Steps
1. **Immediate:** Roll back to previous onboarding flow (Oct 18) - Engineering team
2. **Short-term:** Conduct user research on verification preferences (Oct 25) - UX Research team
3. **Medium-term:** Redesign onboarding with optional verification (Nov 15) - Product team
4. **Ongoing:** Implement A/B testing framework for future changes (Nov 30) - Data team
## Detailed Findings
### Finding 1: Conversion Rate Decline is Isolated to New Users
**Data:**
- New users (<7 days): 24% → 16% (-8pp)
- Returning users (7+ days): 45% → 44% (-1pp, within normal variance)
- Cohort comparison: August cohort performing 35% worse than July cohort
**Insight:** The issue is specific to the new user experience, not a broader platform problem. Returning users are unaffected, suggesting the core product remains strong.
### Finding 2: Onboarding Abandonment Spiked After August 15
**Data:**
- Pre-August 15: 12% abandonment rate during onboarding
- Post-August 15: 45% abandonment rate during onboarding
- Specific drop-off: 78% of abandonment occurs at phone verification step
- Time to abandon: Average 45 seconds (suggests immediate friction)
**Insight:** The phone verification requirement is creating a significant barrier. Users aren't willing to provide phone numbers before seeing product value.
### Finding 3: Users Who Complete New Onboarding Convert Less
**Data:**
- July cohort (old flow): 28% first-purchase conversion
- August cohort (new flow): 22% first-purchase conversion
- September cohort (new flow): 21% first-purchase conversion
- Time to first purchase: Increased from 2.3 days to 3.8 days
**Insight:** Even among users who complete the new onboarding, there's a lingering negative effect. The aggressive verification requirement may be creating distrust or reducing initial engagement.
### Finding 4: Mobile-Specific Issue
**Data:**
- Mobile app: 24% → 16% (-8pp)
- Mobile web: 18% → 17% (-1pp)
- Desktop web: 22% → 22% (no change)
**Insight:** The onboarding change only affected the mobile app. Other platforms maintained performance, confirming the mobile app onboarding is the root cause.
### Finding 5: App Store Feedback Confirms User Frustration
**Data:**
- App rating: 4.7 → 4.3 (drop of 0.4 stars)
- Review volume: 3x increase in negative reviews mentioning "phone number"
- Common complaints: "Too intrusive," "Don't trust with phone," "Just want to browse first"
- 450+ reviews specifically mentioning phone verification (vs. 12 in previous month)
**Insight:** Users are vocally unhappy with the change. This isn't just data - real people are frustrated enough to leave negative reviews.
## Supporting Analysis
### Cohort Comparison
| Cohort | Onboarding Flow | Completion Rate | First Purchase Rate | 30-Day Retention |
|--------|----------------|-----------------|--------------------|--------------------|
| June | Old | 88% | 28% | 52% |
| July | Old | 87% | 28% | 51% |
| August | New | 55% | 22% | 44% |
| September | New | 56% | 21% | 43% |
### Geographic Analysis
The impact is consistent across all major markets:
- US: -8pp conversion rate
- Europe: -7pp conversion rate
- Asia: -9pp conversion rate
This suggests the issue is fundamental to the onboarding design, not cultural or regional.
### Device Analysis
Impact is consistent across device types:
- iOS: -8pp
- Android: -8pp
Both platforms show identical degradation, confirming the flow design (not technical implementation) is the issue.
## Recommendations
### Recommendation 1: Immediate Rollback (Priority: Critical)
**Action:** Revert to previous onboarding flow that allows browsing before verification
**Rationale:**
- The new flow is actively harming the business
- Previous flow had proven performance
- Rollback can be executed quickly (2-3 days)
- Risk is minimal (reverting to known-good state)
**Expected Impact:**
- Recover 6-7pp of conversion rate within 1 week
- Reduce onboarding abandonment from 45% to ~12%
- Stop further brand damage from negative reviews
**Implementation:**
- Timeline: Oct 16-18 (3 days)
- Owner: Engineering team (Mike Rodriguez)
- Risks: Minimal; previous code is in version control
### Recommendation 2: User Research on Verification (Priority: High)
**Action:** Conduct qualitative research to understand user attitudes toward verification
**Rationale:**
- Verification may still be valuable for fraud prevention
- Need to understand what users are willing to provide and when
- Should inform redesign of onboarding flow
**Expected Impact:**
- Clear requirements for redesigned flow
- Understanding of acceptable verification timing
- Reduced risk of repeating this mistake
**Implementation:**
- Timeline: Oct 19-25 (1 week)
- Owner: UX Research team (Emily Watson)
- Methods: User interviews (20), surveys (500+)
### Recommendation 3: Redesigned Onboarding with Optional Verification (Priority: Medium)
**Action:** Create new onboarding flow that allows browsing first, with verification optional or positioned at checkout
**Rationale:**
- Balances business need for verification with user experience
- Allows users to see value before commitment
- Industry best practice (see Spotify, Netflix models)
**Expected Impact:**
- Maintain high completion rates (80%+)
- Recover full conversion rate (24%+)
- Enable verification for users ready to purchase
**Implementation:**
- Timeline: Oct 26 - Nov 15 (3 weeks)
- Owner: Product team (Lisa Park)
- Dependencies: User research findings
### Recommendation 4: A/B Testing Framework (Priority: Medium)
**Action:** Implement proper A/B testing infrastructure to prevent similar issues
**Rationale:**
- This incident occurred because onboarding change was rolled out to 100% of users
- A/B testing would have caught the issue affecting 10-20% of users
- Enables data-driven decision making for future changes
**Expected Impact:**
- Prevent future large-scale negative impacts
- Enable faster iteration with lower risk
- Build experimentation culture
**Implementation:**
- Timeline: Nov 1-30 (4 weeks)
- Owner: Data team (James Liu)
- Scope: Mobile app experimentation platform
## Appendix
### Methodology
- **Data sources:** Mobile app analytics, user feedback, app store reviews
- **Time period:** Q2-Q3 2024 (April-September)
- **Sample size:** 2.4M user sessions, 180K new users
- **Tools:** Amplitude, App Store Connect, Google Play Console
### Assumptions
- Conversion rate calculated as % of users who make purchase within 30 days
- Cohorts defined by signup date
- Revenue impact calculated using average order value of $85
### Limitations
- Cannot directly measure users who never downloaded app due to poor ratings
- User research will be retrospective (after problem occurred)
- Some impact may be due to seasonal factors (though this appears minimal)
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 |