Mmcp.market

presentation-builder skill

by florianbonnet14·florianbonnet14/ThePowerOfAnalytics_ClaudeSkills·29 stars·MIT

Transform 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.

A100/100content scan

Is the presentation-builder skill safe?

Clean: nothing in its files matched our rules. We read 5 files in the folder on 2026-09-28.

No findings.

Install the presentation-builder skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/florianbonnet14/ThePowerOfAnalytics_ClaudeSkills.git /tmp/ThePowerOfAnalytics_ClaudeSkills
mkdir -p ~/.claude/skills
cp -r /tmp/ThePowerOfAnalytics_ClaudeSkills/presentation-builder ~/.claude/skills/presentation-builder
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Presentation Builder Skill

Transform analysis documents (in markdown format) into structured presentation slide plans with detailed content specifications for each slide.

Overview

This skill takes an analysis document and produces a slide-by-slide presentation plan that follows presentation best practices. It does NOT create PowerPoint files - instead, it outputs a clear specification of what each slide should contain, including slide type and all content elements.

Supported Slide Types

1. Cover Slide

  • Title of analysis
  • Date of analysis
  • Name of analyst

2. Executive Summary Slide

Uses the existing executive summary .md file (ask th suer about it). If no file, use the executive-summary-writer to write an executive summary and take the content of the resulting file to produce this slide

3. Text Slide (Bullet Points)

  • Action Title (insight-driven, complete sentence)
  • Bullet points (2-4 maximum)

4. Simple Chart Slide

  • Action Title (insight-driven, complete sentence)
  • Bullet points (1-2 key takeaways)
  • Chart specification: [Metric | x-axis | chart type]

5. Double Chart Slide

  • Action Title (insight-driven, complete sentence)
  • Chart 1 specification: [Metric | x-axis | chart type]
  • Chart 2 specification: [Metric | x-axis | chart type]
  • Callout (key insight connecting both charts)

6. Section Slide

  • Section number
  • Section title

Presentation Structure

Follow the pyramidal principle:

  1. Cover slide
  2. Executive Summary (MAIN framework)
  3. Section dividers + content slides organized by theme
  4. Next steps/recommendations
  5. Q&A slide (optional)

Output Format

For each slide, output:

SLIDE [number]: [Slide Type]

[Content specifications based on slide type]

---

Example Output

SLIDE 1: Cover Slide

Title: Q3 Conversion Rate Analysis: Root Causes & Recovery Plan
Date: October 15, 2024
Analyst: Sarah Chen

---

SLIDE 2: Executive Summary

MOTIVE:
• Q3 conversion rate dropped 15pp (from 18% to 15%), missing target by 12%

Supporting points:
• Represents ~$1.2M annual recurring revenue at risk
• Urgent investigation conducted to identify root cause

ANSWER:
• Root cause: New onboarding flow (launched Sept 15) added friction at step 3

Supporting points:
• Drop isolated to new users (<7 days); returning users unaffected
• Recommend reverting flow immediately, redesigning with user feedback

IMPACT:
• Reverting flow should recover 10pp within 1 week (to 16%)

Supporting points:
• Full recovery to 18% expected within 3 weeks after redesign
• If not addressed, expect $300K Q4 revenue shortfall

NEXT-STEPS:
• Revert onboarding flow → Dev Team → Oct 2 (Tomorrow)

Supporting points:
• User research on friction points → UX Team → Oct 9
• Redesigned flow tested → Product Team → Oct 23
• Rollout decision meeting → Leadership → Oct 30

---

SLIDE 3: Section Slide

Section: 1
Title: Current Performance Analysis

---

SLIDE 4: Simple Chart Slide

Action Title: New Users

Guidelines

Slide Titles

  • Use complete sentences that state the insight
  • NOT just topic names (✗ "Conversion Analysis" ✓ "New Users Convert 30% Less")
  • Front-load the key message
  • Keep to 8-12 words maximum

Content Principles

  • One message per slide
  • Maximum 6 bullet points per slide
  • Maximum 6 words per bullet point (guideline)
  • Support every claim with data where possible
  • Every slide should answer "So What?"

Chart Specifications

Format: [Metric name | x-axis variable | chart type]

Common chart types:

  • Line chart (trends over time)
  • Bar chart (comparisons)
  • Stacked bar chart (composition)
  • Column chart (vertical comparisons)
  • Area chart (cumulative trends)
  • Scatter plot (correlations)
  • Waterfall chart (sequential changes)

Presentation Flow

  1. Start with answer (Executive Summary)
  2. Group related insights into sections
  3. Use section dividers for major transitions
  4. Build narrative logically
  5. End with clear next steps

Processing Steps

When given an analysis document:

  1. Extract key elements:
  • Main question/objective
  • Key findings and insights
  • Supporting data and evidence
  • Recommendations
  • Next steps
  1. Structure the narrative:
  • Create Executive Summary using MAIN framework
  • Identify 3-5 main themes/sections
  • Determine logical flow of insights
  • Plan section breaks
  1. Design each slide:
  • Choose appropriate slide type
  • Write action-oriented title
  • Select supporting content
  • Specify chart requirements (if applicable)
  1. Output specification:
  • Number slides sequentially
  • Format each slide according to type
  • Include all required content elements
  • Maintain consistent structure

Quality Checks

Before finalizing output, verify:

  • [ ] Executive Summary captures all MAIN elements
  • [ ] Slide titles are insights, not topics
  • [ ] Each slide has clear "So What?"
  • [ ] Charts are specified with metric, axis, and type
  • [ ] Flow is logical and builds narrative
  • [ ] Section breaks mark major transitions
  • [ ] Total slide count is appropriate (typically 12-20 for main deck)

Flexibility

Adapt the structure based on:

  • Analysis type: Root cause analysis, performance review, strategy recommendation
  • Audience: Executive (fewer slides, high-level) vs. Technical (more detail)
  • Purpose: Decision-making (focus on recommendations) vs. Informational (comprehensive)
  • Time available: Adjust depth and number of slides accordingly

Default to 15-18 slides for a standard presentation unless specified otherwise.

More skills from florianbonnet14/ThePowerOfAnalytics_ClaudeSkills

  • Aanalysis-plannerStructure analysis investigations before diving into data, preventing wasted time and ensuring thoroughness. Use when users need to plan any significant analysis, investigate KPI changes, respond to stakeholder questions, plan feature/experiment analysis, or when previous analyses were unfocused. Helps define clear goals, generate testable hypotheses, create systematic analysis roadmaps, identify required data, estimate timelines, and prevent analysis paralysis.
  • Aanalysis-results-collectorTransform completed analysis work into structured, communication-ready documentation by conducting guided conversations that extract key findings, evidence, and recommendations. Use when a user has completed an analysis (typically following an analysis plan created by the analysis-planner skill) and needs to document results, create findings summaries, build executive reports, or prepare analysis outcomes for stakeholder communication. This skill systematically gathers what was tested, what was found, and what should be done next, then generates a professional markdown document ready for distribution.
  • Aanalytics-orchestratorIntelligent entry point to the analytics ecosystem based on "The Power of Analytics" book by Florian Bonnet. Guides users to the right analytics agent based on their needs, recommends workflow sequences, and provides clear instructions for launching agents. Use when users need help choosing between analytics agents, want to start an analytics project but aren't sure where to begin, or ask "what can you help me with" in an analytics context. Also use when users mention analytics tasks like defining metrics, planning analysis, collecting results, creating presentations, or writing executive summaries.
  • Acohort-analysis-specialistTrack customer behavior over time by grouping customers based on shared characteristics or experiences. Use when measuring retention rates, understanding how customers evolve over time, comparing new vs old user behavior, evaluating product changes by cohort, identifying at-risk cohorts early, or calculating LTV by cohort. Essential for understanding retention, lifecycle patterns, and how product changes affect different user vintages.
  • Aexecutive-summary-writerTransform analysis findings into clear, actionable executive summaries using the MAIN framework (Motive, Answer, Impact, Next steps) and Pyramidal Principle. Use when completing any analysis that needs stakeholder buy-in, preparing for leadership meetings, documenting investigation findings, writing business reviews, creating post-mortems, proposing initiatives based on data, or communicating insights to executives.
  • Ainfluential-factors-detectiveIdentify and analyze qualitative factors that influence KPIs but can't be measured as numbers. Use when users need to find non-quantifiable drivers affecting metrics (like copy quality, design aesthetics, timing), plan A/B tests for subjective elements, bridge the gap between data and design/content decisions, understand why quantitative analysis is incomplete, optimize messaging or UX elements, or identify the actual levers to pull for improving KPIs at the leaf nodes of a KPI tree.
  • Akpi-tree-architectBuild comprehensive KPI trees from North Star metrics. Use when users need to decompose metrics into hierarchical driver structures, create MECE (Mutually Exclusive, Collectively Exhaustive) breakdowns, identify leverage points, map performance drivers, or prepare for root cause analysis. Essential for setting up analytical foundations after defining a North Star metric.
  • Anorth-star-metric-advisorStrategic framing and KPI setting specialist that helps identify and validate the single most important metric capturing customer value delivery and predicting business success. Use when starting a new team or product, when existing product lacks clear success metric, when team seeks to define what success means, or when metrics don't align with customer value and/or business goals.
  • Asegmentation-expertIdentify, analyze, and act on customer segments to uncover hidden patterns and understand behavior differences. Use when investigating KPI changes to understand which customers drove them, planning targeted initiatives, building customer personas, or analyzing performance differences across groups. Helps select meaningful segmentation dimensions, create actionable segments, analyze performance differences, calculate segment contributions, and generate segment-specific recommendations.

All agent skills → · MCP servers