agentleFS
shangyiyshangyiy/life-kit/skills/presentation/make-presentation-slide/SKILL.md

make-presentation-slide

Skill10 starsChanged 6 days agoMITView on GitHub

Design a presentation that teaches one coherent argument, not a collection of facts. Use when the user wants claim-title slides or runs /make-presentation-slide.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Start by finding the single thesis of the talk.

    line 10
  2. Distinctive:

    Prefer deleting over adding.

    line 26
  3. Distinctive:

    Every section should answer the question naturally created by the previous section.

    line 32
  4. Distinctive:

    When reviewing a deck, focus on:

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Good presentations change how the audience thinks.

Start by finding the single thesis of the talk. Everything should support that thesis.

Organize the presentation as one logical chain. Each slide should answer the question naturally created by the previous slide. If a slide can move without changing the story, the structure is probably weak.

Each slide should contain one idea only.

Use this structure:

  • Title — a complete assertion (not a topic).
  • Evidence — the minimum needed to support that assertion:
    • one picture,
    • one diagram,
    • one table,
    • or a few bullets.
  • Transcript — bridges the logical gap to the next slide. Put explanations here instead of on the slide.

Prefer deleting over adding. Most slides improve when they contain less.

Examples, stories, workflows, and demos are evidence—not the main message. Ask whether each one proves the slide's claim. Remove anything that does not.

Images should make the claim understandable within a few seconds. Avoid decorative artwork. If a table or diagram already communicates the idea, another hero image is usually unnecessary.

Every section should answer the question naturally created by the previous section.

When reviewing a deck, focus on:

  1. Is there one clear thesis?
  2. Does every slide advance the argument?
  3. Does each title make exactly one claim?
  4. Does the evidence actually prove the title?
  5. Are explanations kept in the transcript instead of the slide?
  6. Could two adjacent slides be merged?
  7. Does the ending return to the thesis rather than introduce a new idea?

A presentation is successful when the audience can reconstruct the entire argument from the slide titles alone.

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.