Directing Coincidence Trouble

Community

geegl

directing-coincidence-trouble

巧合、这个巧合太假了、怎么让转折不显得突兀、运气成分太重、天降神兵

Overview

Publisher	geegl
Repository	`directorskills`
Skill name	`directing-coincidence-trouble`
Stars	68
Forks	7
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by geegl on GitHub. Read the source before you install it.

Installation

Install the Directing Coincidence Trouble AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/geegl/directorskills/tree/main/output/books/directing-masterclass/directing-coincidence-trouble
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/geegl/directorskills/tree/main/output/books/directing-masterclass/directing-coincidence-trouble

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/geegl/directorskills.git /tmp/directorskills
mkdir -p .claude/skills
cp -r /tmp/directorskills/output/books/directing-masterclass/directing-coincidence-trouble .claude/skills/directing-coincidence-trouble

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Directing Coincidence Trouble in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Directing Coincidence Trouble on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Directing Coincidence Trouble is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

巧合制造麻烦而非解决困难

R — 原文 (Reading)

应该用巧合给角色制造麻烦，而不是帮他们脱离困境。 — Mackendrick, 第 6 章（编剧墙上的警句）, ~p.115

大多数的强情节故事都是基于因果关系来构筑的。每个事件都像一块多米诺骨牌，向前倾倒，撞倒下一块。 — Mackendrick, 第 2 章

I — 方法论骨架 (Interpretation)

巧合是叙事中最危险的工具之一。麦肯德里克给出的不是禁令（"不要用巧合"），而是一个精确的使用方向：巧合可以是因果断条上的加速器，但不能是替代品。

"制造麻烦"的巧合是指：偶然事件打断了角色原有的计划，迫使他们面对新的困境，从而推动故事进入下一阶段。比如角色在逃跑途中偶然遇到敌人——这个巧合加速了冲突，但角色如何应对仍然取决于他们自己的行动和选择。

"解决困难"的巧合是指：偶然事件直接帮助角色摆脱了困境，替代了角色自身的行动。比如角色正要失败时，一个偶然出现的贵人出手相助——这个巧合替代了角色应该付出的努力，观众会感到不满，因为结局不是角色"挣得"的，而是编剧"施舍"的。

区分标准很简单：这个巧合之后，角色面临的选择是更多了还是更少了？ 如果巧合让角色面对更复杂的局面（制造麻烦），它是好的；如果巧合让角色的困境直接消失（解决困难），它是坏的。巧合应该增加不确定性，而非消除不确定性。

A1 — 书中的应用 (Past Application)

案例 1: 闪回作为"解药"使用 (ce07)

问题: 当"现在时"的故事陷入困境、缺乏动力时，编剧用闪回把观众拉回过去来传递信息
方法论的使用: 闪回本质上是一种"时间巧合"——编剧通过跳回过去来"巧合地"发现解决当前结构困难的信息。这违反了"巧合制造麻烦而非解决困难"的原则，因为闪回是在帮编剧脱离叙事困境
结论: 闪回暂时中断了戏剧张力，如果闪回中的信息不是通过"现在"场景中角色的行动来激活的，它就只是一个暂停键
结果: 被列为反例——用时间跳跃来掩盖结构缺陷

案例 2: 多米诺因果推进法 (f11)

问题: 如何确保故事中每个事件之间有真实的因果关系？
方法论的使用: 用"因此，这一事件的结果是……"作为每个场景开头，强迫检查因果链条的完整性。巧合如果替代了"因此"的因果连接，就破坏了多米诺效应
结论: 好的故事中，每个事件是前一个事件的"结果"和下一个事件的"原因"——巧合不能替代这个"因此"关系
结果: 成为场景级别的诊断工具

A2 — 触发场景 (Future Trigger) ★

用户会在什么情境下需要这个 skill?

诊断剧本/小说中"转折太突兀"或"结局太巧"的问题
设计故事中的意外事件时，判断它应该带来麻烦还是解决问题
复盘成功产品/项目的"意外因素"，判断应归功于策略还是运气

语言信号

"这个转折太巧了 / 太假了"
"天降神兵 / deus ex machina"
"运气成分太重了"
"怎么让巧合看起来合理？"
"这个意外事件应该推动剧情还是解决问题？"

与相邻 skill 的区分

与 p06（可信的不可能优于不可信的可能）的区别：p06 处理的是"可信度"——一个设定在虚构世界内是否自洽；p15 处理的是"因果方向"——巧合应该往哪个方向发挥作用。一个巧合可以同时是"可信的"（在世界观内自洽）和"错误的"（用来解决困难而非制造麻烦）
与 f29（场景必要性检验法）的区别：f29 检验的是场景在整体结构中的位置是否不可替代；p15 检验的是场景中"巧合"元素的因果方向是否正确。一个通过 f29 检验的场景中仍可能有违反 p15 的巧合

E — 可执行步骤 (Execution)

识别故事中的巧合元素
- 完成标准：列出所有非角色主动行动导致的外部事件（偶然遇到的人、意外获得的信息、突然出现的物品等）
- 判停条件：如果找不到任何巧合元素，此方法论不适用
对每个巧合执行方向检验
- 完成标准：标注每个巧合是"制造麻烦"还是"解决困难"
- 判停条件：如果巧合直接帮助角色摆脱困境→需要修改；如果巧合让角色面对更复杂的局面→通过
对"解决困难"类巧合执行替代方案设计
- 完成标准：将巧合改写为角色主动行动的结果，或将其方向反转为"制造麻烦"
- 判停条件：改写后故事的因果链是否比原来更紧密？
检验巧合在因果链中的位置
- 完成标准：巧合之后的场景是否可以用"因此"来连接？（"因为这个巧合发生了，因此角色被迫……"）
- 判停条件：如果巧合之后的场景用"然后"连接（"巧合发生了，然后角色就……"），说明巧合替代了因果链

B — 边界 (Boundary) ★

不要在以下情况使用此 skill

喜剧类型中：喜剧天然依赖巧合来制造笑料（如误会、撞见、身份错认），对巧合的使用规则更宽松
开场铺垫阶段：故事早期用来建立世界观的巧合（如"角色偶然来到一个小镇"）通常属于"前提巧合"，不受此规则约束

作者在书中警告的失败模式

闪回作为"解药"（ce07）：用时间跳跃来掩盖结构困难，本质上是编剧用"时间巧合"来解决叙事困境。闪回中断了戏剧张力，如果其中的信息不能通过"现在"的行动来激活，它只是一个暂停键
多米诺因果链的断裂：当巧合替代了"因此"的因果连接，观众不再被"期待混杂着不确定"所驱动，而是被动地接受"然后发生了什么"。这会导致叙事动力急剧下降

作者的盲点 / 时代局限

麦肯德里克的案例全部来自经典好莱坞线性叙事传统。在现代非线性叙事（如盖·里奇的巧合喜剧、科恩兄弟的黑色幽默）中，"巧合解决困难"可以成为一种刻意的风格选择——通过展示命运的荒诞来表达主题。但即便如此，这些导演通常也会让巧合带来更深层的麻烦（如《冰血暴》中一系列巧合最终导致更大的灾难）
此原则假设观众期待"角色通过自身努力赢得结局"，但在某些文化叙事传统中（如古希腊悲剧中的"神意"、中国传统戏曲中的"天意"），外力介入被视为合法的叙事手段

容易混淆的邻近方法论

"不要用巧合"的简化理解：p15 不是禁止巧合，而是规定巧合的使用方向。完全不用巧合的故事反而可能缺乏意外性
"伏笔"与"巧合"的混淆：伏笔是提前铺垫好的因果关系，不是巧合。一个好的伏笔让观众在事后觉得"原来如此"，而巧合让观众在事后觉得"太巧了"。区分标准是：这个事件在之前是否有铺垫？

审计信息

验证通过: V1 ✓ / V2 ✓ / V3 ✓
蒸馏时间: 2026-06-06

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

test-prompts.json3 KB

Frequently asked questions

What does the Directing Coincidence Trouble AI skill do?

巧合、这个巧合太假了、怎么让转折不显得突兀、运气成分太重、天降神兵

Why use Directing Coincidence Trouble on TypingMind?

Because you install it once and use it with any model. Directing Coincidence Trouble is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Directing Coincidence Trouble in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/geegl/directorskills/tree/main/output/books/directing-masterclass/directing-coincidence-trouble. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Directing Coincidence Trouble?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Directing Coincidence Trouble?

As many as you like. As long as a model supports skills, you can use Directing Coincidence Trouble with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Directing Coincidence Trouble AI skill free?

Yes. It is published on GitHub by geegl under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Defuddle

kepano

CommunityPopular

Extract clean Markdown from HTML pages with Defuddle CLI.

Memory Reflect

Answer questions about history, habits and past decisions by reasoning over Hindsight memory. Use when asked what was decided about something, how something is usually done, what changed over time, or…

To Questionnaire

Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

Wait What

Stop. That last message did not land: re-pitch it.

Directing Coincidence Trouble

Overview