Token导航 LogoToken导航TokenDH.com
AI 工具只读github未标认证来源可访问clear审计通过

scene-analysis场景分析

Agent Skill

scene-analysis 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

674

周安装

27

GitHub Stars

28

下载量

218
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:scene-analysis(场景分析)
来源仓库:https://github.com/bybren-llc/story-systems-template
仓库路径:skills/scene-analysis
安装命令:
npx skills add https://github.com/bybren-llc/story-systems-template --skill scene-analysis
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/bybren-llc/story-systems-template --skill scene-analysis

简介

用于解析叙事结构中的场景元素和角色行为。

  • 适合在剧本创作或故事系统开发中梳理情节逻辑。
  • 可提取关键事件、冲突点和转折点,生成分析报告。
  • 安装方式基于 GitHub,需确保文本输入符合格式要求。
  • 分析结果应结合创作者意图进行主观校验。scene-analysis 属于AI 工具类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Scene Analysis Skill

Invocation Triggers

Apply this skill when:

  • Analyzing scene effectiveness
  • Evaluating scene pacing
  • Identifying scene problems
  • Breaking down scene beats

Scene Fundamentals

What Makes a Scene?

A scene is a unit of story with:

  • Single location (or continuous movement)
  • Continuous time (or clearly marked passage)
  • Beginning, middle, end
  • Purpose in the larger story

The Scene Question

Every scene should answer: "What changes?"

If nothing changes, the scene may not be necessary.

Scene Anatomy

Scene Structure

HOOK      → Grabs attention, establishes context
BUILD     → Develops conflict/tension
TURN      → Something changes
RESOLUTION → Scene's immediate outcome
PROPULSION → Sets up what's next

Example Analysis

INT. RESTAURANT - NIGHT

HOOK: Sarah sits waiting. Checks her watch. John arrives, late.

BUILD: Awkward pleasantries. Sarah's cool. John tries to connect.

TURN: Sarah reveals she knows about the affair.

RESOLUTION: John admits it. Offers no excuse.

PROPULSION: Sarah says "I want a divorce" - cut before John responds.

Scene Purpose

Plot Functions

FunctionDescription
SetupEstablish information for later
ConfrontationCharacters in conflict
RevelationNew information emerges
DecisionCharacter makes choice
ActionPhysical events unfold
ConsequenceResults of previous actions

Character Functions

FunctionDescription
IntroductionMeet a character
DevelopmentDeepen understanding
Arc momentCharacter changes
RelationshipDefine/change relationship

Every Scene Must

  1. Serve at least ONE plot function
  2. Serve at least ONE character function
  3. Ideally serve BOTH simultaneously

Pacing Analysis

Scene Length Guidelines

TypePagesPurpose
Short (1/2-1 page)Quick information, transitions
Medium (2-3 pages)Standard dialogue scenes
Long (4-5 pages)Major confrontations, setpieces
Extended (5+ pages)Climactic moments only

Pacing Rhythm

Vary scene lengths for rhythm:

SHORT - MEDIUM - MEDIUM - SHORT - LONG - SHORT

Not:

MEDIUM - MEDIUM - MEDIUM - MEDIUM - MEDIUM

Scene Economy

  • Enter late: Skip arrivals, greetings
  • Leave early: Cut after the point is made
  • Cut the fat: Every line earns its place

Scene Beats

What is a Beat?

A shift in the scene - emotion, power, information.

Identifying Beats

Mark where something changes:

1. Sarah waits (anticipation)
   [BEAT: John arrives late]
2. Awkward greeting (tension)
   [BEAT: Sarah asks direct question]
3. John deflects (avoidance)
   [BEAT: Sarah reveals she knows]
4. John exposed (power shift)
   [BEAT: John admits truth]
5. Resolution (new status quo)

Beat Mapping

| Beat # | What Happens | Emotional Shift |
|--------|--------------|-----------------|
| 1 | Sarah waits | Hope → Doubt |
| 2 | John arrives | Doubt → Tension |
| 3 | Small talk | Tension → Impatience |
| 4 | Sarah confronts | Impatience → Anger |
| 5 | John admits | Anger → Devastation |

Scene Analysis Template

## Scene Analysis: [Scene Description]

### Location & Time
INT./EXT. [LOCATION] - [TIME]
Page [X] - [Y] ([Z] pages)

### Scene Purpose
- **Plot Function:** [setup/confrontation/revelation/etc.]
- **Character Function:** [introduction/development/arc/etc.]
- **What changes:** [state A → state B]

### Structure
- **Hook:** [description]
- **Build:** [description]
- **Turn:** [description]
- **Resolution:** [description]
- **Propulsion:** [description]

### Beat Breakdown
[Beat mapping table]

### Strengths
- [What works]

### Issues
- [What doesn't work]

### Recommendations
1. [Specific improvement]
2. [Specific improvement]

Common Scene Problems

No Conflict

Problem: Characters agree, nothing is at stake. Fix: Give characters opposing goals. Even allies disagree on methods.

No Change

Problem: Scene ends same as it started. Fix: Something must be different. Information, relationship, stakes.

Wrong Length

Problem: Scene overstays welcome or rushes through. Fix: Match length to importance. Trim fat or expand key moments.

Unclear Purpose

Problem: Scene exists but why? Fix: Define the scene's job. If it has none, cut it.

Predictable

Problem: Scene goes exactly as expected. Fix: Add reversals, surprises, complications.

Scene Types Analysis

Exposition Scene

  • Risk: Information dump
  • Goal: Information + conflict
  • Test: Would scene be interesting without info?

Action Scene

  • Risk: All spectacle, no stakes
  • Goal: Character revealed through action
  • Test: What does action tell us about character?

Dialogue Scene

  • Risk: Talking heads
  • Goal: Subtext, conflict, change
  • Test: Is there tension in the conversation?

Transition Scene

  • Risk: Unnecessary
  • Goal: Essential bridge only
  • Test: Can it be cut? Can info be combined elsewhere?

Scene Checklist

Before Writing

  • What is the scene's purpose?
  • What changes by the end?
  • What's the conflict?
  • When does the scene start/end?

After Writing

  • Does the scene have a clear hook?
  • Does tension build?
  • Is there a turn?
  • Does it propel to next scene?
  • Can it be shorter?
  • Is it the right length for its importance?

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

28.22%
按下载量换算62

Cursor

24.48%
按下载量换算53

kilo

17.22%
按下载量换算38

windsurf

13.73%
按下载量换算30

zencoder

7.5%
按下载量换算16

Antigravity

3.83%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills