Presentation Decks

Build and structure presentation decks for any audience. AI generates slide outlines with speaker notes, follows SCR narrative structure, and adapts tone for technical vs. executive rooms.

Skill Details

Install this skill

Versionv1.0.0AuthorJorge ArteagaLicenseMITSections11

Works with

Claude CodeCursorWindsurf

When This Skill Owns the TaskWorkflow

Required Context to Gather FirstWorkflow

Before building a deck, ask for or infer:

Presentation purpose — What is this deck trying to achieve? (First meeting, business case, QBR, POV readout)

Audience — Who is in the room? (C-suite, IT team, mixed business/technical, partner)

Duration — How long is the slot? (20 min, 45 min, 90 min)

Known customer context — Industry, pain points, key stakeholders

Salesforce products in scope — What are we proposing or presenting?

Call to action — What decision or action should this deck drive?

Existing assets — Any discovery summary, architecture review, or PoV to incorporate?

WorkflowWorkflow

Define the outcome — What does success look like at the end of this presentation?

Choose the deck type — Apply the right template from the table below.

Build the narrative arc — Use SCR (Situation / Complication / Resolution) for the spine.

Outline each section — Generate the slide-by-slide structure.

Write the speaker notes — Every slide needs what to say, not just what to show.

Adapt for the audience — Apply the audience adaptation guidelines.

Design the close — The final slide should drive a specific decision, not just say "Thank you."

Core Frameworks

Deck Types and When to Use Them

SCR Narrative Framework

Every effective business presentation follows this spine:

Code

SITUATION — Where we are now
  "Based on what we've learned about [Company], you're dealing with [current state].
   Your [role] are [specific challenge]. This is common in [industry]."

COMPLICATION — Why the current state is a problem
  "The challenge is that [status quo] means [business impact].
   Every [time period], this costs you approximately [quantified pain]."

RESOLUTION — What we propose and why it works
  "What if [specific capability] could [outcome]?
   [Customer similar to them] did exactly this and saw [result].
   Here's how we'd do it with you..."

Audience Adaptation Guide

Slide-by-Slide Anatomy

For every slide, the AI should produce:

Code

SLIDE [N]: [Slide Title]
TYPE: [Title / Data / Story / Architecture / Transition / Close]
HEADLINE: [The one takeaway this slide should land — 1 sentence, written as a conclusion]
VISUAL: [What goes on the slide — chart, diagram, quote, image, bullets]
SPEAKER NOTES: [What to say out loud — 3-6 sentences; include transitions to next slide]

Output FormatTemplate

Slide Deck Outline Template

MARKDOWN

# [Deck Title] — [Company Name]
**Presentation Type:** [Type] | **Audience:** [Roles] | **Duration:** [X min] | **Date:** [Date]

## Presentation Goal
[One sentence: what decision or action should this deck drive?]

## Narrative Arc (SCR Summary)
- **Situation:** [1-2 sentences on current state]
- **Complication:** [1-2 sentences on why that's a problem]
- **Resolution:** [1-2 sentences on the proposed solution and outcome]

---

## Slide Outline

### Section 1: Opening (Slides 1-[X])

SLIDE 1: [Title Slide]
TYPE: Title
HEADLINE: [Not applicable — this is the title]
VISUAL: Company name, Salesforce logo, date, presenter name
SPEAKER NOTES: "Thank you for the time today. Our goal is [outcome]. Before we dive in, I want to make sure we're focused on what matters most to [audience]. [Opening question or statement]."

SLIDE 2: [Agenda / What We'll Cover]
TYPE: Transition
HEADLINE: "Here's what we'll cover — and what we want to leave with"
VISUAL: Simple numbered agenda (3-4 items max)
SPEAKER NOTES: "We'll spend about [X min] on [topic]. The most important thing I want you to walk away with is [key outcome]."

---

### Section 2: Situation (Slides [X]-[Y])

SLIDE [N]: [Current State]
TYPE: Story
HEADLINE: "[Specific challenge framed as their reality]"
VISUAL: [Chart showing current state metric / quote from discovery / before/after]
SPEAKER NOTES: "[Reference something specific from discovery]. This is what we heard from your team..."

---

### Section 3: Complication (Slides [X]-[Y])

SLIDE [N]: [The Cost of the Current Approach]
TYPE: Data
HEADLINE: "[Quantified impact of the current state]"
VISUAL: [Numbers, chart, or benchmark comparison]
SPEAKER NOTES: "The challenge isn't just the process — it's what the process costs..."

---

### Section 4: Resolution (Slides [X]-[Y])

SLIDE [N]: [The Proposed Solution]
TYPE: Story / Architecture
HEADLINE: "[What changes with Salesforce]"
VISUAL: [Solution overview diagram or key capability visual]
SPEAKER NOTES: "Here's what this looks like in practice..."

SLIDE [N]: [Customer Proof]
TYPE: Story
HEADLINE: "[Outcome a similar customer achieved]"
VISUAL: Quote card, metrics, or case study summary
SPEAKER NOTES: "[Customer name] was in a similar position. They saw [result] in [timeframe]."

---

### Section 5: Close (Last 1-2 Slides)

SLIDE [N]: [Summary and Value]
TYPE: Data
HEADLINE: "[The one-sentence value statement]"
VISUAL: 3 bullet outcomes or ROI summary
SPEAKER NOTES: "To summarize: [Situation]. [Complication]. With Salesforce, [Resolution]."

SLIDE [N]: [Call to Action]
TYPE: Close
HEADLINE: "[The specific decision or action you're asking for]"
VISUAL: Next steps with owner and date
SPEAKER NOTES: "Based on everything we've discussed, the natural next step is [X]. Does that make sense to you?"

Anti-PatternsReference

Scoring Rubric (90 Points)Reference

Cross-Skill IntegrationReference

Task	This Skill	Defer To
Build a full slide deck outline	Yes	—
Write speaker notes for each slide	Yes	—
Adapt deck structure for executive vs. technical audiences	Yes	—
Create the narrative arc for a presentation	Yes (with slides)	sf-se-storytelling for narrative-only
Write a 1-page executive summary	No	sf-se-executive-briefing
Build the demo that the deck introduces	No	sf-se-demo-scripts
Generate data visualizations inside the deck	No	sf-lwc-dataviz
Deck Type	Purpose	Typical Length	Key Difference
Discovery / First Meeting	Set context, ask questions, build relationship	5-10 slides	Ends with questions, not a pitch
Vision / Pitch	Inspire with the art of the possible	10-15 slides	Heavy on storytelling; light on technical detail
POV / Business Case	Justify investment with quantified outcomes	12-18 slides	Data-heavy; leads with ROI
Technical Deep-Dive	Align on architecture and solution design	15-25 slides	Architecture diagrams; feature depth
Executive Briefing	C-suite alignment in 20 minutes	5-8 slides	One insight per slide; no bullet lists
QBR / Business Review	Review progress and plan next period	10-15 slides	Metrics-led; forward-looking
Audience	What They Care About	Slide Style	What to Cut
CEO / C-Suite	Revenue, risk, strategic differentiation	1 idea per slide; no bullets; big numbers	Technical details, feature lists, acronyms
VP / Director	Team productivity, goals, timelines	Summary bullets; metrics; clear ask	Deep technical architecture, API details
Technical Buyer / Architect	Architecture, integration, security, scalability	Diagrams, specs, tradeoffs	Business metrics (they'll tune these out)
End Users	Ease of use, workflow impact, change management	Screenshots, workflows, before/after	Executive strategy, pricing
Mixed room	Varies — lead with business, earn technical right	Business first 2/3, technical last 1/3	Never go deep on both in the same deck
Anti-Pattern	Why It Fails	Fix
Starting with "About Salesforce" slides	No one cares about your company history before you've earned the right	Start with the customer's situation; earn the right to talk about Salesforce
Bullet-heavy slides with 8+ points	Audience reads the bullets and stops listening to you	One idea per slide; the headline is the takeaway; visuals replace text
"Any questions?" as the final slide	Passive; doesn't drive a decision	Close with a specific next step that you're recommending
Adapting a 30-slide technical deck for a C-suite meeting	Wrong content for the audience; executives disengage	Build the right deck for the room; don't reuse decks across audiences
Generic slides with no customer name or context	Shows lack of preparation; demo mode, not customer mode	Personalize at least the headline, the customer's pain points, and the proof point
Skipping speaker notes	The deck becomes a script, not a guide; presenter reads the slides	Every slide needs a clear message and a transition to the next
Building the deck before knowing the call to action	The structure lacks direction; the close is weak	Define the desired outcome before you write a single slide
Category	Points	Pass Criteria
Narrative Clarity	25	SCR arc is clear; every slide advances the story
Audience Fit	20	Depth, vocabulary, and visual style match the stated audience
Speaker Notes Quality	20	Every slide has specific guidance on what to say and how to transition
Call to Action	15	Final slide drives a specific decision or next step
Personalization	10	Customer name, industry context, and discovered pain woven throughout
Skill	When to Use It
sf-se-storytelling	Craft the narrative before building the slides
sf-se-executive-briefing	Compress the deck into a 1-page leave-behind for executives
sf-se-proof-of-value	Generate the ROI data and business case slides
sf-se-demo-scripts	Build the demo that the presentation introduces
sf-se-discovery	Use the discovery summary to personalize every slide