sw-series-engine-bible
From an idea to a sellable series design; series engine / franchise, story pattern, character webs that keep generating conflict, pilot types, and the documents that sell them (剧集引擎/franchise/故事模式/人物网/试播集类型/剧集圣经/跳板/提案).
Install / Use
npx skills add jtydhr88/screenwriting-skills --skill sw-series-engine-bibleInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of sw-series-engine-bible
sw-series-engine-bible scores 86/100 on our quality scale, 731st of 1,153 Content & Media skills we index.
Its SKILL.md is 26 KB long, well organised into 14 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 1,376 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so sw-series-engine-bible is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
sw-series-engine-bible compared with similar skills
All 4 of these similar skills score higher than sw-series-engine-bible; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| sw-series-engine-bible (this skill)by jtydhr88 | 86 | 1.4k | 55d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
Frequently asked questions
- How do I install sw-series-engine-bible?
- Run
npx skills add jtydhr88/screenwriting-skills --skill sw-series-engine-bible. The install tabs above show the steps for each supported agent. - Which AI agents does sw-series-engine-bible work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is sw-series-engine-bible safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is sw-series-engine-bible still maintained?
- The repository was last updated about 2 months ago, so sw-series-engine-bible is actively maintained.
Skill content
View source on GitHubname: sw-series-engine-bible description: From an idea to a sellable series design; series engine / franchise, story pattern, character webs that keep generating conflict, pilot types, and the documents that sell them (剧集引擎/franchise/故事模式/人物网/试播集类型/剧集圣经/跳板/提案). Merged from Rabkin's four-element franchise and story landmines, Landau's tacit contract and pitch recipe, Oberg's series types and bible specs, Douglas's franchise-plus-springboard and bible tiers, Goldberg & Rabkin's 100-episode test, Blum's concept/presentation/bible ladder, Miller's ten-component treatment, Calvisi's Compelling Crisis, Smith's series format, plus engines read off Sopranos, Fleabag and Succession. Use when turning an idea into a series, testing whether a premise has legs, choosing premise vs typical-episode pilot, designing a sustainable character web, writing a logline, pitch document, bible or treatment, picking a series type, adapting IP into a series, or diagnosing a project that feels "more like a movie than a series".
剧集引擎与剧集圣经(Series Engine & Bible)
输出语言=提问语言;术语一律锚回原词,见 sw-workflow/terms.md,不自创译名。
管四层:引擎(凭什么每周都有故事)、人物网(冲突从哪里自动产生)、pilot 类型与策略、文档(logline → 提案 → treatment → bible)。
不管:单集与季的幕结构、页码、act out 与 cliffhanger 类型学(→ sw-series-structure);编剧室流程与 pitch 会议礼仪(→ sw-writers-room);半小时喜剧的笑点力学与人物配置(→ sw-sitcom-comedy);国产剧策划书、分集大纲、集数体量与审查(→ sw-chinese-series-practice)。前提/主控思想/三维人物/对白等媒介无关内容不在此重写(→ sw-premise-theme、sw-character-conflict)。
参考资料分三个文件:引擎拆解、剧集类型与人物网见 reference.md;文档模板的完整字段表(Rabkin 十节 pitch document、Smith series format 十一节、Oberg bible 十二组件)见 reference-documents.md;填好的样例(两份 writers’ guidelines、Miller 六份 treatment 矩阵、Succession 七个 want 表)见 reference-samples.md。
按任务读哪几节(不要通读)
本节 44 KB,规则编到 56 条,逐条读完通常是浪费。
| 任务 | 读 | 跳过 | |---|---|---| | 判断一个点子能不能做成剧 | 一(引擎定义)、二(写成句子,尤其第 8 与第 10 条的二选一) | 三–七 | | 设计人物网 | 三 | 五、六 | | 选 pilot 类型 | 四 | 三、七 | | 写 bible / pitch / series format | 六,字段表转 reference-documents.md | 一–四 | | 诊断一份已有的方案或大纲 | 九(诊断清单);改单集时整组跳过 ㉑–㉚ | 六 | | 改编 IP | 七 | 四、五 |
reference.md/reference-documents.md/reference-samples.md 都是查表用的,只在正文指向时打开。
来源与各书关系
Rabkin 给引擎原理,Landau 给字段,Oberg 给类型与规格,Douglas 给行业语汇,Goldberg/Rabkin 给工业底线,Blum 给文档层级,Miller/Calvisi/Smith 给表单,四部语料给证据。
- Rabkin《Writing the Pilot: Creating the Series》(2017):franchise 四元素、story pattern、story landmines、"问题通向 process"。
- Landau《The TV Showrunner's Roadmap》1e(2014)/2e(2022):tacit contract、central question vs mystery、micro mission、story tentacles、guideposts、11 项 pitch 配方、pilot 三分类。
- Oberg《Writing a Successful TV Series》(2023):series type 八种、story-type、Maslow 与 M-Factor、bible 规格、"别把自己 box in"。
- Douglas《Writing the TV Drama Series》3e(2011)(中译《美剧编剧入门》据第 2 版,2009):franchise+springboard、bible 三档、pilot 四步、官方中译术语。
- Goldberg & Rabkin《Successful Television Writing》(2003):franchise=规则集、原创剧四问与 100 集、两份真实 writers' guidelines(Diagnosis Murder 与 Martial Law 两份 mini-bible 的小节构成、绝不碰清单与介入授权机制见 reference-samples.md 十一)。
- Blum《电视与银幕写作》(英文 4th ed. 2001/中译 2003):concept→presentation→bible 三级、三项可卖性检验、三种网台 pilot 策略、五故事检验。
- Miller《The Hero Succeeds》(2016):treatment 10 要素+六大问、arena 先天问题、story engine=license to intervene。
- Calvisi《Story Maps: TV Drama》(2016):Compelling Crisis、Week-to-Week、17 栏 Basic Story Map。
- Smith《Writing Television Sitcoms》(2009) ch20:series format 十一节、"高管默认偏好 typical-episode pilot"。
- 语料:Sopranos 剧本集(Chase 前言+pilot)、Fleabag: The Scriptures、坂元裕二《花束般的恋爱》(电影剧本)、Succession S1–S4 剧本集。
一、引擎的定义
1. franchise=concept + conflict + theme + story pattern(Rabkin ch5、ch8)。他自评 2011 年旧版的七项清单(人物、设定、故事类型、对白风格、互动方式、叙事风格、中心冲突)像用"灰皮长鼻大耳"描述大象:给现有剧写故事时是好 checklist,不能指导你造自己的引擎。
2. theme 禁止单词,必须是可争辩的对立命题:"There is no such thing as a one-word theme for a television series."(同章)The Shield——"一个好人在行善的追求中能做多少恶,才会变成他所对抗的恶?";Mad Men——"一个人以贩卖'消费带来幸福'为业,同时知道这在自己生活里不成立";Lost——"Faith versus reason"。
3. 主题必须落成人物之间的冲突("TV doesn't handle abstract concepts too well")。The Shield 的最小配置:能对抗恶的好人+一个恶+用传统方法对抗恶并失败的其他好人(否则观众不懂主角为何改用敌人的手段)。concept 只是容器、可替换(Lost 的 concept 来自 ABC 高管)。
4. 咬合测试(Rabkin ch6):"Quick, come up with a story that naturally explores both concept and conflict. Now come up with 99 more." 反例 Agents of SHIELD:唯一的中心冲突(Skye 既反集权又乐于加入 SHIELD)在一个人内部且与 concept 无关——"you can feel its emptiness";作者自己在 NBC 首季 Baywatch 同病(有 concept 无 conflict 无 theme,"every week you are reinventing the franchise")。
5. 类比不是小说,是爵士即兴(Rabkin ch4):冲突与主题=循环的和弦(chord changes),单集=在上面即兴的新旋律。
6. 同一件事的五种行业说法
- Landau 2e ch4:pilot 是与观众的 tacit contract,每集"fundamentally the same – only different";高管问"What's the franchise?"等于问主角每周在做什么。1e Tip 3 的软概念剧公式:"Each week, the characters will struggle to achieve ______."
- Goldberg & Rabkin ch2:"It has to be the same show every week, and yet at the same time, it has to be new, fresh, and different." franchise=允许创造的规则集。反例 Stingray 每周换体裁,一位 showrunner 断言"It's got no franchise.",两个月下档。
- Douglas 3e ch1:franchise"既是边界也是机会";每集由 springboard 启动——案件类天然(罪案/委托/病人),家庭、职场、校园、爱情类必须由一个个人的(可以是内在的)inciting incident 启动。
- Oberg 3.1:"A series isn't a story that brings answers. It's a story engine that generates questions." 电影是特快列车,剧集是站站停的火车,但每集仍要交付一部电影的情节量。
- Miller ch1/Calvisi §9:引擎依赖人物有 license/agency 介入他人生活(能逮捕、能辩护、能治疗)或一个把新人物拉进主角世界的统一处境;Calvisi 的两个必填栏是 Compelling Crisis 与 Week-to-Week(电视台永远问"what does he DO each week?")。Blum ch17 给经济学理由:剧集要在屏幕上坚持三五年才有金融收益。
7. story pattern=每集重复的那个形状(Rabkin ch8):Sons of Anarchy 不是"关于摩托帮",是 Jax 要保护三个家庭——察觉威胁→出手保护→反噬危及另一个家庭。→ 一句话写出 pattern,用 pilot 的后半段完整跑一遍(前半只做设定与触发)。(Breaking Bad 的 pattern 原文、结构常量与人物模式两层、反例见 reference.md 五)
8. 五道"有没有腿"的判据:99 个故事(Rabkin ch6)/六集测试(Landau 1e Tip 7)/pitch 备三、presentation 备五六(Landau 2e ch14/Blum ch17)/100 集与四问(Goldberg & Rabkin ch17)/五故事检验(Blum ch17)。(五项的阈值、原话与出处全表见 reference.md 七)
⚠️ 限定剧、迷你剧、一次性播完的闭合长篇不跑这一条。 100 集与"能撑五季"是美国广播网续订经济学的判据;一个封闭县域、一间办公室、一桩旧案这类题材按类型数本来就撑不到 100 集,照字面跑会把合格的项目否掉。闭合长篇改用第 10 条的引擎失压测算:算出物质性引擎在第几集失压,那一集就是这部剧该结束的地方,集数由此论证出来而不是被接受。两条判据二选一,按媒介与订购方式选。
9. 概念强弱不决定可持续性:Torchwood 反证(Rabkin ch9):按 concept 一定押 Torchwood,结果它只有四季而 Doctor Who 拍到第十季——外星威胁只是 premises/pretexts,不是 stories。→ "pilot 之后想不出三集"的病灶在人物冲突,不在 concept。(全案对照见 reference.md 五)
10. 引擎失压论(Succession S4 前言):判断一部剧该不该结束,看物质性情节引擎(交易、帝国、职位),不看人物还有没有戏——Armstrong 结束该剧不是因为人物写完了("the motor in the room was still running hot"),而是"the big plot engine, the brutal materialist plumbing which ran under the show, was looking to me like it would eventually start to lose pressure"。
用法:这一条是第 8 条的替代品,不是补充。可无限续订的剧用第 8 条(能不能再跑 100 集);闭合长篇与限定剧用这一条(引擎在第几集失压)。先判断媒介与订购方式,再选判据。
四个引擎样本各一句(详解见 reference.md 五):Sopranos=治疗室+两个家庭(Melfi 开场划下的"听到谋杀要报警"这条 ethical ground rule 本身是引擎);Fleabag=一张本身就在互相伤害的人物关系网+一个装置(对镜说话);坂元《花束般的恋爱》=双主角的 want 在五年间错位、全片没有反派;Succession="继承"这个永不能解决的问题。
二、把引擎写成句子
11. 核心问题必须是过程句(Rabkin ch3):"Pilots need to raise questions that lead to processes, not solutions." 电影问"Who killed Marion Crane?";剧集问:Grantham 伯爵如何在不适合它的经济体系里保住庄园(Downton)?温和的化学老师如何在暴力的毒品生意里活下去(Breaking Bad)?Richie Finestra 能否在酒和毒品杀死他之前复兴摇滚(Vinyl)?→ 写成 "How will X keep doing Y in a world that Z?"。
12. 不要在 pilot 里把核心谜团演出来(同章,Extant 的三重错误是教科书案例):判决是 "execution is not the problem here. Conception is."(三重错误逐条见 reference.md 七)
13. Story landmines(Rabkin ch9)=pilot 潜台词里埋下、若干集后才引爆的人物冲突。→ 每个主要人物各埋一枚(未言明的恐惧/欲望/矛盾),写下预计第几集引爆;必须是人物层面——"她是警探的女儿"不算。(三条理由与 Doctor Who/Crazy Ex-Girlfriend 正例见 reference.md 七)
地雷数量与"一个总悬念"的冲突,以及解法。 八个主要人物=八枚地雷,在国产长剧里就等于八条并发谜线,而国产体系把"多谜并发"当病(见
sw-chinese-series-practice的"一个问题"格局与《皇城根儿》反例)。解法不是减少地雷,是改变它们的挂法:把全部地雷挂在同一个总悬念之下,当它的分解层,每集只揭一层,揭一层立刻补一个带时限的新悬念。于是观众追的始终是一个问题,而你仍然有八颗可定时引爆的炸药。排表时给每枚地雷写两个集号:引爆集,以及它揭开了总悬念的第几层。
14. 痛苦不是冲突;一个人的两个属性必须互相妨碍(同章,反例 Feed the Beast):"suffering isn't conflict, and so suffering alone can't drive story"。(Tommy/Dion 的逐条拆解与该剧 soap opera 化见 reference.md 七)
15. sweet spot(Landau 1e Tip 16)=类型、调性、主题、中心冲突、franchise、中心问题/谜团的交叉点;2e ch4 的公式是 sweet spot = character development × franchise,一小时剧的版本是 "a series must deliver the promise of its premise every week"——这就是 tacit contract。(原文、TWD/Homeland 范例与 currency 概念见 reference.md 七)
16. 营销实习生测试(Rabkin ch10)|可选,零成本复核,不要当一道工序——logline 写好之后再跑它,通常只是重读一遍并宣布通过;它的价值在"写 logline 的时候心里有这个读者",不在事后核对。:一句话能不能让一个初级营销人员替你向 Entertainment Weekly 要到几英寸版面。Bigger 不是预算大,是定义剧的冲突的规模。(对照实例见 reference.md 七)
17. "Big does not have to mean shallow." 三条加大法(同章):换职业(Sopranos 的起源只改了一处:职业)、换地点、换时代。反向立场(Miller ch1–2):"having great characters trumps high concept every time"。(三例全文与 Miller 的论据见 reference.md 七)
18. 记账式单元:每集"解决掉"的事,必须在后面某一集留下一笔要兑付的账。(本 pack 的推广,把 Succession S1 的季层做法下放到集层——原规则是"季终十条线全部落子,但每条落子都生成下一季的债务:Greg 的复印件、Tom 的邮轮、Roman 的过失致死、Shiv 的双重效忠",见 succession-series-writing。)
一般的案件剧到第 12 集开始重复,原因是每集结案等于清零。把"结案"改成"记账"就不会:本集签成的协议、保下的人、压住的投诉,都在账上留一个条目,由后面指定的某一集兑付。排大纲时给每条账目写成一行 第 N 集做了什么 → 第 M 集谁付账,M 必须是具体集号。一季里这样的账 6–10 笔为宜,过少则各集仍是孤岛,过多则观众记不住。
- 与"每集一案"的关系:它是单元剧与连续剧之间的第三条路——单元照旧闭合(观众每集拿到结果),但代价不闭合。
- 与 story pattern(第 7 条)的关系:story pattern 管"每集的形状重复",记账管"每集的后果积累"。两者必须同时在:只有形状没有积累=系列剧;只有积累没有形状=观众不知道每周买的是什么。
- 自检:随手指一集,说出它欠谁、谁来还、第几集还。答不出的集就是一个被清零的集。
19. 用"同一套本事的第几种用法"给长剧分段,而不是用时间顺序。(本 pack 的推广,依据 Landau 1e Tip 13 的 movement 分季法:季初只定 tent poles,把季拆成每 4–6 集一个 movement,每个 movement 一件大事。)
主角的技能不变,用法换一次就是一个段落,换几次就有几段:学着用它赢 → 一边赢一边查/一边用它办私事 → 反过来用它并引爆更大的代价 → 放弃原目标、改用它去改规则。同一个人、四种用法、四种后果,天然就是四段;24 集除以四段=每段 6 集,正好落在 movement 的 4–6 集区间里。
- 好处:段落的分界线长在人物身上,不长在日历上;而且每段的高潮是"这种用法的反噬",不需要另外设计。
- 判据:说不出某一段里主角对这套本事的用法与上一段哪里不同,这一段就是水的。
- 与季弧的关系:先定用法序列,再定 tent poles,最后才排集——顺序颠倒就会变成"先画时间表再往里填事"。
三、人物网
20. 内在冲突必须外化成一圈拉扯他的人物(Rabkin ch6)。Buffy 的"想过正常生活 vs 拯救世界"外化为母亲要她正常、watcher 要她杀吸血鬼、好友在日常世界、爱人是百年吸血鬼;SHIELD 的 Skye 反之,冲突留在一个人内部,无法产生故事。
21. 每部剧都是家庭剧(Landau 2e ch6):"Every television series is about a family – whether they're related by blood or not." 推论:所有剧中家庭都必须 imperfect 且在某个层面 discontented。(六种家庭类型与例子见 reference.md 六)
22. familial role 分配库(同章):不必凑齐性别年龄,要确定"每个人物在正面和负面两个方向上会如何对待彼此"。(角色库全表与执法搭档/职场同事的推论见 reference.md 六)
23. transactional family(Logan Roy 范式)(同章):"寻求老板认可会取代寻求父母认可——而且前者还附带薪水作为额外确认";Logan "withholding his approval and validation","His relationships with his kids are all transactional."
24. 三条场景级规则(同章):"the people who love you most know how to hurt you the most."→写两人场前先确定"他知道对方哪个按钮",再决定按不按。(新人物测试与潜文本公式原文见 reference.md 六)
25. 专长分工(Landau 1e Tip 20):不同技能组合用来制造冲突、呈现多重 POV、帮观众区分人物;Grey's Anatomy 用专科定义人物。(Breaking Bad 分工表、House 的反同意原则、Out of Their Element 生成器见 reference.md 六)
26. 理性轴(Rabkin 附录 Mooresville pitch):"start from the position that they are both rational, intelligent adults" → 关系剧的双向吸引要给结构性理由,不只是化学反应。(全案见 reference.md 六)
27. 互补双主角(Landau 1e Tip 9):"two incomplete people together you get one whole."(Mulder/Scully=信与疑。)(Hacks 的 mutual need/shame 模板与 Gomorrah 的 logline 生成器见 reference.md 六)
28. 坂元式双主角错位(《花束般的恋爱》):不靠对抗而靠体贴造成价值转折(场 85 吹头发时说"我打算找工作了")。(四对镜像人物与台词预算分配见 reference.md 五)
29. 羞耻与空洞(Landau 2e ch7,引 Brené Brown《Daring Greatly》):shame = our fear of disconnection;创伤造成 emotional voids→voids 产生回避脆弱的 coping mechanisms。"Anyone who challenges any of these constructs becomes an antagonist."(三类防御的设计菜单见 reference.md 六)
30. grounded superpower 同时是 liability(Landau 2e ch5,Gilligan 的造人法):Walt 的超能力是"自欺的能力"。1e Tip 8:"when a character's greatest strength also becomes his or her greatest liability… The trick to dramatic sustainability is keeping your main character in this form of limbo."(三例与方框全文见 reference.md 六)
31. 同一 backstory 的两次陈述(Landau 2e ch7,Mare of Easttown):先给修饰版,几集后在更安全或更被迫的场合给真版本;落差就是人物的 shame。(两段台词原文与群像配平见 reference.md 六)
32. flaw 的揭示节奏(Landau 1e Tip 8):f
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
