Token导航 LogoToken导航

Agent Skill · AI 工具

scene-analysis(场景分析)

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

scene-analysis 是AI 工具类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在AI 工具类的 2,536 个 Skill 里排第 1,486。

总安装 674周安装 27GitHub Stars 28下载 218核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

AI 工具类 Skill 用来扩展助手本身的能力,例如接模型、接检索、接外部服务。

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

来源仓库内路径:skills/scene-analysis

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/bybren-llc/story-systems-template --skill scen…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

scene-analysis 怎么安装?

在终端执行 npx skills add https://github.com/bybren-llc/story-systems-template --skill scene-analysis。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

scene-analysis 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

scene-analysis 需要什么权限?

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

scene-analysis 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

scene-analysis 用的人多吗?

公开数据是累计安装 674 次,近一周安装 27 次,下载 218 次,GitHub 28 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

scene-analysis 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理AI 工具类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

AI 工具类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
executing-plans

执行计划 · Codex、Claude

1,515,336173,110只读MIT通过
verification-before-completion

完成前的验证 · Codex、Claude

1,319,472173,121权限未标注MIT通过
subagent-driven-development

子 Agent 驱动开发 · Codex、Claude

1,312,416173,138只读MIT通过
copy-editing

复制编辑 · Codex、Claude

1,209,57625,632只读MIT通过
paywall-upgrade-cro

付费专区升级 cro · Codex、Claude

1,030,17625,617只读MIT通过
scene-analysis

场景分析 · 本页

67428只读MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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?

平台分布

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