agentleFS
thewyattbrocatothewyattbrocato/design-and-copy-skills/skills/presentation-design/SKILL.md

presentation-design

Skill2 starsChanged 11 days agoMITView on GitHub

Use whenever a talk, slide deck, pitch, readout or other spoken presentation is being planned, structured, written, cut or reviewed, in any language and at any length - "make me a deck for...", "too many slides", "my slides are walls of text", "how should I open", "turn this report into a presentation", "cut this to ten minutes", "review my deck". Covers the audience action and the one takeaway, order and openings, slide count for the minutes, one message per slide, slide titles as claims, words per slide, data on slides, what goes in speaker notes versus a handout or appendix, and cutting to time. Not for the visual styling of one slide or page (visual-hierarchy), a chart on its own (chart-design), written documents (editing-and-cutting), or the mechanics of producing a slide file.

12 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Opening length: Default: about a quarter of a six-minute talk, sliding toward a tenth of an hour-long one.

    line 53
  2. Distinctive:

    Supporting points: Default: three. Two to five is fine.

    line 55
  3. Distinctive:

    Text size: Default: about 36 px body, 32 px floor, on a 1920-wide frame (about 28 and 24 points).

    line 58
  4. Distinctive:

    Speaker notes: Default: none unless asked.

    line 59
  5. Distinctive:

    Animation: Default: none. Change for a build that reveals items in the order the speaker says them.

    line 60
  6. Distinctive:

    Closing: Default: the last content slide holds the takeaway and the ask with owner and date, and stays up during questions.

    line 61
  7. Distinctive:

    Hard questions: Default: when a decision or Q&A is expected, name the two or three hardest questions and park a backup slide for each after …

    line 63
  8. Distinctive:

    Read only the titles in order: they give the argument and the ask.

    line 71
  9. Distinctive:

    No slide above the word cap.

    line 74
  10. Distinctive:

    Every slide supports the takeaway, or sits in the appendix.

    line 77
  11. Distinctive:

    No agenda, greeting, "thank you" or "questions" slide unless the user asked for one.

    line 78

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Presentation design

A presentation is a person talking with a screen behind them, and the screen is there to help the talk. Left alone, a model writes a document in slide form: an agenda, label titles ("Background", "Findings"), five bullets a slide, one section of the source per slide, twelve slides for a ten-minute slot, then "Thank you / Questions". This skill settles the audience action, the message, the order, the count and the home of every fact before any slide gets drawn.

Do not produce

  • An agenda, a "Welcome" or title-reading slide up front, or "Thank you" and "Questions?" as the closing slide.
  • Label titles ("Q3 results", "Next steps", "Approach") where a full-sentence claim fits.
  • A slide count with no minutes behind it, or more content slides than the time allows.
  • A live slide with more than about 50 words, or body text under 32 px on a 1920-wide frame. Not for a deck the user says will be read alone: those pages keep full sentences and the context a reader needs.
  • More than three changes, a restructure or merged slides for a request that is a quick look or a once-over of a nearly final deck.
  • Bullets that restate what the speaker will say, or a script pasted onto the slide.
  • A data table, a reference list or a derivation on a live slide.
  • A deck that copies the source document's section order or the project's chronology.
  • A closing with no ask, owner and date when a decision is wanted.
  • Speaker notes, a handout or a Q&A section nobody asked for.
  • An invented number, quote, customer or result.

When to use

Planning, outlining, writing, shortening or reviewing a deck or talk: pitches, readouts, all-hands updates, proposals to a committee, lightning talks, training decks (structure only), and turning a report or notes into something to present. Also single decisions inside one: how to open, what the last slide says, which slides to drop.

When not to use

  • How one slide looks (emphasis, spacing, type, color, grid): visual-hierarchy, spacing-and-grouping, typesetting, color-palette and layout-structure, if installed. This skill decides what goes on the slide and how many slides there are.
  • One chart's form, axes and honesty: chart-design, if installed. Here you decide whether a slide needs a chart and what its title claims.
  • Writing a single headline or line from scratch: headlines-and-leads, if installed.
  • Cutting a written document or summary: editing-and-cutting, if installed. This skill cuts decks and talks.
  • Courses, quizzes and exercises: practice-and-assessment, if installed. Screens that teach inside a product: teaching-interfaces.
  • Producing the file (PPTX, Slides, Keynote, HTML scaffolding) and delivery coaching (voice, nerves). Deliver in the format the user named.
  • A one-line fix ("shorten this title") needs only the matching check, not the whole procedure.
  • Explicit user instructions, an existing template or brand deck, and conventions the room expects (a funder's required sections, a fixed pitch order) win over every default below.

Procedure

  1. Pin the occasion. Audience (who decides, and whether the room already holds the opposite view), minutes, how it is delivered (live room, screen share, read alone later) and what they should do afterwards, as a verb: approve, choose, send, fund. "Understand" and "be informed" are not actions; name the decision the understanding serves. If a fact is missing, assume the simplest case, say so in one line and still deliver.
  2. Write the takeaway. One sentence that someone could disagree with, carrying the recommendation or the number. Every slide supports it or goes to the appendix.
  3. Declare the deck type. Live, read-alone, or both. "Both" means two artifacts, slides to speak with and a document to leave behind, not one compromise page. See notes, handouts and cutting.
  4. Set the budget. Slides from minutes, opening share, and a drop list for when time shrinks (see calls below).
  5. Order it. Default order: need, then takeaway, then two to five supporting points, then recap, then the ask. Not the order the work happened. Openings, previews and closings: story and order. For a mixed or opposed room, material bigger than the slot, or a case resting on one example or an analogy, read audience and argument first.
  6. Build slide by slide. One slide per supporting point or sub-point. Title is the claim; add the one visual (number, chart, diagram, photo, quote) and only the words that make it stand alone. Detail: slide craft. Data slides: data on slides.
  7. Move detail out. Tables, references, derivations and anything the speaker will not mention go to the appendix or handout, each fact in one place.
  8. Run the checks below. For a review, start with the title read and use reviewing a deck.

Judgment calls

  • Slide count. Default: about one content slide per two minutes, so ten minutes means roughly five content slides, with title and appendix slides outside the count. Change when slides are a single image or number (a minute or less each) or when the deck is read alone (count pages, not minutes). Always state the count and the minutes it rests on.
  • Opening length. Default: about a quarter of a six-minute talk, sliding toward a tenth of an hour-long one. Change when the room already knows the context; then open on the takeaway.
  • Opening content. Default: the need in the audience's terms, who did what, the takeaway, a spoken preview of the labels. A hook only if it is short and about the subject (a case, a number), never a joke or a show of hands. Change for bad news: still state the verdict early, but frame what is at stake and what decision is needed first.
  • Supporting points. Default: three. Two to five is fine; six or more means group them or cut. Give each a short label and reuse it in the preview, the transitions and the recap.
  • Agenda slide. Default: none; a short deck previews by voice. Change for sessions past about thirty minutes where people need to find their place, and then repeat the map only at part boundaries. The map and the title slide are the first things cut when time is short.
  • Words per live slide. Default: a claim title, one visual and under about 30 words. Past about 50 words nobody can read and listen at once; past about 75 it is a page of a document. Change for a read-alone deck: complete sentences and fuller captions are right there.
  • Text size. Default: about 36 px body, 32 px floor, on a 1920-wide frame (about 28 and 24 points); scale with the frame. If the words do not fit at that size, cut or split, never shrink.
  • Speaker notes. Default: none unless asked. When asked, write an outline per slide (the point, the number to say, the hand-off line), not a script, unless the user asked for a script.
  • Animation. Default: none. Change for a build that reveals items in the order the speaker says them; never on titles.
  • Closing. Default: the last content slide holds the takeaway and the ask with owner and date, and stays up during questions. Change when nothing is being asked; then close on the takeaway.
  • Live room. Default: the screen helps the speaker. Change for a story, a discussion or a pause, where the screen goes blank so attention returns to the speaker; over a call or in a recording never blank it, show a quiet slide tied to the moment. Charts built on screen and talks over a call: data on slides and slide craft.
  • Hard questions. Default: when a decision or Q&A is expected, name the two or three hardest questions and park a backup slide for each after the end. Skip for casual updates.

Output

Deliver the thing asked for first: the slide list (number, claim title, the one visual or content, a word count when trimming), the opening lines, the cut deck, or the rebuilt slides. Start with a line that states the minutes, the count and the takeaway when you built or cut a deck. When a count is asked for (three openings, ten slides), give exactly that. If the deck already works, say so and change little. After the work, at most two one-line notes: an assumption, or what moved to the appendix. Answer in the user's language.

Quick checks

  • Read only the titles in order: they give the argument and the ask.
  • The audience action is a verb, and the takeaway is one sentence on the first slide or in the first lines.
  • Slide count is stated and fits the minutes; the drop list names what goes first.
  • No slide above the word cap; no body text under the size floor; nothing on screen the speaker will skip.
  • Strip the speech from any slide: a stranger can still say what it shows and why it is there.
  • Tables and references live in an appendix or handout; each fact has one home.
  • Every slide supports the takeaway, or sits in the appendix.
  • No agenda, greeting, "thank you" or "questions" slide unless the user asked for one.
  • Nothing invented; placeholders are visible.
  • The plan names who decides, or says nobody does, and the order follows the room's stance.
  • A light review kept to a verdict and at most three changes; a deck read alone kept its fuller pages.

References

  • references/audience-and-argument.md: load when the room is mixed or opposed, the material exceeds the slot, or the proof is one case or an analogy.
  • references/story-and-order.md: load when planning the structure, the opening, the preview and transitions, bad news, or the close; has the order, timing shares and a worked outline.
  • references/slide-craft.md: load when writing or fixing individual slides: titles, word budget, one message, what to delete, consistency across the deck.
  • references/data-on-slides.md: load when a slide carries numbers, a chart or a table.
  • references/notes-handouts-and-cutting.md: load for speaker notes, handouts, appendices, live-versus-read decks, backup slides, and any cut to a time slot or slide count.
  • references/reviewing-a-deck.md: load when judging or fixing an existing deck ("review my slides", "why is this boring", "walls of text").

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.