Back to Details

presentation-dry-run

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Presentation Dry Run

演讲预演

Purpose

目标

Help the user turn a rough presentation into a clear talk with one message per slide, a logical structure, readable figures, and realistic timing. This skill is based on the handbook's presentation standards: clarity above all, respect the audience's time, explain setup before results, and rehearse before presenting.
The output is a talk plan, slide-level issue list, and rehearsal checklist.
If the user does not have slides yet and is asking what the PPT should look like, what each page should contain, or how to create a reusable deck style, use 
research-slide-deck-builder
first.
帮助用户将粗糙的演示内容打磨成一场逻辑清晰的演讲，确保每张幻灯片传递一个核心信息、结构合理、图表可读性强，并符合实际时间安排。本Skill基于手册中的演示标准：清晰度优先、尊重受众时间、先解释实验设置再展示结果、演讲前进行排练。
输出内容包括演讲计划、幻灯片问题清单和排练检查清单。
如果用户尚未制作幻灯片，而是询问PPT的样式、每页应包含的内容或如何创建可复用的演示文稿模板，请先使用
research-slide-deck-builder
。

When to Use

适用场景

  • User is preparing a conference talk, lab meeting, group meeting, thesis defense segment, interview talk, or class presentation
  • User has slides and wants feedback
  • User needs to fit content into a strict time limit
  • User is nervous about how to explain results
  • User wants to prepare for questions
  • 用户正在准备学术会议演讲、实验室组会、团队会议、论文答辩环节、面试演讲或课堂演示
  • 用户已有幻灯片并需要反馈
  • 用户需要将内容压缩至严格的时间限制内
  • 用户对如何解释研究结果感到紧张
  • 用户希望为问答环节做准备

Workflow

工作流程

Stage 1: Define Audience and Constraints

阶段1：明确受众与约束条件

Ask:
  • Who is the audience?
  • How long is the talk?
  • What is the single message they should remember?
  • Is the goal to inform, persuade, get feedback, or defend?
  • What is the audience's expected technical background?
The same slides should not be used unchanged for a lab, conference, and committee.
询问以下问题：
  • 受众是谁？
  • 演讲时长是多少？
  • 受众需要记住的核心信息是什么？
  • 演讲目标是告知、说服、获取反馈还是答辩？
  • 受众的预期技术背景如何？
同一套幻灯片不应毫无改动地用于实验室组会、学术会议和答辩委员会。

Stage 2: Check Structure

阶段2：检查结构

Use the standard structure unless the talk has a reason to differ:
  1. Title
  2. Outline
  3. Background / motivation
  4. Problem statement
  5. Methodology
  6. Results
  7. Discussion
  8. Future work
  9. Acknowledgments
For short talks, compress sections rather than deleting context.
除非有特殊理由，否则采用标准结构：
  1. 标题页
  2. 演讲大纲
  3. 背景/研究动机
  4. 问题陈述
  5. 研究方法
  6. 研究结果
  7. 讨论分析
  8. 未来工作
  9. 致谢
对于短时长演讲，应合并压缩部分内容，而非删除必要背景信息。

Stage 3: Slide-Level Review

阶段3：幻灯片级审查

Check each slide for:
  • One main message
  • No wall of text
  • Font readable in the room or on screen
  • Figures with labeled axes and captions
  • Results connected to hypotheses
  • Slide number and references where needed
  • Visual evidence for claims
  • No unexplained abbreviations
Use the 6x6 rule as a warning signal, not as a mechanical law.
逐一检查每张幻灯片：
  • 是否仅传递一个核心信息
  • 没有大段文字堆砌
  • 字体在现场或屏幕上清晰可读
  • 图表带有标注的坐标轴和说明文字
  • 研究结果与假设相关联
  • 必要处标注幻灯片编号和参考文献
  • 论点有可视化证据支持
  • 没有未解释的缩写词
将“6x6规则”作为警示信号，而非机械遵循的定律。

Stage 4: Timing Plan

阶段4：时间规划

Create a timing budget:
  • Opening and motivation
  • Method
  • Results
  • Discussion and limitations
  • Future work
  • Buffer for questions or interruptions
If the talk is overfull, cut by removing secondary claims, not by speaking faster.
制定时间分配方案：
  • 开场与动机介绍
  • 研究方法
  • 研究结果
  • 讨论与局限性分析
  • 未来工作
  • 问答或突发情况缓冲时间
如果内容过多，应删减次要论点，而非加快语速。

Stage 5: Question Preparation

阶段5：问答准备

Prepare:
  • Three likely technical questions
  • Three likely strategic questions
  • One question the user fears
  • A calm answer for weak or negative results
  • A phrase for saying "I don't know yet" without sounding unprepared
准备以下内容：
  • 三个可能的技术问题
  • 三个可能的策略性问题
  • 一个用户最担心的问题
  • 针对薄弱或负面结果的冷静回应
  • 一句既能表达“我目前还不清楚”又不会显得准备不足的表述

Stage 6: Produce the Artifact

阶段6：生成成果文件

Save to 
~/phd-log/presentations/YYYY-MM-DD-[talk].md
.
markdown
undefined
保存至
~/phd-log/presentations/YYYY-MM-DD-[talk].md
。
markdown
undefined

Presentation Dry Run — [Talk]

Presentation Dry Run — [Talk]

Audience and goal

Audience and goal

  • Audience:
  • Time limit:
  • Goal:
  • One message:
  • Audience:
  • Time limit:
  • Goal:
  • One message:

Structure

Structure

SectionSlidesTimeNotes
SectionSlidesTimeNotes

Slide issues

Slide issues

SlideIssueFixPriority
SlideIssueFixPriority

Timing budget

Timing budget

  • Opening:
  • Background:
  • Method:
  • Results:
  • Discussion:
  • Future work:
  • Buffer:
  • Opening:
  • Background:
  • Method:
  • Results:
  • Discussion:
  • Future work:
  • Buffer:

Questions to prepare

Questions to prepare

  1. [Likely question] — [answer sketch]
  2. [Likely question] — [answer sketch]
  3. [Hard question] — [answer sketch]
  1. [Likely question] — [answer sketch]
  2. [Likely question] — [answer sketch]
  3. [Hard question] — [answer sketch]

Rehearsal checklist

Rehearsal checklist

  • Talk fits time limit
  • All figures explained before interpretation
  • Experimental setup stated before results
  • Main takeaway is repeated in closing
  • Backup slides prepared for likely questions
undefined
  • Talk fits time limit
  • All figures explained before interpretation
  • Experimental setup stated before results
  • Main takeaway is repeated in closing
  • Backup slides prepared for likely questions
undefined

Tone

语气

Be audience-aware and concise. A strong talk is not everything the user knows; it is the clearest path through what the audience needs.
贴合受众且简洁明了。一场出色的演讲并非展示用户所知的全部内容，而是为受众提供了解所需信息的最清晰路径。

What Not to Do

禁忌事项

  • Do not let the user solve timing problems by speaking faster.
  • Do not optimize slide aesthetics before the message is clear.
  • Do not allow unexplained abbreviations.
  • Do not skip rehearsal planning.
  • 不允许用户通过加快语速来解决时间问题。
  • 在核心信息明确前，不要优化幻灯片的美观性。
  • 不允许出现未解释的缩写词。
  • 不要跳过排练规划。