Build a deck or talk — slides for a meeting, review, training, conference or client. Use when asked to "make a presentation", structure slides, or turn a document into a talk. For investor decks use pitch-deck instead.
Installs into .claude/skills of the current project.
Are you the author of Presentation?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ivanvp91-presentation)
---
name: presentation
description: Build a deck or talk — slides for a meeting, review, training, conference or client. Use when asked to "make a presentation", structure slides, or turn a document into a talk. For investor decks use pitch-deck instead.
description_ru: Собрать презентацию или выступление — слайды для встречи, разбора, обучения, конференции или клиента. Когда просят «сделай презентацию», выстроить слайды или превратить документ в доклад. Для инвесторов — pitch-deck.
triggers: презентация, презентацию, презу, слайд, слайды, slides, deck, дек, доклад, выступление, keynote, powerpoint
---
# Presentations
## 1. Three questions before any slide
- **Audience**: who is in the room, what they already know, what they care about.
- **Decision**: what they must think, feel or approve when you finish. A deck without a decision is a document — write a document instead.
- **Format**: presented live (slides support you, few words) or sent to read (slides carry the argument, more words). These are different artefacts; do not build one and use it as the other.
## 2. Write the story first, in text
Draft the slide titles as full sentences that state the claim: "Churn comes from onboarding, not price". Read the titles in order — if that sequence alone does not make the argument, no amount of design will save it. Fix it here, where editing is cheap.
Default arc: **Situation → Complication → Question → Answer → Evidence → What we need**. Put the answer early for a senior audience; build up to it only when you must bring people along.
## 3. One idea per slide
The title is the idea. The body is the single piece of evidence for it. If a slide needs two titles, it is two slides. Six to ten words per bullet, at most four bullets — or better, replace the bullets with one chart, one image, or three words.
## 4. Numbers and charts
- One message per chart, and the message is the chart's title.
- Simplest form that carries it: line for trend, bar for comparison, single big number for a headline metric.
- Label directly instead of using a legend; drop gridlines, borders and 3D.
- Always state the source and the period. Round hard — "≈40%", not "39.7431%".
## 5. Visual discipline
Consistent template: same title position, same type scale (title / body / caption only), one accent colour, generous margins. Minimum 24pt body text for a room. Never paste a screenshot of a table nobody can read — crop to the row that matters, or restate it as a number.
## 6. Endings and appendix
Close with the ask and the next step, not "Thank you / Questions". Move backup detail, methodology and long tables into an appendix after the close — it is what makes a deck survive the Q&A.
## What not to do
- No agenda slide for a deck under ten slides.
- No wall of text read aloud.
- No animation that delays information.
- No slide you cannot explain in one sentence — cut it.
## Answer format
Slide-by-slide outline: number, sentence-title, what is on the slide, what you say. If asked to produce the deck itself, generate a self-contained HTML file with one section per slide (keyboard navigation, 16:9, the type/colour rules above) or Markdown slides — and say which tool it targets.
