Skip to main content
skill CX Codex

presentation-notes — Claude Code skill: speaker notes and setup

presentation-notes turns your deck into scannable speaker prompts — a key idea, an opener, a few bullets to talk around and a bridge per slide.

MIT 134 installs ★ 17 updated 2026-02-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add aaronvanston/skills-presentations --skill presentation-notes -a claude-code
Open on GitHub

What presentation-notes does

Give it your slides and it returns a short block for each one: the single idea worth remembering, an opening line, prompts to talk around, and a bridge to what comes next. Blocks are built to be glanced at mid-talk, not read out loud.

Slide type changes the advice. On a question slide it tells you to hold the pause before answering. Data slides get a nudge to explain what the numbers mean, and dividers stay brief. Delivery cues appear where they matter, like a marked pause or a good spot to ask whether anyone has questions yet.

The audience shapes the tone. Internal notes can be blunt and lean on shared history; investor or customer decks build the case before the conclusion. Recorded and async runs get denser notes with clearer cues for where each section is heading. Want a script you can read word for word? This produces the opposite on purpose.

What it helps with

  • write notes for every slide before a talk
  • turn a written script into prompts you can ad-lib from
  • prepare talking points for a numbers slide
  • trim notes for a recorded session
  • bridge sections with a one-line transition

Example prompts for the agent

  • Write speaker notes for my slides about the product launch, the audience is customers.
  • Give me talking points for the revenue slide, bullets I can riff on.
  • Make the notes tighter for a recorded demo and mark the transitions between sections.

How to install presentation-notes

1Skills CLI (Vercel)

npx skills add aaronvanston/skills-presentations --skill presentation-notes -a claude-code

2Manually: put the files in place

~/.claude/skills/presentation-notes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/presentation-notes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about presentation-notes

How do I install presentation-notes in Claude Code?

Run npx skills add aaronvanston/skills-presentations --skill presentation-notes -a claude-code. The skill lands in ~/.claude/skills/presentation-notes/SKILL.md.

What does presentation-notes do?

It writes a key idea, an opening line, talk-track prompts and a transition for each slide. You get cues to improvise from instead of a script.

Does it handle different slide types differently?

Yes. Question slides get a pause before the answer, data slides ask you to explain what the figures mean, and recap slides should not repeat the deck.

Source text

SKILL.md · MIT
---
name: presentation-notes
description: Generate speaker notes and talking points for conversational, off-the-cuff delivery. Creates scannable prompts designed for riffing — not scripts to read. Use when asking "write speaker notes for...", "talking points for...", "what should I say on this slide...", or when preparing to present a deck live.
---

# Presentation Notes

Generate speaker notes designed for natural, conversational delivery — not scripts to read verbatim.

## Philosophy

- **Riff from headlines** — the slide is the prompt, not the script
- **Add context verbally** — explain the "why" that isn't on screen
- **Tell stories** — concrete examples land better than abstractions
- **Acknowledge the room** — react to the audience, don't just broadcast
- **Land the key point** — each slide has ONE thing to remember

## Note Format

Speaker notes should be **scannable prompts**, not paragraphs.

### Per-slide structure:
```markdown
## Slide: [Headline]

**Key point:** [The ONE thing they must remember]

**Open with:** [First sentence or hook]

**Talk track:**
- [Bullet prompt 1]
- [Bullet prompt 2]
- [Bullet prompt 3]

**Transition:** [Bridge to next slide]
```

### Example:
```markdown
## Slide: Speed is a feature

**Key point:** Being fast isn't just nice — it's a competitive advantage.

**Open with:** "This slide captures something we keep rediscovering..."

**Talk track:**
- Every time we ship faster, customers notice and tell us
- Our competitors take months for changes we do in days
- Speed compounds — fast shipping builds momentum and morale

**Transition:** "So how do we protect that speed as we scale? That's what this next section is about..."
```

## Notes by Slide Type

**Statement slides** — Focus on the story behind the statement: what led to this conclusion, what's the implication, why does it matter?

**Question slides** — Pause and let it land. Don't rush to answer your own question. Acknowledge the tension, then bridge to your answer.

**Data slides** — Contextualize the numbers: what story does the data tell? What surprised you? What would be concerning if different?

**Section dividers** — Keep it brief: quick framing of what's coming and how it connects to what came before.

**Recap slides** — Don't re-present. Touch each point quickly, add one synthesis insight, set up the "so what."

## Delivery Cues

When relevant, include delivery notes:
```markdown
**Delivery:**
- [PAUSE] after the question, let it land
- Scan the room before transitioning
- Good moment for: "Questions so far?"
```

## Context Adjustments

**Internal (team/company):** More informal, reference shared history, challenge directly, be candid about what's hard.

**External (investors/customers):** Build credibility first, prove before concluding, leave room for questions.

**Recorded/async:** Tighter, less tangential, stronger signposting and transitions.

© aaronvanston · MIT · aaronvanston/skills-presentations

Similar skills

All skills for Writing and docs →

From the same set5

Project sponsors

Companies that keep this analytics open