Token导航 LogoToken导航

Agent Skill · AI 工具

story-analysis(故事分析)

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

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

总安装 10,608周安装 451GitHub Stars 67下载 3,716核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jwynia/agent-skills --skill story-analysis

这个 Skill 是做什么的

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

story-analysis 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。它适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。安装命令:npx skills add https://github.com/jwynia/agent-skills --skill story-analysis

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

story-analysis 怎么安装?

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

story-analysis 支持哪些 AI 工具?

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

story-analysis 需要什么权限?

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

story-analysis 是免费的吗?

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

story-analysis 用的人多吗?

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

story-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通过
story-analysis

故事分析 · 本页

10,60867只读MIT通过

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

SKILL.md 原文

Story Analysis Diagnostic

Purpose

Systematically evaluate completed short stories or novel chapters to identify strengths, weaknesses, and improvement opportunities. Use after drafting to assess whether the piece achieves its narrative goals.

Quick Reference

ModeUse ForKey Focus
Short StoryComplete standalone piecesUnity, shattering moment, resolution
ChapterSections within larger workContinuity, momentum, arc contribution

Short Story Analysis

SA1: Narrative Foundation

Evaluate:

  • Single clear premise or conflict driving the story
  • Scope appropriate for length
  • Premise integrated with plot and character
  • Clear implications that matter to the story

Questions:

  1. Can you state the core conflict in one sentence?
  2. Is the scope right for the word count?
  3. Does the premise connect to character stakes?
  4. Are the implications explored within the story?

SA2: Character Construction

Evaluate:

  • One or two main characters with clear stakes
  • Efficient characterization through actions/choices
  • Character arcs intersecting with premise
  • Limited but purposeful supporting cast
  • Distinct voice and perspective

Questions:

  1. Who is the story about and what do they want?
  2. Is character revealed through action, not description?
  3. Does the character change in response to events?
  4. Does every character serve a purpose?

Red Flags:

  • Character described but never demonstrated
  • Supporting characters who don't affect anything
  • Stakes unclear or abstract

SA3: Story Environment

Evaluate:

  • Details woven into action, not exposition
  • Each element serves multiple purposes (setting/plot/theme)
  • Clear rules and limitations
  • Environment revealed through character interaction
  • Effective atmosphere and tone

Questions:

  1. Is worldbuilding shown through action or told in blocks?
  2. Does each setting detail do double duty?
  3. Are the story's rules clear and consistent?
  4. Does the environment affect character choices?

Red Flags:

  • Info-dump paragraphs
  • Details that never matter again
  • Setting that doesn't influence events

SA4: The Shattering Moment

Definition: The pivotal point that transforms everything—a moment that cannot be undone.

Must function through one approach:

  • Personal revelation that transforms understanding
  • External event that forces change
  • Relationship transformation that shifts dynamics
  • Internal realization that cannot be undone
  • Cultural/social collision that demands response

For Science Fiction:

  • Technology IS the shattering moment
  • Technology ENABLES the shattering moment
  • Technology PREVENTS recovery
  • Shattering moment CHANGES relationship with technology

Questions:

  1. Is there a clear turning point?
  2. Is it connected to the core conflict?
  3. Does it change the character irreversibly?
  4. Does everything after feel different?

SA5: Scene Structure

Evaluate:

  • Scenes maximize both character and premise
  • Strategic balance of scene and summary
  • Opening hook establishes character, situation, conflict
  • Focused conflict from the core premise
  • Resolution addresses conflict while suggesting broader implications

Questions:

  1. Does every scene advance character AND plot?
  2. Is the opening hook doing its job?
  3. Is the conflict focused or diffuse?
  4. Does the resolution satisfy while resonating beyond?

SA6: Technical Execution

Economy of Detail:

  • Every element serves multiple purposes
  • No extraneous background or world info
  • Exposition integrated into action
  • Clear connection between details and story purpose

Point of View:

  • Consistent and purposeful POV choice
  • Viewpoint optimal for revealing character and premise
  • Minimal POV shifts
  • Clear character perspective on events
  • Effective narrative distance

Language and Voice:

  • Consistent tone throughout
  • Purposeful dialogue
  • Effective subtext
  • Style serves story purpose
  • Distinct narrative voice

SA7: Emotional Architecture

Tension Management:

  • Clear emotional throughline
  • Strategic building and release
  • Effective pacing of reveals
  • Balance of explicit and implicit

Reader Engagement:

  • Clear emotional stakes
  • Strategic use of empathy
  • Meaningful emotional payoff
  • Effective use of subtext

Questions:

  1. Is there a clear emotional journey?
  2. Does tension build appropriately?
  3. Is the emotional payoff earned?
  4. What remains unspoken but felt?

SA8: Thematic Resolution

Evaluate:

  • Character arc completion
  • Premise implications addressed
  • Immediate conflict resolved
  • Larger questions remain thought-provoking

Questions:

  1. Is the character arc complete?
  2. Are the premise implications explored?
  3. Is the immediate conflict resolved?
  4. Does the story linger in the mind?

Novel Chapter Analysis

CA1: Position in Narrative Arc

Evaluate:

  • Chapter's specific role in overall structure
  • Contribution to plot progression
  • Advancement of character development arcs
  • Thematic development within larger work

Questions:

  1. What is this chapter's job in the novel?
  2. What plot progress happens here?
  3. What character progress happens here?
  4. How does it develop the theme?

CA2: Narrative Momentum

Evaluate:

  • Opening hook's connection to previous chapter
  • Tension management across chapter breaks
  • Balance of resolution and open questions
  • Strength of chapter ending propulsion
  • Questions answered vs. questions raised

Questions:

  1. Does the opening connect to what came before?
  2. Does the ending make readers want to continue?
  3. What questions does this chapter answer?
  4. What new questions does it raise?

Red Flags:

  • Chapter ends at natural stopping point (too easy to put down)
  • Opening ignores previous chapter's energy
  • All questions answered, no forward pull

CA3: Plot Threading

Evaluate:

  • Ongoing plot threads advanced
  • New plot threads introduced
  • Plot elements resolved
  • Setup for future chapters
  • Connection to primary and secondary arcs

Track:

ThreadStatus This Chapter
Main plotAdvanced / Setup / Resolved
Subplot AAdvanced / Setup / Resolved
Subplot BAdvanced / Setup / Resolved

CA4: Character Continuity

Evaluate:

  • Progress on character arcs from previous chapters
  • New character aspects revealed
  • Relationship evolution
  • Setup for future development
  • Consistency with established traits

Questions:

  1. How has this character changed since chapter 1?
  2. What new facets are revealed here?
  3. How do relationships shift?
  4. Is the character consistent with who they've been?

CA5: POV and Voice

Evaluate:

  • Consistency with established POV patterns
  • Effective transitions between viewpoints (if multiple)
  • Depth of penetration into character perspective
  • Balance of internal and external narrative
  • Voice and tone alignment with overall narrative

CA6: Information Flow

Evaluate:

  • Balance of new and established information
  • Strategic revelation of background elements
  • Management of reader vs. character knowledge
  • Setup of future revelations
  • Integration of necessary exposition

CA7: Pacing Elements

Evaluate:

  • Chapter's pace relative to surrounding chapters
  • Internal pacing structure
  • Tension development and release
  • Scene length and rhythm
  • Strategic use of time

CA8: Connection Tracking

Previous Chapter:

  • Immediate continuity elements
  • Tension carryover
  • Question resolution
  • Thread advancement

Next Chapter:

  • Setup elements planted
  • Tension building toward
  • Questions raised
  • Threads advanced

Broader Novel:

  • Major arc advancement
  • Theme development
  • Character arc progression
  • World development contribution

Evaluation Checklists

Short Story Checklist

  • Single clear premise/conflict
  • Appropriate scope for length
  • Characters with clear stakes
  • Characterization through action
  • Environment serves multiple purposes
  • Clear shattering moment
  • Every scene advances character AND plot
  • Consistent POV
  • Emotional arc present
  • Resolution satisfies while resonating

Chapter Checklist

  • Clear role in overall novel
  • Opening connects to previous chapter
  • Ending creates forward pull
  • Plot threads advanced
  • Character development progresses
  • Consistent with established elements
  • Sets up future developments
  • Appropriate pacing for position in novel

Anti-Patterns

1. The Checklist Tyranny

Pattern: Treating all checklist items as equally important. Flagging every missed item as a problem requiring fix. Why it fails: Not all issues matter equally. A missing shattering moment is critical; a slight POV wobble might be stylistic choice. Checklists identify possibilities, not mandates. Fix: Prioritize by impact. Ask "Does this actually hurt the story?" before recommending changes. Some rules can be broken effectively.

2. The Genre Blindness

Pattern: Applying one genre's standards to all stories. Evaluating literary fiction by thriller pacing standards, or action stories by literary depth requirements. Why it fails: Genres have different contracts with readers. What's a flaw in one genre is a feature in another. Fix: Identify genre expectations first. Evaluate against what the story is trying to be, not a universal standard.

3. The Nitpick Cascade

Pattern: Focusing on micro-issues while missing macro problems. Catching comma splices while the story has no conflict. Why it fails: Sentence-level perfection can't save structural failure. Fixing small things first is procrastination from hard work. Fix: Diagnose at structure level first. Only move to prose-level analysis after structure is sound.

4. The Comparison Trap

Pattern: Evaluating against published bestsellers or classics. "This isn't as good as [famous work]." Why it fails: Drafts aren't finished works. Different stories serve different purposes. Unfair comparison discourages rather than guides. Fix: Evaluate against the story's own goals. What is this trying to do? Does it succeed at that?

5. The Fix-Everything Dump

Pattern: Delivering a comprehensive list of all issues without prioritization or encouragement. Why it fails: Overwhelming. Writers shut down when facing 50 problems. No sense of what matters most. Fix: Identify 3-5 highest-impact issues. Note what's working. Create actionable, prioritized guidance.

Integration Points

Inbound:

  • From drafting: After completing draft
  • From revision: As part of revision process

Outbound:

  • To revision: For identified issues
  • To scene-sequencing: For pacing problems
  • To dialogue: For conversation issues
  • To character-arc: For character problems

Complementary:

  • flash-fiction: For stories under 1500 words
  • prose-style: For sentence-level issues
  • story-sense: For diagnosing what's wrong

平台分布

Claude Code

30.79%
按下载量换算1,144

OpenCode

22.43%
按下载量换算833

Gemini CLI

17.46%
按下载量换算649

Antigravity

12.59%
按下载量换算468

trae

8.47%
按下载量换算315

Codex

3.12%
按下载量换算116

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

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

继续浏览同类 Skills