TypingMindTypingMindThe best frontend for AI
Scene Transition Caboose Diagnosis logo

Scene Transition Caboose Diagnosis

Community
geegl
scene-transition-caboose-diagnosis

用户提到场景多余、要不要删、节奏拖沓、末节场景

Overview

Publishergeegl
Repositorydirectorskills
Skill namescene-transition-caboose-diagnosis
Stars
68
Forks
7
Bundled files
1
LicenseMIT
Links
Skill sourceRepository
  • 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 Scene Transition Caboose Diagnosis 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/scene-transitions/scene-transition-caboose-diagnosis
  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/scene-transitions/scene-transition-caboose-diagnosis .claude/skills/scene-transition-caboose-diagnosis
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scene Transition Caboose Diagnosis 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 Scene Transition Caboose Diagnosis 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 Scene Transition Caboose Diagnosis 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)

末节场景 (Caboose Scene)：不具有任何戏剧性结尾的过渡场景，像火车末节车厢一样被拖着走。

— Bays, 术语表, p.149-152

I — 方法论骨架 (Interpretation)

末节场景是场景转换中最常见的失败模式——一个没有戏剧功能的场景，只是被"拖着"存在。像火车的最后一节车厢，它不提供动力，只是被拉着走。

诊断标准：如果删除这个场景后观众不会丢失任何故事信息或情感连接，那它就是末节场景。核心问题是"这个场景的戏剧功能是什么？"——如果答案是"只是过渡"或"只是让观众喘口气"，那它很可能是一个需要删除的 caboose。

关键区别：不是所有过渡场景都是 caboose。有戏剧功能的过渡（如揭示角色新信息、建立下一场景的情绪基调）不是 caboose。只有那些"什么都没发生"的场景才是。

A1 — 书中的应用 (Past Application)

案例 1: 诊断剧本中的多余场景

  • 问题: 编剧发现剧本中有3个场景让读者反馈"有点无聊"
  • 方法论的使用: 用 caboose 诊断法逐个检查：场景A删除后观众会丢失角色关系信息（不是 caboose）；场景B删除后观众不知道主角去了哪里（不是 caboose，但需要更短的交代）；场景C删除后没有任何信息丢失（是 caboose）
  • 结论: 场景C是末节场景，应该直接删除
  • 结果: 删除场景C后，剧本节奏明显改善

案例 2: 诊断电影中的过渡场景

  • 问题: 导演发现观众在影片中段15分钟处开始走神，但不确定是哪个场景导致的
  • 方法论的使用: 用caboose诊断法检查中段三个场景：场景D删除后观众不知道角色为何改变了决定（不是caboose）；场景E删除后观众不知道角色去了哪里（不是caboose但需缩短）；场景F删除后只丢失了一段角色走路去车站的画面，无任何信息损失（是caboose）
  • 结论: 场景F是末节场景——它的唯一功能是'过渡'，但这个功能可以被一句台词替代
  • 结果: 删除场景F并用一句对话交代角色行程，观众走神问题消失

A2 — 触发场景 (Future Trigger) ★

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

  1. 用户不确定某个场景是否多余——"这个场景要不要删？"
  2. 用户觉得剧本/影片节奏拖沓——"中间部分有点无聊"
  3. 用户在做最后的剪辑精简——"需要精简到X分钟以内"

语言信号 (用户的话里出现这些就应激活)

  • "场景多余"
  • "要不要删"
  • "节奏拖沓"
  • "末节场景"
  • "这段有点无聊"

与相邻 skill 的区分

  • 与 scene-transition-seamless-pause 的区别: seamless-pause 是有效的过渡技巧，caboose 是需要删除的无效过渡
  • 与 scene-transition-loyalty-transfer 的区别: loyalty-transfer 用于场景之间的情感转移，caboose-diagnosis 用于判断场景本身是否应该存在

E — 可执行步骤 (Execution)

当 skill 被激活后, agent 应按以下步骤执行:

  1. 列出场景的戏剧功能

    • 完成标准: 用一句话说清这个场景为故事贡献了什么——揭示信息？建立情绪？推进情节？如果答不上来，高度疑似 caboose
    • 🔴 判停条件: 若场景没有任何可识别的戏剧功能，直接判定为 caboose，建议删除

  2. 做"删除测试"

    • 完成标准: 假设删除该场景，检查观众是否会丢失故事信息或情感连接。如果删除后无影响 = caboose

  3. 检查是否可以缩短而非删除

    • 完成标准: 有些场景有微弱的戏剧功能，可以通过缩短（如从3分钟压到30秒）保留功能同时消除拖沓感
    • 🔴 判停条件: 若缩短后仍无明显戏剧功能，直接删除

B — 边界 (Boundary) ★

不要在以下情况使用此 skill

  • 不要删除有信息传递功能的场景——即使它看起来"无聊"，可能承载了重要的潜台词
  • 不要在未看完整体结构的情况下诊断单个场景——caboose 的判断需要上下文

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

  • 误删"安静"场景——有些场景表面安静但承载了角色发展的关键信息
  • 把"节奏变化"误判为"拖沓"——快节奏叙事中的短暂喘息不是 caboose

作者的盲点

作者假设所有场景都应该有明确的戏剧功能，但某些艺术电影的"留白"场景可能故意没有传统戏剧功能——它们的功能是创造氛围或让观众反思。

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 Scene Transition Caboose Diagnosis AI skill do?

用户提到场景多余、要不要删、节奏拖沓、末节场景

Why use Scene Transition Caboose Diagnosis on TypingMind?

Because you install it once and use it with any model. Scene Transition Caboose Diagnosis 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 Scene Transition Caboose Diagnosis in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/geegl/directorskills/tree/main/output/books/scene-transitions/scene-transition-caboose-diagnosis. 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 Scene Transition Caboose Diagnosis?

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 Scene Transition Caboose Diagnosis?

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

Is the Scene Transition Caboose Diagnosis 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.

Related AI Skills

View all
HKUDS logo

Cli Anything 3mf

HKUDS
OrganizationPopular

3MF mesh geometry editor — detect and resize cylindrical holes, repair meshes, compare 3D printing files. Works with BambuStudio and PrusaSlicer 3MF files.

4.6K
49.5K
Instructions
View
HKUDS logo

Cli Anything Godot

HKUDS
OrganizationPopular

Agent-native CLI for Godot project management, scenes, exports, and script execution.

4.6K
49.5K
Instructions
View
HKUDS logo

Cli Anything Intelwatch

HKUDS
OrganizationPopular

Zero friction. Full context. Competitive intelligence, M&A due diligence, and OSINT directly from your terminal. Uses Node.js/npx.

4.6K
49.5K
Instructions
View
kepano logo

Defuddle

kepano
CommunityPopular

Extract clean Markdown from HTML pages with Defuddle CLI.

3.5K
48.5K
Instructions
View

Set up your own AI workspace now

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