Dialogue Busy Hands No Eye Contact logo

Dialogue Busy Hands No Eye Contact

Community
geegl
dialogue-busy-hands-no-eye-contact

(1)演员对话时互相盯着对方眼睛不放;(2)表演感觉舞台化或不真实;(3)导演不知道如何让对话场景看起来自然

Overview

Publishergeegl
Repositorydirectorskills
Skill namedialogue-busy-hands-no-eye-contact
Stars
68
Forks
7
Bundled files
1
LicenseMIT
Links
  • 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 Dialogue Busy Hands No Eye Contact AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/geegl/directorskills/tree/main/output/books/master-shots-v2/dialogue-busy-hands-no-eye-contact
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/master-shots-v2/dialogue-busy-hands-no-eye-contact .claude/skills/dialogue-busy-hands-no-eye-contact
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dialogue Busy Hands No Eye Contact 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 Dialogue Busy Hands No Eye Contact 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 Dialogue Busy Hands No Eye Contact 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)

在现实生活中,熟人之间几乎不看对方眼睛——直接对视只有运用在刀刃上才会有令人难忘的效果。

— Christopher Kenworthy, 第9章, p.g_0031


I — 方法论骨架 (Interpretation)

对话场景中最有反直觉的两条导演原则:(1)不要让演员互相对视;(2)给演员安排具体的手头任务。

"避免对视"不是冷漠,而是还原真实——现实中熟人说话时视线是流动的(看手里的杯子、看窗外、看对方的领带),只有在情感爆发点才直视。让演员从头到尾对视会让观众感觉"假"。

"找事干"的逻辑是:当演员有具体任务(洗碗、泡咖啡、摆弄道具、弹钢琴),他们的注意力有地方放,身体语言自然流动,转身、低头、看向别处都有了叙事理由。这比"自由发挥"可靠得多。

两条原则配合使用:任务提供身体运动的理由,避免对视提供视线流动的理由。结果是看起来"不像在演"的表演。

A1 — 书中的应用 (Past Application)

案例 1: 洗碗场景

  • 问题: 两人在厨房对话,如何避免"话剧感"?
  • 方法论的使用: 让一个角色洗碗,另一个擦桌子。手头有任务→视线自然落在碗碟上→偶尔抬头对视才有冲击力
  • 结论: 有家务的对话比空手对话真实10倍
  • 结果: 观众注意力在角色的手和碗上,对视瞬间成为"事件"

案例 2: 头靠头的亲密场景

  • 问题: 新手导演拍亲密对话时让演员一直盯着对方
  • 方法论的使用: 要求演员把头靠在对方肩上——看不到对方眼睛→视线自然流动→亲密感反而更强
  • 结论: "看不见对方"比"盯着对方"更亲密
  • 结果: 演员放松,表演更自然

A2 — 触发场景 (Future Trigger) ★

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

  1. 演员对话场景表演生硬——"感觉像在演话剧"
  2. 导演不确定是否应该让演员对视——"要不要让他们看着对方?"
  3. 拍亲密/日常对话场景希望更自然——"怎么让对话不像在背台词"
  4. 演员紧张导致表演僵硬——"他们太在意对方了"

语言信号

  • "演员对视不自然"、"对话像话剧"
  • "怎么让表演更自然"、"演员太僵了"
  • "要不要让他们看着对方"、"亲密场景怎么拍"
  • "对话感觉假"、"像在背台词"

与相邻 skill 的区分

  • 与 dialogue-task-overload 的区别:task-overload 是"给演员更多任务来触发本能反应"(极端手段),此 skill 是"基础的自然主义表演指导"(基本原则)

E — 可执行步骤 (Execution)

  1. 评估场景的情感密度

    • 完成标准:判断场景是"日常对话"还是"情感爆发"。日常→全程避免对视;爆发→保留1-2次对视作为"事件"
  2. 为每个演员设计手头任务

    • 完成标准:每个演员至少有1个具体的身体任务(洗碗/倒咖啡/整理文件/摆弄手机),任务与场景情绪匹配(紧张→快速小动作;放松→缓慢大动作)
  3. 安排对视的时机

    • 完成标准:整个场景中只有1-2个"抬头看"的瞬间,这些瞬间对应台词的情感高潮。其余时间视线在任务和环境上流动

  • 🔴 判停条件: 若演员因手头任务太复杂而忘记表演,或场景需要的对峙张力因避免对视而被削弱,回到步骤1重新评估情感密度并调整任务难度

B — 边界 (Boundary) ★

不要在以下情况使用此 skill

  • 刻意设计的对峙/告白/摊牌场景——这些场景的张力正来自直接对视
  • 角色第一次见面——陌生人对视是正常的试探行为
  • 舞台剧/话剧改编——话剧美学允许更直接的对视

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

  • 新手让演员从头到尾对视→观众觉得假
  • 给演员的任务太复杂→演员忙于操作道具忘记表演

反模式与常见错误

  • 为避免对视而让演员始终低头——把"不互相对视"变成"不看任何东西",演员的视线失去焦点,表演变成木讷而非自然
  • 手头任务与台词内容争夺观众注意力——演员在切菜的同时说出关键台词,观众盯着刀和菜而忽略了台词的情感重量,任务变成了干扰而非辅助
  • 在情感高潮点仍然坚持不对视——把"日常避免对视"教条化到所有场景,包括告白、摊牌、诀别等本应直视的瞬间,削弱了对视作为"事件"的爆发力

作者的盲点 / 时代局限

  • 未考虑独白/画外音场景(这些场景没有"对方"可以不对视)
  • 偏向西方表演体系——东亚文化中回避对视有不同含义(尊重vs冷漠)

容易混淆的邻近方法论

  • "方法派"表演中的"情绪记忆"——那是演员内心工作,不是导演的外部调度

Bundled files

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

Frequently asked questions

What does the Dialogue Busy Hands No Eye Contact AI skill do?

(1)演员对话时互相盯着对方眼睛不放;(2)表演感觉舞台化或不真实;(3)导演不知道如何让对话场景看起来自然

Why use Dialogue Busy Hands No Eye Contact on TypingMind?

Because you install it once and use it with any model. Dialogue Busy Hands No Eye Contact 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 Dialogue Busy Hands No Eye Contact in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/geegl/directorskills/tree/main/output/books/master-shots-v2/dialogue-busy-hands-no-eye-contact. 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 Dialogue Busy Hands No Eye Contact?

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 Dialogue Busy Hands No Eye Contact?

As many as you like. As long as a model supports skills, you can use Dialogue Busy Hands No Eye Contact with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dialogue Busy Hands No Eye Contact 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇