giving-presentations

refoundai/lenny-skills · updated Jun 12, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/refoundai/lenny-skills --skill giving-presentations
0 commentsdiscussion
summary

Help users craft and deliver compelling presentations using proven techniques from product leaders.

  • Guides narrative development before slide design, focusing on identifying the single takeaway the audience should remember
  • Teaches structural patterns including \"what is vs. what could be\" contrast, descriptive slide titles as conclusions, and state changes every 3-5 slides to maintain engagement
  • Covers delivery techniques: breathing exercises, maintaining eye contact, managing prese
skill.md

Giving Presentations

Help the user create and deliver compelling presentations using techniques from 19 product leaders.

How to Help

When the user asks for help with presentations:

  1. Understand the context - Ask about the audience, the stakes, the format (keynote, board meeting, all-hands), and how much time they have
  2. Start with narrative, not slides - Help them identify the one thing they want the audience to remember before touching slide software
  3. Structure for engagement - Guide them to use contrast, story, and state changes to maintain attention
  4. Prepare for delivery - Coach on rehearsal techniques, managing nerves, and physical presence

Core Principles

Start with the arrow, then build the bow

Tristan de Montebello: "Stop focusing as much on what you want to say and focus more on what you want your audience to remember. We call it the bow and arrow technique because you can only remember one thing out of a talk... The one thing is your arrow." Define a single sentence that represents the only thing you want remembered. Select anecdotes and data (the bow) that provide the tension to launch that arrow.

Use "what is vs. what could be" contrast

Nancy Duarte: "This motion of traversing between what is, what could be, what is, what could be... makes people leave their current state and long for this future state." Structure your narrative to alternate between the current flawed reality and the ideal future. End with "new bliss" - the world with your idea adopted.

Make the title the takeaway

Andy Raskin: "Replace 'The Team' with 'Our team is veterans of whatever industry.' Every single slide it's a takeaway, not a label." Slide titles should be descriptive conclusions, not generic category labels. The audience should understand the point without reading the body.

The audience is the hero, you are the mentor

Nancy Duarte: "In myths and movies, the mentor comes alongside the hero. The presenter should come alongside the audience and help them get unstuck or bring a magical tool." Treat the audience as the protagonist on a journey. Your job is to give them tools, not show off your expertise.

Schedule state changes every 3-5 slides

Wes Kao: "Every three to five slides, put in a state change. We want to turn audience engagement from an art into a science." Insert interactive elements at regular intervals. Ask the audience to guess a data point before revealing it to increase engagement.

De-risk with pre-meetings and role-play

Casey Winters: "You want to de-risk that meeting not make it a big success or fail moment... have pre-meetings with key individuals so they're less surprised." Role-play the presentation by impersonating specific stakeholders and their likely objections. Surface concerns before the formal review.

Look up when thinking, not down

Tristan de Montebello: "If you're looking down on Zoom, it looks like you're looking at your phone. If instead you think up, you actually look thoughtful by default." Direct your gaze upward when gathering thoughts. Place a "Think Up" post-it note on your monitor as a reminder.

Reframe anxiety as excitement

Matt Abrahams: "When you feel those symptoms of anxiety, say 'This is exciting. I get to share my point of view.' By seeing it as more positive, it causes us to relax." Anxiety and excitement share the same physiological response. Labeling the arousal as excitement improves performance.

Use the 1:2 breathing ratio

Matt Abrahams: "Your exhale should be twice as long as your inhale. Take a three count in, take a six count out." The physiological relaxation response is triggered during the exhale. Use a double-inhale to fully expand lungs before the long exhale.

Stay in character from start to finish

Tristan de Montebello: "Don't share your insecurities. Stay in character from beginning all the way through past the ending. Audiences rarely notice internal nervousness unless you leak it." Do not apologize for minor verbal slips or admit to being nervous. Use the internal cue "stay in it" to maintain composure.

Master the material so you don't need notes

Jeffrey Pfeffer: "I never appeared before Congress with notes. I wanted them to believe, which was true, that I was in complete control and mastery of the material." Presenting without notes signals authority. Master your material so thoroughly that you can maintain eye contact throughout.

Use the Accordion Method to internalize, not memorize

Tristan de Montebello: "Practice your talk with strict time constraints, starting at 3 minutes and working down to 30 seconds. Once you reach the essence, expand it back up." This helps you internalize key pillars rather than memorizing a word-for-word script, which can lead to catastrophic failure if you lose your place.

Questions to Help Users

  • "What's the one thing you want the audience to remember after your presentation?"
  • "Who is your audience and what do they care about?"
  • "What's the contrast between 'what is' and 'what could be' in your story?"
  • "Have you rehearsed this talk out loud? How many times?"
  • "What are the most likely objections or questions you'll get?"
  • "Where in your deck do you have state changes or interactive moments?"

Common Mistakes to Flag

  • Starting with slides instead of narrative - Open a notes app first, not PowerPoint. Define your story points before designing visuals
  • Generic slide titles - "The Problem" tells the audience nothing. "Our customers waste 4 hours per week on manual data entry" tells them everything
  • No state changes - A 30-slide monologue will lose the audience. Build in interaction every 3-5 slides
  • Over-rehearsing word-for-word - This can cause catastrophic failure if you lose your place. Internalize key pillars instead of memorizing scripts
  • Leaking insecurity - Saying "I'm nervous" or "I don't know if this makes sense" breaks character and signals uncertainty

Deep Dive

For all 40 insights from 19 guests, see references/guest-insights.md

Related Skills

  • Written Communication
  • Stakeholder Alignment
  • Running Effective Meetings
  • Fundraising
how to use giving-presentations

How to use giving-presentations on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add giving-presentations
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/refoundai/lenny-skills --skill giving-presentations

The skills CLI fetches giving-presentations from GitHub repository refoundai/lenny-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/giving-presentations

Reload or restart Cursor to activate giving-presentations. Access the skill through slash commands (e.g., /giving-presentations) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.751 reviews
  • Sophia Singh· Dec 28, 2024

    Useful defaults in giving-presentations — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Noor Reddy· Dec 28, 2024

    Solid pick for teams standardizing on skills: giving-presentations is focused, and the summary matches what you get after install.

  • Kwame Mehta· Dec 12, 2024

    Registry listing for giving-presentations matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Noor Harris· Nov 19, 2024

    giving-presentations is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ren Malhotra· Nov 3, 2024

    giving-presentations fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Layla Abbas· Oct 22, 2024

    We added giving-presentations from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Hiroshi Kapoor· Oct 10, 2024

    Keeps context tight: giving-presentations is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Diego Jackson· Sep 25, 2024

    giving-presentations is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Rahul Santra· Sep 13, 2024

    giving-presentations is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Ren White· Sep 13, 2024

    Solid pick for teams standardizing on skills: giving-presentations is focused, and the summary matches what you get after install.

showing 1-10 of 51

1 / 6