scriptwriting

脚本创作

概述

这项技能提供了多种框架和方法，帮助创作引人入胜的脚本，让内容听起来自然、能在情感上吸引受众，并能通过教育视频、叙事电影等多种媒介有效传递信息。

脚本类型决策树

确定合适的脚本创作方法：

What type of script are you creating?
├── EDUCATIONAL/INSTRUCTIONAL
│   ├── Video Tutorial → Use "Educational Video Script"
│   ├── Course Lecture → Use "Lecture Script Format"
│   └── Training Module → Use "Instructional Design Script"
├── PRESENTATION/BUSINESS
│   ├── Keynote/TEDx → Use "Presentation Script"
│   ├── Pitch Deck → Use "Pitch Script Format"
│   └── Webinar → Use "Webinar Script Structure"
├── NARRATIVE/CREATIVE
│   ├── Documentary → Use "Documentary Script"
│   ├── Short Film → Use "Narrative Script Format"
│   └── Commercial → Use "Commercial Script"
└── AUDIO/PODCAST
    ├── Interview → Use "Interview Script Framework"
    ├── Solo Episode → Use "Podcast Monologue"
    └── Narrative Audio → Use "Audio Drama Format"

脚本创作核心原则

口语与书面语的区别

脚本与书面散文有本质区别，因为脚本是供人听的，而不是供人读的。请遵循以下原则：

1. 为听觉而写

   • 句子要短（理想情况下为 10-15 个词，最多 20 个词）
   • 除非需要使用专业术语，否则使用简单词汇
   • 只使用主动语态（除非为了特定效果，否则不使用被动语态）
   • 在自然适用的地方使用缩略形式

2. 自然的口语模式

   • 自然情况下可以使用不完整句
   • 适当加入重新起句和自我修正（少量使用）
   • 使用对话式插话，并直接与听众交流
   • 变换节奏，避免单调

3. 清晰胜过巧妙

   • 每句话只表达一个想法
   • 清楚地提示转折
   • 自然地重复重点
   • 避免使用指代不明的代词

避免 AI 脚本模式

脚本中绝不要使用以下表达：

• “Let's delve into...” → “Let's look at...” 或直接切入主题
• “In today's video...” → 直接进入内容
• “Without further ado...” → 完全删掉
• “Comprehensive guide...” → “Complete guide...” 或明确说明
• 三段式模式 → 变换列表长度
• 长破折号 → 使用停顿或另起一句

教育视频脚本

结构框架

开场钩子（0:00-0:10）

从以下模式中选择一种开场：

• 问题式钩子：提出观众心中确切的问题
• 问题式钩子：展现观众正在经历的困扰
• 结果式钩子：展示观众最终能达成的状态
• 故事式钩子：用简短的轶事引出课程内容

示例：

[WRONG - AI Pattern]
"Welcome to today's comprehensive tutorial where we'll delve into 
the fascinating world of Python programming."

[RIGHT - Natural]
"Your Python code keeps crashing with mysterious errors? 
In the next five minutes, you'll know exactly how to debug them."

内容承诺（0:10-0:20）

明确说明观众将学到什么或达成什么：

"By the end of this video, you'll be able to:
- Read Python error messages like a pro
- Use three debugging tools that save hours
- Prevent these errors from happening again"

内容讲解（主体部分）

渐进式揭示模式：

1. Context Setting (Why This Matters)
   "Here's why this breaks most people's code..."
   
2. Core Concept Introduction
   "The key insight is actually simple..."
   
3. Concrete Example
   "Let me show you exactly what I mean..."
   
4. Guided Practice
   "Now you try. Pause here and..."
   
5. Common Pitfalls
   "Watch out for this mistake..."
   
6. Advanced Application
   "Once you master the basics..."

有效的过渡

避免公式化的过渡，改用：

[SCENE CHANGE]
"Now here's where it gets interesting..."
"But wait - there's a problem..."
"OK so that handles X. What about Y?"
"You might be thinking... [address objection]"

教育脚本模板

教程脚本（5-10 分钟）

[HOOK - 10 seconds]
"[Problem statement or intriguing question]"

[PROMISE - 10 seconds]
"I'll show you [specific outcome] in [timeframe]"

[PROOF - 15 seconds]
"[Credibility statement or quick demo of result]"

[PART 1: FOUNDATION - 2 minutes]
- What is [concept]?
- Why does it matter?
- When do you use it?

[PART 2: DEMONSTRATION - 3 minutes]
- Step-by-step walkthrough
- Visual callouts
- Pause points for practice

[PART 3: PRACTICE - 2 minutes]
- Exercise for viewer
- Common mistakes to avoid
- Verification of success

[WRAP-UP - 30 seconds]
- Recap key points (not three!)
- Next steps
- Call to action

讲座脚本（20-45 分钟）

[OPENING CONTEXT - 2 minutes]
- Connect to previous knowledge
- State learning objectives
- Preview structure (not agenda)

[CONCEPT BLOCKS - 5-7 minutes each]
Block Structure:
1. Introduce concept
2. Explain with analogy
3. Show concrete example
4. Check understanding
5. Bridge to next concept

[SYNTHESIS - 3 minutes]
- Connect all concepts
- Show complete picture
- Real-world application

[CLOSING - 2 minutes]
- Key takeaways
- Assignment/practice
- Preview next session

演讲脚本

主题演讲/TEDx 结构

开场（前 30 秒）

绝不要这样开场：

• “Thank you for having me”
• “I'm honored to be here”
• “Today I want to talk about”

改用以下方式开场：

• 发人深省的陈述
• 令人惊讶的统计数据
• 个人故事片段
• 反直觉的论点

主线

每场演讲都需要一个核心信息。所有内容都应围绕它展开。

结构：

1. SETUP (20% of time)
   - Establish the problem/opportunity
   - Make it personal to audience
   - Plant the seed of your idea

2. CONFRONTATION (60% of time)
   - Challenge conventional thinking
   - Present your core insight
   - Support with evidence/stories
   - Address objections

3. RESOLUTION (20% of time)
   - Show the new possibility
   - Give concrete next steps
   - End with memorable callback

推介脚本格式

一分钟推介

[PROBLEM - 15 seconds]
"You know how [target audience] struggles with [specific problem]?"

[SOLUTION - 15 seconds]
"We've built [solution] that [key benefit]."

[PROOF - 15 seconds]
"We've already [evidence of traction/validation]."

[ASK - 15 seconds]
"We're looking for [specific request] to [specific outcome]."

叙事脚本

短篇内容的三幕结构

第一幕：铺垫（25%）

• 建立日常状态
• 引入人物/情境
• 引发事件
• 确立利害关系

第二幕：冲突（50%）

• 情节逐步推进
• 障碍与尝试
• 中点反转
• 至暗时刻

第三幕：收束（25%）

• 高潮
• 余波
• 新常态
• 主题收束

纪录片脚本格式

[SCENE HEADING]
Location - Time

[NARRATION]
Write narration in normal paragraph form.
Keep sentences short. Make points clear.

[INTERVIEW SEGMENT]
SUBJECT NAME:
"Direct quote from interview transcript."

[B-ROLL NOTES]
Describe supporting visuals needed.

[LOWER THIRD]
Name, Title/Context

[TRANSITION]
Description of how to move to next segment.

播客/音频脚本

单人节目结构

[COLD OPEN - 30 seconds]
Hook with best moment/insight from episode

[INTRO - 30 seconds]
"Welcome back to [show]. I'm [host].
Today: [one sentence description]."

[SETUP - 2 minutes]
- Context for topic
- Why it matters now
- What you'll learn

[MAIN CONTENT - Varied]
Segment 1: [7-10 minutes]
- Main point
- Supporting stories
- Examples

[BREAK/TRANSITION]
"Quick note about [sponsor/announcement]"

Segment 2: [7-10 minutes]
- Second point
- Deeper dive
- Practical application

[CONCLUSION - 2 minutes]
- Synthesis
- Key takeaway
- Call to action

[OUTRO - 30 seconds]
"Thanks for listening. See you next [frequency]."

访谈脚本框架

[PREP NOTES]
Guest: [Name]
Topic: [Specific focus]
Goal: [What listeners should learn]

[INTRODUCTION OF GUEST]
Don't read bio. Instead:
"Today I'm talking with [name] who [relevant credibility].
[Name], [engaging first question]?"

[QUESTION FLOW]
Opening: Permission to be personal
"Before we dive into [expertise], can you tell us..."

Expertise: Get specific
"Walk me through exactly how you..."

Challenge: Create tension
"What's the biggest misconception about..."

Story: Make it real
"Can you share a time when..."

Future: Look ahead
"Where do you see this going..."

Closing: Give value
"If people remember one thing..."

声音与语气指南

根据目的调整语气

教育类语气

• 鼓励但不居高临下
• 清晰但不刻意简化
• 权威但不傲慢

示例进阶：

"This might seem complicated at first." (Acknowledge difficulty)
"Here's the simple version." (Provide access)
"Now let's add one more layer." (Build complexity)
"See? You've got it." (Affirm success)

激励类语气

• 直接但不咄咄逼人
• 鼓舞人心但不脱离现实
• 个人化但不过度分享

专业语气

• 自信但不自负
• 内容详尽但不枯燥
• 注重成果但不带推销意味

自然对话原则

真实的口语模式

少量使用：

• “Um”和“uh”，以增强真实感（每分钟最多 1-2 次）
• 自我修正：“The data shows... actually, let me rephrase that”
• 思考停顿：“...” 或 “[pause]”
• 自然强调：“This is THE key insight”

对话式衔接语

将正式的过渡语替换为：

• “所以，事情是这样的……”
• “但实际上……”
• “好了，现在……”
• “而且你猜怎么着……”
• “奇怪的地方在于……”

脚本格式规范

视频脚本格式

VIDEO                          | AUDIO
-------------------------------|----------------------------------
[Wide shot of speaker]         | SPEAKER: Welcome. Today we're 
                              | solving a problem that affects
                              | 90% of developers.
                              |
[Cut to screen recording]      | See this error message? You've
                              | probably seen it dozens of times.
                              |
[Zoom on error]               | But here's what it actually means...

双栏格式（视听脚本）

VISUAL                        | AUDIO/NARRATION
------------------------------|----------------------------------
FADE IN:                      | [MUSIC: Upbeat, fades under]
                             |
Title: "Python Debugging"     | NARRATOR: Your code is broken.
                             |
CUT TO: Screen recording     | But in the next five minutes,
showing error message        | you'll know exactly why.

标注规范

用于强调：

• 用大写字母表示喊出的词语
• 用 斜体 表示强调的词语
• 用 ... 表示停顿
• 用 — 表示被打断的话语
• 用 [方括号] 表示动作／指示

用于标注时间：

• 用 (2 beat) 表示特定停顿
• 用 [PAUSE] 表示自然停顿
• 用 // 表示对话重叠

修改与润色

朗读测试

每份脚本都必须通过朗读测试：

1. 按表演语速朗读
2. 标记绕口的部分
3. 标注换气点
4. 找出不自然的表达
5. 记录每个部分的时长

清晰度检查清单

• 每句话都能在第一次听时听懂吗？
• 技术术语在使用前都已解释吗？
• 代词的指代对象清楚吗？
• 列表长度有所变化（不总是三项）吗？
• 是否已去除行话和流行术语？

吸引力检查清单

• 是否在前 10 秒内设置了钩子？
• 是否清楚地说明了价值？
• 全文是否穿插了故事和示例？
• 节奏和能量是否有所变化？
• 是否有明确的行动号召？

自然语言检查清单

• 是否自然地使用了缩略形式？
• 句子是否都少于 20 个单词？
• 是否始终使用主动语态？
• 是否没有 AI 陈词滥调（参见参考资料）？
• 是否使用了对话式衔接语？

常见问题及规避方法

开场问题

❌ “在这份全面的指南中……” ✅ “下面介绍具体做法……”

❌ “让我们深入探索……的奇妙世界” ✅ “让我们来拆解……”或直接开始

❌ “欢迎收看新一期节目，我们将探索……” ✅ “今天：［具体主题／问题］”

过渡问题

❌ “现在，让我们进入下一个要点……” ✅ “但接下来才是有意思的地方……”

❌ “需要注意的是……” ✅ 直接说出重要内容

❌ “话虽如此……” ✅ 用“所以……”或直接开始新的话题

结尾问题

❌ “总而言之，我们已经介绍了 X、Y 和 Z……” ✅ “需要记住的关键一点是……”

❌ “希望这些内容对你有帮助……” ✅ “现在你可以……”［具体能力］

❌ “感谢收看／收听……” ✅ 以有价值的内容收尾，而不是表达感谢

资源

脚本

• scripts/script_timer.py - 计算朗读时间和语速
• scripts/dialogue_formatter.py - 为制作流程格式化脚本
• scripts/readability_scorer.py - 分析脚本的复杂程度

参考资料

• references/hooks_database.md - 100 多个经过验证的开场钩子
• references/transition_library.md - 自然的过渡语
• references/ai_cliches_to_avoid.md - 全面的 AI 表达模式清单
• references/story_structures.md - 高级叙事框架

素材

• assets/templates/video_script_template.docx - 双栏视听格式
• assets/templates/podcast_script_template.md - Markdown 格式
• assets/templates/presentation_slides.pptx - 演讲者备注模板