Back to Details

studio-script

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Studio Script

Studio Script

Scripts that sound like the creator on their best day: short, concrete, with a hook that earns the next 30 seconds. Everything comes from their real week and their own words. Nothing is invented.
听起来像创作者处于最佳状态时写出的脚本：简短、具体，用一个 hook 抓住接下来的 30 秒。一切都来自他们真实的一周和他们自己的话。绝不凭空编造。

Before writing

编写前

Read, in this order:
  1. video-agent/voice.md
    : who they are, who they talk to, how they sound, what they believe, their proof, the ask. Missing: offer 
    /studio-setup
    (about 10 minutes, recommended), or ask 4 questions now (what they do, for whom, the language they record in, what viewers should do after watching).
  2. video-agent/swipe.md
    : hooks that worked in their niche and, on top, the "Concepts" that over-performed with their proof (from 
    /studio-script viral
    ). Every script sits on one of them (references/viral.md). Missing: run 
    /studio-script viral
    first (5 minutes); a week written without it is written blind.
  3. video-agent/audit.md
    if it exists: what works on their own account (from 
    /insta-audit
    ). Its "3 changes for next week" apply to this week's scripts, and its best topics, lengths and hook formulas come first. Their own data beats the niche's.
  4. The last 20 lines of 
    video-agent/log.md
    : topics and hook formulas already used. Never repeat a topic from the last 4 weeks unless they ask.
  5. references/viral.md, references/hooks.md, references/script-rules.md and references/humanize.md.
Talk to them in their language, and write the scripts in the language they record in.
按以下顺序阅读：
  1. video-agent/voice.md
    ：他们是谁、对谁说话、说话方式、相信什么、能证明其主张的素材，以及行动号召。缺失时：提供 
    /studio-setup
    （约 10 分钟，推荐），或现在询问 4 个问题（他们做什么、面向谁、录制时使用的语言、观众看完后应该做什么）。
  2. video-agent/swipe.md
    ：该细分领域中奏效的 hooks，以及在此基础上、带有其证据的“Concepts”中表现超额的部分（来自 
    /studio-script viral
    ）。每个脚本都要基于其中之一（references/viral.md）。缺失时：先运行 
    /studio-script viral
    （5 分钟）；未运行就写一周脚本，等于盲写。
  3. video-agent/audit.md
    （如果存在）：他们自己账号上有效的内容（来自 
    /insta-audit
    ）。其中“下周需做的 3 项调整”适用于本周所有脚本；其表现最佳的主题、时长和 hook 公式应优先使用。自己的数据胜过细分领域的数据。
  4. video-agent/log.md
    的最后 20 行：已经用过的主题和 hook 公式。除非用户要求，否则最近 4 周内不得重复主题。
  5. references/viral.md、references/hooks.md、references/script-rules.md 和 references/humanize.md。
用他们所用的语言与用户交谈，并用他们录制时使用的语言编写脚本。

Modes

模式

  • /studio-script
    → a week of scripts (default 5).
  • /studio-script <topic or idea>
    → one script.
  • /studio-script hook <script or topic>
    → the hook printer: 20 hooks from at least 10 formulas, grouped by concept of swipe.md (proven concepts first), filled with voice.md (the viewer's words, their phrases, their proof, their myths), scored, through the quality gates, best 3 on top. Each keeps its formula name, so a hook that works can be reposted with a new wording.
  • /studio-script rewrite <script>
    → their script, tightened: same content and facts, better hook, shorter lines, timing checked, humanized. Show what changed.
  • /studio-script viral [@handles or niche keywords]
    → what over-performs in their niche, measured: recent Shorts of 10 to 12 accounts scored against each account's median, the first 3 seconds of every outlier, its hook formula, and the Concepts on top of 
    video-agent/swipe.md
    (references/viral-research.md). About 5 minutes, once a month.
  • /studio-script humanize <file, script slug or pasted text>
    → any text (script, caption, description, post) made to sound like them: references/humanize.md, with its before and after score. 
    humanize check
    only reports.
For 
hook
, 
humanize
and 
viral
, skip "The week" and "The mix": read voice.md and the references, then do only that job.
  • /studio-script
    → 一周的脚本（默认 5 条）。
  • /studio-script <topic or idea>
    → 单条脚本。
  • /studio-script hook <script or topic>
    → hook 生成器：使用至少 10 种公式生成 20 个 hooks，按 
    swipe.md
    中的概念分组（优先使用已验证的概念），填入 
    voice.md
    的内容（观众用词、他们的原话、他们的证据和误区），进行评分并通过质量关卡，把最好的 3 个放在最前面。每个 hook 都保留其公式名称，这样有效的 hook 以后换一种措辞也能重新发布。
  • /studio-script rewrite <script>
    → 精简他们的脚本：内容和事实不变，hook 更好，句子更短，检查时长，并进行 humanize 润色。展示改动之处。
  • /studio-script viral [@handles or niche keywords]
    → 经实测找出其细分领域中表现超额的内容：近期 10 至 12 个账号的 Shorts，按各账号的中位数评分；每个异常表现内容的前 3 秒、其 hook 公式，以及排在 
    video-agent/swipe.md
    顶部的 Concepts（references/viral-research.md）。约 5 分钟，每月一次。
  • /studio-script humanize <file, script slug or pasted text>
    → 将任意文本（脚本、文案、描述、帖子）调整为他们的口吻（references/humanize.md），并给出润色前后的评分。
    humanize check
    只做检查报告。
对于 
hook
、
humanize
和 
viral
，跳过“本周”和“组合”：读取 voice.md 和相关参考资料，然后只完成对应任务。

1. The week

1. 本周

Ask one question: "What actually happened this week?" Give prompts so it's easy: a result (with the number), a mistake, a question a client or a follower asked, something they learned or tested, a tool they used, an opinion that came up in a conversation, something they disagree with.
Real material beats ideas, as long as it fits a proven concept. Then check what is hot today in the niche (a launch, a trend, a price change of the week): one script rides it, first in the week. If they have nothing, propose 5 topics from voice.md (beliefs, mistakes their viewer makes, proof), audit.md (their topics that over-perform) and swipe.md, and let them pick.
Then: how many videos (default 5) and is there something to promote this week (yes → one Offer video, no → none).
问一个问题：“这一周实际发生了什么？” 给出提示，让回答更容易：带数字的成果、犯过的错误、客户或粉丝提出的问题、学到或测试过的东西、用过的工具、聊天中出现的观点、不同意的事情。
只要契合一个已验证的概念，真实素材就胜过创意。然后检查该细分领域今天有哪些热门内容（新品发布、本周趋势、本周价格变化）：本周先写一条相关脚本。如果没有素材，就根据 voice.md（观点、观众会犯的错误、证据）、audit.md（他们表现超额的主题）和 swipe.md 提出 5 个主题，让用户挑选。
然后：需要多少条视频（默认 5 条），以及本周是否有要推广的内容（有 → 制作一条 Offer 视频；无 → 不制作）。

2. The mix

2. 组合

Each video gets a type. Plan the week before writing:
TypeWhat it doesDefault per week of 5
Teachone problem, one fix the viewer can apply today2
Proofa real result and what made it happen1
Storya moment, a turn, a lesson1
Opiniona position against the usual advice in the niche1
Offerthe problem, what they made for it, who it's for, the ask0 or 1, never 2
Each video also gets its offer proximity, the rung of voice.md "The ask" it points to (0 to 3, script-rules.md), following the week mix there.
Show the plan as a table (number, type, topic, concept, hook formula you'll try first, offer proximity) and let them swap before you write. Never the same hook formula twice in a row, never the same type three times in a week.
每条视频都要确定类型。写作前先规划一周：
类型作用每周 5 条的默认数量
教学（Teach）解决一个问题，并给出一个观众今天就能应用的修复方法2
实证（Proof）一个真实结果，以及促成该结果的因素1
故事（Story）一个时刻、一次转折、一条经验1
观点（Opinion）针对该细分领域中的常见建议表明立场1
Offer问题、他们为此制作了什么、适合谁、行动号召0 或 1，绝不为 2
每条视频还要确定 Offer 邻近度，即它指向 voice.md 中“The ask”的哪一级（0 至 3，script-rules.md），并遵循该文件中的每周组合。
以表格展示计划（编号、类型、主题、概念、准备优先尝试的 hook 公式、Offer 邻近度），并在开始写作前让用户调整。不得连续两次使用同一个 hook 公式，也不得一周内三次使用同一种类型。

3. Write each script

3. 编写每条脚本

  1. Aim: the concept of swipe.md it rides (with its best video and its x), the fresh news if any, the viewer it talks to, the false belief or myth it breaks (voice.md), and the ask line of its rung.
  2. 3 hooks, each from a different formula of hooks.md. Score each with the rubric in script-rules.md. Keep the best; the other two go under "Other hooks". All below 7/10: write 3 more.
  3. The on-screen hook: 6 words or fewer, shown during the first seconds. It adds to the spoken hook, never repeats it word for word.
  4. The body, from the structure of its type (script-rules.md). One sentence per line. A re-hook near the middle.
  5. The end: the ask from voice.md, said once, or a last line that loops into the first.
  6. Visual notes, apart from the spoken lines: what to show, and the 1 to 4 words worth a callout (a number, a result, a tool name).
  7. Timing: count the words, divide by their pace (voice.md, else 160 wpm). Check every beat rule in script-rules.md. Fix before showing.
  8. Facts: every number, name and result comes from voice.md or what they told you. Anything else becomes 
    {{your number}}
    , 
    {{client name}}
    , and is listed under "To fill".
  9. Humanize: run references/humanize.md on the script (steps 1 to 6, no report per script). Read it as if spoken aloud. Nothing they would never say (voice.md "Words I never use"), no em dash, no AI shape, every fact intact. Its score goes in the script's Score line.
  10. Triggers and gates: at least four triggers of script-rules.md at their place, then the four quality gates (generic, structureless, interchangeable, viral). A failed gate is a rewrite before showing.
  1. 目标：
    swipe.md
    中它所依托的概念（以及该概念的最佳视频和 x 值）、可能存在的最新动态、它对话的观众、要打破的虚假信念或误区（voice.md），以及其层级对应的 ask 台词。
  2. 3 个 hooks：每个都采用 hooks.md 中不同的公式。按 script-rules.md 中的评分标准进行评分。保留最佳的一个；其他两个放在“其他 hooks”下。如果全部低于 7/10，则再写 3 个。
  3. 屏幕上的 hook：最多 6 个词，在最初几秒显示。它是对口播 hook 的补充，绝不逐字重复。
  4. 正文：依据其类型的结构编写（script-rules.md）。每句一行。中段附近安排一个 re-hook。
  5. 结尾：按照 voice.md 说出 ask，只说一次；或者用最后一句回环到开头。
  6. 视觉提示：与口播台词分开：展示什么，以及值得用字幕突出显示的 1 至 4 个词（数字、结果、工具名称）。
  7. 时长：数出词数，除以其语速（voice.md，否则为 160 wpm）。检查 script-rules.md 中的每条节拍规则。展示前先修正。
  8. 事实：每个数字、名称和结果都来自 voice.md 或他们提供的信息。其他内容一律写成 
    {{your number}}
    、
    {{client name}}
    ，并列在“To fill”下。
  9. Humanize：对脚本运行 references/humanize.md 中的流程（步骤 1 至 6，不为每条脚本单独生成报告）。像朗读出来一样读一遍。不要出现他们绝不会说的话（voice.md 中的“Words I never use”），不使用破折号，不使用 AI 式句型，所有事实保持不变。其分数写入脚本的 Score 行。
  10. Triggers 和质量关卡：在各自对应的位置至少使用 4 个 script-rules.md 中的 triggers，然后通过四项质量关卡（generic、structureless、interchangeable、viral）。任何一项关卡未通过，都要先重写再展示。

4. Format

4. 格式

Save to 
video-agent/scripts/week-YYYY-MM-DD.md
(the Monday of the week). One file per week; a single script goes into the current week's file.
markdown
undefined
保存到 
video-agent/scripts/week-YYYY-MM-DD.md
（该周的周一）。每周一个文件；单条脚本则写入当前周的文件。
markdown
undefined

Week of 2026-10-05

Week of 2026-10-05

#SlugTypeFormulaOfferLength
1hooks-too-longTeachThe mistake040 s
#SlugTypeFormulaOfferLength
1hooks-too-longTeachThe mistake040 s

1. hooks-too-long

1. hooks-too-long

On screen: Your hook is too long Hook: Your first sentence has 20 words. Nobody hears word 12.
script
Your first sentence has 20 words. Nobody hears word 12.
By then, most people already swiped.
I checked my last {{number}} shorts.
The ones that held past 3 seconds had short hooks.
Under 12 words, with the topic in the first 5.
Here's the part everyone skips.
Cutting is easy, picking the one point is the hard part.
So write your hook, then cross out everything before the point.
"In this video I'll show you how to write better hooks."
Becomes: "Your hook is too long."
Same idea, half the words, and it lands before they swipe.
Try it on your next three videos.
Follow for one script fix a day.
Visual notes
  • line 1 → callout: 20
  • line 5 → callout: 12 words
  • line 9 → show: the long hook, crossed out
Ask: Follow for one script fix a day.
Other hooks
  • (Stop / start) Stop explaining in your hook. Start with the result.
  • (Their words) "My hook is fine, it's the algorithm."
Triggers: gap 0s, self-recognition 0s, proof 6s, pattern break 20s, specificity 28s Score: hook 8/10 · human 10/10 · 111 words · 40 s at 165 wpm · offer 0 · gates ✓ To fill: {{number}}

The `script` block holds only the spoken lines: the creator reads it while recording, and short-editing reads it to edit.

Then show a READY summary and wait:

```text
READY · week of 2026-10-05 · 5 scripts (Teach, Proof, Story, Opinion, Teach) · 38 to 52 s
Saved: video-agent/scripts/week-2026-10-05.md
To fill: 3 placeholders
Reply yes to log them, or tell me what to change.
```

After a yes, add one line per script to `video-agent/log.md`:

```text
2026-10-05 | hooks-too-long | Teach | The mistake | why long hooks lose viewers
```
On screen: Your hook is too long Hook: Your first sentence has 20 words. Nobody hears word 12.
script
Your first sentence has 20 words. Nobody hears word 12.
By then, most people already swiped.
I checked my last {{number}} shorts.
The ones that held past 3 seconds had short hooks.
Under 12 words, with the topic in the first 5.
Here's the part everyone skips.
Cutting is easy, picking the one point is the hard part.
So write your hook, then cross out everything before the point.
"In this video I'll show you how to write better hooks."
Becomes: "Your hook is too long."
Same idea, half the words, and it lands before they swipe.
Try it on your next three videos.
Follow for one script fix a day.
Visual notes
  • line 1 → callout: 20
  • line 5 → callout: 12 words
  • line 9 → show: the long hook, crossed out
Ask: Follow for one script fix a day.
Other hooks
  • (Stop / start) Stop explaining in your hook. Start with the result.
  • (Their words) "My hook is fine, it's the algorithm."
Triggers: gap 0s, self-recognition 0s, proof 6s, pattern break 20s, specificity 28s Score: hook 8/10 · human 10/10 · 111 words · 40 s at 165 wpm · offer 0 · gates ✓ To fill: {{number}}

`script` 块只包含口播台词：创作者录制时照着朗读，`short-editing` 则读取它进行剪辑。

然后显示 READY 摘要并等待：

```text
READY · week of 2026-10-05 · 5 scripts (Teach, Proof, Story, Opinion, Teach) · 38 to 52 s
Saved: video-agent/scripts/week-2026-10-05.md
To fill: 3 placeholders
Reply yes to log them, or tell me what to change.
```

收到 yes 后，在 `video-agent/log.md` 中为每条脚本添加一行：

```text
2026-10-05 | hooks-too-long | Teach | The mistake | why long hooks lose viewers
```

5. Hand off

5. 交接

Show the week's table and the first script in full, then ask what to change. Next steps: record each script (phone, camera or webcam, one take per script, into 
video-agent/takes/<slug>.mp4
), then 
/short-editing <slug>
, then 
/publish <slug>
.
展示本周表格和第一条脚本的完整内容，然后询问用户想改什么。后续步骤：录制每条脚本（手机、相机或摄像头，每条脚本一次录完，保存到 
video-agent/takes/<slug>.mp4
），然后运行 
/short-editing <slug>
，再运行 
/publish <slug>
。

Honest limits

诚实的限制

  • A strong script is not a promise of views. Topic, timing, delivery and luck matter as much.
  • The hook score is a writing checklist, not a prediction.
  • Scripts only sound like the creator when voice.md has their real words. A thin voice file gives generic scripts: update it.
  • 好脚本并不承诺播放量。主题、时机、表达和运气同样重要。
  • hook 分数是写作检查表，不是预测。
  • 只有当 voice.md 中有创作者的真实原话时，脚本才会像创作者本人。内容单薄的 voice 文件只能产出泛泛的脚本：应更新它。