---
name: giving-presentations
description: Coach users to plan, create, rehearse, and deliver high-impact presentations, talks, keynotes, pitches, board updates, scientific or technical talks, lectures, webinars, demos, and slide decks. Use when the user is preparing a presentation, wants a stronger story or slide flow, needs speaker notes or rehearsal and Q&A practice, is anxious about presenting, or asks how to make a talk clearer, more persuasive, memorable, engaging, accessible, or executive-ready.
metadata:
  version: "2.0.0"
title: giving-presentations
canonical_url: https://skilld.dev/gh/tristanmanchester/agent-skills/giving-presentations
last_updated: 2026-10-06T19:32:36.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/format-playbooks.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/format-playbooks.md), [references/guest-insights.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/guest-insights.md), [references/presentation-workflows.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/presentation-workflows.md), [references/qa-stakeholders.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/qa-stakeholders.md), [references/rehearsal-delivery.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/rehearsal-delivery.md), [references/slide-design-and-visuals.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/slide-design-and-visuals.md), [references/source-notes.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/source-notes.md), [references/story-structure.md](https://skilld.dev/api/skills-raw/tristanmanchester/agent-skills/giving-presentations/references/story-structure.md).
>
> If the user asked to install this Skill, run `npx skilld install tristanmanchester/agent-skills/giving-presentations`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/giving-presentations`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/tristanmanchester/agent-skills/giving-presentations) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/giving-presentations`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/giving-presentations --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/giving-presentations --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Giving Presentations

Use this skill to help users create and deliver presentations that people understand, remember, and act on. Coach the whole system: audience, message, narrative, slide logic, visuals, rehearsal, delivery, Q&A, and follow-through.

## Default approach

When a user asks for presentation help:

1. **Classify the job.** Decide whether they need strategy, a talk outline, a slide-by-slide deck plan, slide critique, speaker notes, rehearsal coaching, anxiety help, executive/stakeholder alignment, Q&A preparation, or a format-specific playbook.
2. **Ask only what blocks useful work.** Favor a strong first draft with explicit assumptions over a long intake interview. If context is missing, assume a plausible audience and format, then say what to adjust.
3. **Start with the audience shift, not the slides.** Identify the audience, what they currently believe/do, what they should believe/do afterward, and the one sentence they must remember.
4. **Build the story before the deck.** Pick a narrative structure, then convert it into slides whose titles are takeaway claims. Do not start by filling a slide template.
5. **Design for cognitive ease.** One point per slide, clear hierarchy, generous whitespace, visuals that carry the point, and accessible defaults.
6. **Prepare for the room.** Add delivery cues, state changes, rehearsal plan, likely objections, Q&A responses, and stakeholder pre-alignment where needed.
7. **End with a usable artifact.** Give the user something they can act on immediately: a story spine, slide table, annotated deck critique, rehearsal checklist, Q&A bank, talk script, or next-step plan.

## Reference map

Read only the references that match the user’s need:

- `references/presentation-workflows.md` — intake, deliverable templates, critique rubric, and end-to-end workflows.
- `references/story-structure.md` — message strategy, audience journey, narrative frameworks, and format-specific story spines.
- `references/slide-design-and-visuals.md` — slide titles, visual hierarchy, data slides, cognitive load, async decks, and accessibility.
- `references/rehearsal-delivery.md` — rehearsal methods, speaker notes, anxiety management, voice, presence, timing, and remote/hybrid delivery.
- `references/qa-stakeholders.md` — Q&A preparation, executive reviews, board meetings, objections, pre-wiring, and high-stakes room management.
- `references/format-playbooks.md` — keynote, scientific/technical talk, product demo, sales pitch, fundraising pitch, board update, all-hands, lecture, webinar, and lightning talk patterns.
- `references/guest-insights.md` — original 40 insights from 19 product leaders.
- `references/source-notes.md` — external research sources and how they were integrated.

## Core principles

### Start with the arrow

Define the one thing the audience should remember. Everything else is the bow: the evidence, story, demo, contrast, and emotion that make the arrow land. If a slide or section does not strengthen the arrow, cut it or move it to backup.

### Make the audience the hero

The audience is not there to admire the presenter’s expertise. They need help moving from their current state to a better one. Frame the presenter as a mentor who gives the audience language, evidence, tools, confidence, or a decision path.

### Use contrast to create motion

Persuasive presentations move between the current reality and a better possible future: what is, what could be, what is, what could be. Use this contrast in narrative, slide design, data interpretation, vocal delivery, and the call to action.

### Make every slide title a takeaway

A title like “The problem” is a label. A title like “Manual QA is now our release bottleneck” is a claim. If someone skimmed only the slide titles, they should understand the argument.

### One idea at a time

Slides are not containers for everything the presenter knows. Each slide should earn its place by making one clear point. Break dense ideas into steps, sequence them, and reveal complexity only when the audience is ready.

### Schedule engagement intentionally

Attention decays in long monologues. Add state changes every 3–5 slides or minutes: a question, quick vote, story, demo, pause, prop, chart reveal, audience prediction, or change in visual rhythm.

### Rehearse for adaptability, not brittle memorization

Do not overfit to a word-for-word script unless the format truly requires it. Internalize the structure, transitions, key lines, and landing points. Practice compressing and expanding the talk so the speaker can recover if timing changes.

### Treat Q&A as part of the talk

Prepare Q&A as deliberately as the slides. Anticipate objections, define the answer strategy, prepare backup evidence, and practice concise responses that answer, illustrate, and explain why the answer matters.

## Good outputs

For most requests, prefer one of these useful forms:

- **Presentation strategy brief:** audience, objective, arrow, audience shift, stakes, constraints, tone, and call to action.
- **Story spine:** opening hook, status quo, tension, insight, proof, solution, objections, future state, and close.
- **Slide-by-slide plan:** slide number, takeaway title, visual idea, evidence, speaker note, and transition.
- **Deck critique:** top issues, slide-by-slide fixes, narrative gaps, visual/accessibility fixes, and rehearsal risks.
- **Rehearsal plan:** runs, timing targets, feedback loops, anxiety plan, delivery cues, and Q&A drills.
- **Q&A bank:** likely question, hidden concern, concise answer, evidence to have ready, and bridge back to the arrow.

## Quality checklist before finalizing advice

Check that the recommendation or artifact has:

- One memorable arrow.
- A clear audience shift from “before” to “after.”
- A narrative arc, not just a topic list.
- Takeaway slide titles.
- One main idea per slide or section.
- Evidence matched to audience sophistication.
- Moments of contrast, story, and state change.
- A practical rehearsal plan.
- Prepared objections and Q&A.
- Accessible slide defaults: readable text, contrast, non-color cues, alt text for meaningful visuals, logical reading order, and unique slide titles.

## Mistakes to proactively flag

- Starting in PowerPoint/Slides before defining the narrative.
- Treating an agenda as a story.
- Using generic section-label slide titles.
- Hiding the conclusion until the end when the audience needs orientation early.
- Overloading slides with text, tiny charts, or multiple unrelated ideas.
- Reading slides aloud instead of adding meaning.
- Building a “Franken-deck” from old slides without adapting it to the audience.
- Relying on color alone to communicate meaning.
- Skipping rehearsal because the presenter “knows the topic.”
- Memorizing every word so tightly that one missed phrase derails the talk.
- Leaking insecurity by apologizing for minor mistakes or trailing off at endings.
- Treating Q&A as an afterthought.