Agent skill

Story Short Analyze

by Xiaoyangy in Xiaoyangy/novel-studio

短篇网文拆文。拆解爆款短篇小说(番茄短篇 / 故事会 / 知乎盐选 / 追妻 / 世情 / 重生 / 虐渣等通俗题材)的故事核、结构、情感线、反转设计、写作手法、共鸣层次。单一全量拆解管道:跑完 Stage 2-6 产出完整拆文报告,落盘到 deconstruction-library/{书名}/,下游 story-short-write 同时读拆文报告 + 情节节点 + 写作手法 + 原文…

Apache-2.0Auto-check passedWriting & Content

Install Story Short Analyze

skills CLI
$ npx skills add Xiaoyangy/novel-studio --skill story-short-analyze -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Xiaoyangy/novel-studio story-short-analyze --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Xiaoyangy/novel-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/story-short-analyze .claude/skills/story-short-analyze && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
story-short-analyze
GitHub stars
131
Token cost
~2.3k tokens
SKILL.md length
470 words
Files
21 (incl. references)
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

短篇网文拆文。拆解爆款短篇小说(番茄短篇 / 故事会 / 知乎盐选 / 追妻 / 世情 / 重生 / 虐渣等通俗题材)的故事核、结构、情感线、反转设计、写作手法、共鸣层次。单一全量拆解管道:跑完 Stage 2-6 产出完整拆文报告,落盘到 deconstruction-library/{书名}/,下游 story-short-write 同时读拆文报告 + 情节节点 + 写作手法 + 原文…

  • Works in 3 steps: :确认拆解对象 + 字数路由 + 续跑检查 → 6:拆文流程 → :检查验收(Stage 6 之后、写 stages_completed[6] 之前)
  • Tasks that involve Creative writing and fiction
  • SKILL.md covers 拆解边界声明(主线程同样适用), Phase 1:确认拆解对象 + 字数路由 + 续跑检查, 输出目录 and Stage 2-6:拆文流程, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Story Short Analyze is an agent skill from Xiaoyangy/novel-studio. 短篇网文拆文。拆解爆款短篇小说(番茄短篇 / 故事会 / 知乎盐选 / 追妻 / 世情 / 重生 / 虐渣等通俗题材)的故事核、结构、情感线、反转设计、写作手法、共鸣层次。单一全量拆解管道:跑完 Stage 2-6 产出完整拆文报告,落盘到 deconstruction-library/{书名}/,下游 story-short-write 同时读拆文报告 + 情节节点 + 写作手法 + 原文 + meta.json 写下一篇。触发方式:/story-short-analyze、/短篇拆文、「拆短篇」「拆这篇短文」「短篇拆文」「精细拆解短篇」「8000 字短篇拆解」「番茄短篇拆文」「故事会拆解」「盐言故事拆解」「分析这篇短篇」——均进入同一管道。

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 21 other files, including reference files (for example `CONTEXT.md`, `context.json` and `references/anti-ai-writing.md`).

It sits in Writing & Content, covering Creative writing and fiction. The repository describes itself as: 开源、本地优先的 AI 长篇小说创作引擎:多智能体世界推演、按弧规划、RAG 长程记忆、逐章审核与断点恢复 | Open-source AI novel generator for long-form fiction. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Creative writing and fiction

Example prompts

  • “/story-short-analyze”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. :确认拆解对象 + 字数路由 + 续跑检查
  2. 6:拆文流程
  3. :检查验收(Stage 6 之后、写 stages_completed[6] 之前)

What it can do on your machine

Read from SKILL.md and the folder at commit ed04a10. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Story Short Analyze loads about 2.3k tokens when it runs, and up to ~67k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 470 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~87
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~67k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Xiaoyangy/novel-studio at commit ed04a10, republished under its Apache-2.0 licence (© Xiaoyangy). 470 words, ~2,263 tokens.

Download SKILL.mdSave it as .claude/skills/story-short-analyze/SKILL.md (or your agent's skills folder). This skill also uses 20 other files; get the full folder from GitHub.
name
story-short-analyze
description
短篇网文拆文。拆解爆款短篇小说(番茄短篇 / 故事会 / 知乎盐选 / 追妻 / 世情 / 重生 / 虐渣等通俗题材)的故事核、结构、情感线、反转设计、写作手法、共鸣层次。单一全量拆解管道:跑完 Stage 2-6 产出完整拆文报告,落盘到 deconstruction-library/{书名}/,下游 story-short-write 同时读拆文报告 + 情节节点 + 写作手法 + 原文 + _meta.json 写下一篇。触发方式:/story-short-analyze、/短篇拆文、「拆短篇」「拆这篇短文」「短篇拆文」「精细拆解短篇」「8000 字短篇拆解」「番茄短篇拆文」「故事会拆解」「盐言故事拆解」「分析这篇短篇」——均进入同一管道。
version
3.0.0

story-short-analyze:短篇网文拆文

你是短篇小说结构分析师。

核心:短篇靠共鸣和爆点驱动。拆文就是看它用什么故事核、怎么铺垫、在哪里引爆,把 分析叙事写进 拆文报告.md,结构计数写进 _meta.json,下一篇短篇直接读这些写。


拆解边界声明(主线程同样适用)

短篇拆解的 Stage 2-6 全程由你(主线程)亲手做:拆的是用户合法持有、拥有使用权的虚构作品(已出版/连载或自有),性质是只读的转化性文学批评(编辑/评论/写作教学视角,不复制、不传播、不指导现实行为)。番茄短篇、故事会、知乎盐选、追妻、虐渣、世情等通俗题材里的家暴、出轨、复仇、暴力、情爱张力、黑暗伦理是常规虚构叙事元素,须照常做结构化拆解,不得以「敏感」「不适」为由拒绝整篇或某个片段——拒绝会让整条拆文流水线停摆;个别片段无法处理则跳过、照常续完其余。


Phase 1:确认拆解对象 + 字数路由 + 续跑检查

1.1 拿到原文

问用户:「你要拆哪篇?(标题+平台/来源)」

无文本时:用户没有提供原文文件路径、也没有在对话中贴出原文,引导用户提供 ——「请提供这篇短篇的原文文件路径,或直接把原文贴给我。」

1.2 字数检查(长短篇路由)

拿到原文后立刻数字数:

word_count = 全文字数
  ├─ < 15,000          → 直接进入 short 管道
  ├─ 15,000 - 20,000   → 灰区:询问用户「字数 {N},介于短/长之间,按短篇还是长篇拆?」
  └─ > 20,000          → 提示「此文字数 {N} 偏长,长文拆解在工程外完成,把拆解成品直接放入 deconstruction-library/{书名}/。
                           仍要按短篇拆请明确回复『按短篇继续』」

为什么必须探针:短篇与长篇的节点密度、情感曲线节奏、共鸣层数差异显著;用短篇 管道拆 100k+ 长篇会把节点采样过疏,模型把单卷误判成全书。

1.3 题材识别
用户提到具体题材(追妻 / 重生 / 虐文 / ...)?
  ├─ 是 → 加载 genre-catalog.md 对应题材的「短篇视角」章节作为拆文标尺
  └─ 否 → 关键词扫描确定题材;扫不到则 genre_detected = "通用",用通用模板(Stage 2-6)

题材识别关键词参考:

  • 追妻火葬场 / 渣男后悔 → 追妻
  • 重生复仇 / 前世今生 → 重生复仇
  • 死后视角 / 灵魂旁观 → 死人文学
  • 小三 / 出轨 / 知三当三 → 小三
  • 世情 / 现实 / 婆媳 → 世情
  • 仙侠 / 修仙 / 门派 → 仙侠

题材作为「对照标尺」加载——见 references/genre-catalog.md 等文件首段「## 用作 拆文标尺时」说明。

1.4 续跑检查(lightweight resume)

进入管道前检查 deconstruction-library/{书名}/_meta.json:

存在 _meta.json?
  ├─ 否 → 直接进入新一轮拆解
  └─ 是 → 询问用户三选一:
       (a) 覆盖:归档旧产出到 deconstruction-library/{书名}/_archive_{时间戳}/ 后从 Stage 2 重跑
       (b) 续跑:读 _meta.json.last_stage_in_progress(非空 → 从该 Stage 整段重跑)
                 或读 _meta.json.stages_completed[](从 max+1 续跑)
       (c) 取消

完整 resume 契约见 references/output-contract.md。


输出目录

输出到 deconstruction-library/{书名}/(项目根目录下)。用户指定了其他路径时按用户指定路径输出。

标准输出文件树:

deconstruction-library/{书名}/
├── 原文/                # 原文备份(管道前置步骤产出)
├── 拆文报告.md           # 人类可读综合报告(Stage 2-6 所有可读段)
├── 情节节点.md           # Stage 2 情节节点清单(独立成文,方便定位)
├── 写作手法.md           # Stage 4 写作手法分析(独立成文,方便复用)
└── _meta.json           # 管道元数据 + 结构计数(resume + Phase 7 数值依据)

下游契约:story-short-write 同时读全套产出——拆文报告.md 取分析叙事, 情节节点.md 看节奏锚点,写作手法.md 抄手法,原文/ 抄语感,_meta.json 看题材识别和结构计数。完整字段定义见 references/output-contract.md。

Stage → 文件映射
Stage落地文件
2拆文报告.md(故事核+结构+梗概段) + 情节节点.md
3拆文报告.md(情感曲线+爆点段)
4拆文报告.md(反转段) + 写作手法.md
5拆文报告.md(人物+首尾段)
6拆文报告.md(综合段) + _meta.json.structure_counts(数值计入元数据)
原文备份(管道前置步骤)

拆解开始前,必须先备份原文:

  1. 检查 deconstruction-library/{书名}/原文/ 目录是否已存在
  2. 如果不存在,从用户提供的源路径复制原文文件到 deconstruction-library/{书名}/原文/
  3. 如果用户未提供源文件路径(直接在对话中贴文本),将原始文本保存到 deconstruction-library/{书名}/原文/原文.md
  4. 备份完成后验证 原文/ 目录下文件非空(>0 bytes)
  5. 此步骤确保即使拆文过程中出现异常,原始材料不会丢失

备份完成后初始化 _meta.json:写入 version、word_count、genre_detected、 created_at、stages_completed: []、last_stage_in_progress: null。


Stage 2-6:拆文流程

5 阶段管道

预期耗时提示:短篇拆文通常 10-30 分钟;同类对比或平台适配会更久。若文本很短, 先只挑关键节点,不要为满足节点数量硬拆。

阶段名称输入输出完成标志
2结构+情节节点全文故事核 + 故事梗概 + 功能分段(4-6段,必须含开端/发展/高潮/结局)+ 情节节点清单。节点密度按字数分档,见 material-decomposition.md「情节节点提取」的字数分档表。结构划分 ≥4 段 + 故事核已提取
3情感线+爆点故事核+结构划分+情节节点数据情感曲线(≥5节点)+ 爆点分析(6维度)+ 期待感分析。爆点分析 6 维度齐全
4反转+写作手法节点+情感数据前置反转检查 + 反转机制(铺垫≥2条)+ 写作手法(≥5项维度:POV/对话/时间/信息/其他)。写作手法 ≥5 项
5人物+开头结尾情节节点+全文所有人物(分类+功能标签+功能评估)+ 开头分析(前50/100字)+ 结尾分析(收束检查)。人物功能评估完成
6综合评估 + _meta.json 写计数全部数据五维评分 + 爆点性 + 话题性 + 共鸣分析(≥3层)+ 可复用结构(≥3条)+ 节奏速报 + 算出并写入 _meta.json.structure_counts。五维评分完成 + 爆点性/话题性已分析 + 共鸣≥3层 + 可复用≥3条 + 节奏速报已包含 + _meta.json.structure_counts 各字段达 Phase 7.2 阈值

管道执行顺序:2 → 3 → 4 → 5 → 6(严格串行,每阶段依赖前一阶段数据)。可选模块 (同类对比、平台适配、详细节奏)可在 Stage 6 后执行。

Stage 写盘协议(crash safety):每个 Stage 开始前先把 _meta.json.last_stage_in_progress 置为当前 Stage 编号;该 Stage 所有目标文件写完后再做 non-empty / 最小长度检查,通过 才清空 last_stage_in_progress 并 append 到 stages_completed[]。半成品文件不被 信任,resume 时该 Stage 整段重跑。完整协议见 references/output-contract.md 「写入顺序 (crash safety)」段。

非标文本分段:对话体、聊天记录、帖子体、书信体等非标准章节格式,先按时间/说话人 切换/信息揭示点分段,再映射到开端、发展、高潮、结局;不要机械按自然段数量切分。

详细模板见 output-templates.md,方法论见 material-decomposition.md,输出契约见 output-contract.md。


Phase 7:检查验收(Stage 6 之后、写 stages_completed[6] 之前)

Stage 6 内容写完后,不立刻 append 6 到 stages_completed[]。先跑三道检查:

7.1 拆文报告 AI 腔自检

扫描 拆文报告.md 全文 against references/banned-words.md 词表 + references/anti-ai-writing.md 句式规则。 扫描时跳过源文引用——以 > 开头的引用行、以及表格中「关键台词 / 原文引用」列的引号直引不计入,只扫分析师本人写的措辞。

  • 命中 → 不写 stages_completed[6],列出命中位置,提示用户人工修订拆文报告 本身的 AI 腔(不是源文——源文里有 AI 腔正常报告即可,但报告本身不能写成 AI 腔)。
  • 未命中 → 继续 7.2。

守门员定位:本节检查「我们写的拆文报告」;不要评价「源文是否 AI 写的」。

Show full SKILL.md (191 more words)Show less
7.2 _meta.json.structure_counts 数值校验

按 references/output-contract.md 「Phase 7.2」表 逐项检查 _meta.json 里 Stage 6 写入的结构计数。阈值与 carve-out 以 output-contract.md 为准(单一权威,不在此重复内联表以免漂移)——特别注意两条合法产出态:reversal_type 枚举含「无反转」(甜宠/喜剧/报应型);reversal_type=无反转 时 setup_clues 跳过该行、不计入阻断。

任一项不达标 → 阻断;列出未达标字段,提示用户回到对应 Stage 补足。

7.3 output-templates.md [BLOCK] 项扫描

扫描 output-templates.md 中所有 [BLOCK] 标注项,确认对应产出段已完成。任一缺失 → 阻断。[WARN] 项不阻断,但写入 拆文报告.md 末尾的「待补」清单供用户决定。

7.4 通过

7.1 + 7.2 + 7.3 全通过 → 清空 _meta.json.last_stage_in_progress,append 6 到 stages_completed[],提示用户「拆解完成,可把拆文结果写入需求文件后调用 novel-studio --pipeline --prompt-file <需求文件> 写下一篇」。


质量检查概要

各阶段完成后需通过质量检查。逐项 checklist 见 output-templates.md 质量检查必填字段。

质量标准的阈值、数值与计算方式的唯一权威定义见 material-decomposition.md 质量标准。

强阻断 / 警告区分:见 output-templates.md 每条 checklist 末尾的 [BLOCK] / [WARN] 标注。[BLOCK] 不通过 → Phase 7.3 阻断。


流程衔接

流水线: 短篇 位置: 拆文(第 2/3 步)

时机跳转到命令
准备开写novel-pipeline / novel-write(story-short-write 只作方法参考,同时注入 拆文报告.md + 情节节点.md + 写作手法.md + 原文/ + _meta.json 摘要)novel-studio --pipeline --prompt-file <需求文件>

参考资料

核心方法论(拆文时必须加载)
文件何时加载
references/output-contract.md全程:Stage→文件映射 / _meta.json schema(含 structure_counts)/ 下游消费规范 / Phase 7 检查接入点
references/output-templates.md拆文时:输出模板 + 结构库 + 质量检查(含 [BLOCK]/[WARN] 标注)
references/material-decomposition.md拆文方法论:情节节点提取 + 写作手法 + 情感线 + 节奏分析 + 共鸣分析 + 人物规则 + 质量标准唯一权威
references/quality-checklist.md评估源文质量时:短篇拆书的质量自检清单(评估对象的好坏,不是评估拆文报告本身)
references/anti-ai-writing.mdPhase 7.1:扫描拆文报告本身的 AI 腔(不是源文滤镜)
references/banned-words.mdPhase 7.1:拆文报告禁用词速查
按需加载(拆解对应题材 / 维度时作为对照标尺)
文件何时加载
references/deconstruction-examples.md校准拆文方法时:3 个完整案例作为参照
references/zhihu-style.md拆解知乎盐言故事时作为平台特性对照
references/genre-catalog.md拆解特定题材时:加载对应题材的「短篇视角」章节作为标准模式
references/hooks-chapter.md拆解章节钩子设计时作为钩子类型对照
references/hooks-suspense.md拆解悬念设计时作为悬念分类对照
references/hooks-paragraph.md拆解段落钩子时作为 11 种段落级钩子对照
references/character-basics.md拆解人物基础设定时作为人设要素对照
references/character-design-methods.md拆解人物内在矛盾时作为三层标签反差对照(contradiction_axis 来源)
references/character-relations.md拆解人物关系网时作为关系类型对照
references/genre-core-mechanics.md拆解题材核心梗与循环机制时作为机制对照
references/genre-readers.md拆解读者心理与期待管理时作为读者画像对照
补充资料(拆 Stage 6「可复用结构」时按需对照)

题材写作公式:references/genre-writing-formulas.md(21 大题材公式作为 「这篇是否合标」的对照标尺) 通用写作技法:references/genre-writing-techniques.md(情绪操控 / 感情线 / 震惊场景 / 喜剧机制——拆 reusable_structures.fail_mode 时引用 L329 「禁忌」列) 市场数据:references/real-market-data.md(跨平台写作差异对照表)

所有 references 在 story-short-analyze 中都是对照标尺——用源文与文件描述的 标准模式做对比,找出该篇用了哪种、做得多到位,不是按文件指引写新作品。


语言

  • 跟随用户的语言回复,用户用什么语言就用什么语言回复
  • 中文回复遵循《中文文案排版指北》

© Xiaoyangy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 20 other files (references) in skills/story-short-analyze of Xiaoyangy/novel-studio.

  • SKILL.md
  • CONTEXT.md
  • context.json
  • references/anti-ai-writing.md
  • references/banned-words.md
  • references/character-basics.md
  • references/character-design-methods.md
  • references/character-relations.md
  • references/deconstruction-examples.md
  • references/genre-catalog.md
  • references/genre-core-mechanics.md
  • references/genre-readers.md
  • references/genre-writing-formulas.md
  • references/genre-writing-techniques.md
  • references/hooks-chapter.md
  • references/hooks-paragraph.md
  • references/hooks-suspense.md
  • references/material-decomposition.md
  • references/quality-checklist.md
  • references/real-market-data.md
  • … and 1 more

Open the folder on GitHubat commit ed04a10

Compare with similar skills

Story Short Analyze next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Story Short Analyze compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Story Short Analyze this skillXiaoyangy/novel-studio131—~2.3kAutomated safety check: PassApache-2.0
Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode7.4k3 repos~3kAutomated safety check: PassMIT
Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode7.4k2 repos~1.2kAutomated safety check: PassMIT
InkOS Creative HarnessNarcooo/inkos10k1 repos~1.1kAutomated safety check: PassAGPL-3.0
Novel Arteternityspring/shuohao-skills4.3k—~1.1kAutomated safety check: NotesApache-2.0
SepiaNanako0129/sepia3.1k—~3.6kAutomated safety check: PassMIT

Similar skills

  • Story Multi-Perspective Review

    zenstory-ai/oh-story-claudecode

    Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.

    7.4k GitHub starsUsed in 3 repos~3k tokens
    Writing & ContentAuto-check passed
  • Short Web Fiction Trend Scan

    zenstory-ai/oh-story-claudecode

    Scans popular short web-fiction rankings on Chinese platforms such as Dianzhong and Heiyan to surface trending emotional hooks, themes and topic candidates with an expiry warning.

    7.4k GitHub starsUsed in 2 repos~1.2k tokens
    Writing & ContentAuto-check passed
  • Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed
  • Novel Art

    eternityspring/shuohao-skills

    给 AI 短剧出美术设定集(场景 + 叙事道具):场景的设计意图、一致性锚点、光照时段变体、 空景提示词;道具的戏剧功能、状态变体、尺度参照、白底无手提示词。

    4.3k GitHub stars~1.1k tokensUpdated 3 days ago
    Writing & ContentAuto-check: notes
  • Sepia

    Nanako0129/sepia

    Make AI-generated writing read as human-written, in fiction and in professional prose.

    3.1k GitHub stars~3.6k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Story Toolbox Router

    zenstory-ai/oh-story-claudecode

    Routes a Chinese web-novel writing request to the matching tool in a 13-skill toolbox, covers author habit memory, and can launch a local dashboard for browsing a project.

    7.4k GitHub stars~1.7k tokensUpdated yesterday
    Writing & ContentAuto-check passed

More from Xiaoyangy/novel-studio

All 18 skills in this repo
  • Story Long Write

    Xiaoyangy/novel-studio

    长篇网文写作方法论与 novel-studio pipeline 适配器。用于把长篇开书、大纲、日更、续写、重写等需求整理为 pipeline 输入;在 novel-studio 内禁止直接生成正文。触发方式:/story-long-write、/写长篇、「帮我开书」「写大纲」「日更」「续写」「继续写」「修改第X章」「回炉」「重写第X章」。

    131 GitHub stars~9k tokensUpdated 18 days ago
    Auto-check passed
  • Story Short Write

    Xiaoyangy/novel-studio

    短篇网文写作方法论与 novel-studio pipeline 适配器。用于把短篇、盐言故事、拆文续写等需求整理为 pipeline 输入;在 novel-studio 内禁止直接生成正文。触发方式:/story-short-write、/写短篇、「帮我写一篇短篇」「写个盐言故事」。

    131 GitHub stars~5.6k tokensUpdated 18 days ago
    Auto-check passed
  • Story Douban Long Write

    Xiaoyangy/novel-studio

    豆瓣阅读原创长篇专项方法论与 novel-studio pipeline 适配器。用于把 15W-30W 字原创长篇的主题、类型、开头、文字、标签、简介和提交自检要求整理为 pipeline 输入;在 novel-studio 内禁止直接生成正文。触发方式:/story-douban-long-write、/豆瓣长篇、/豆瓣写作、「写一部豆瓣阅读原创长篇」「按豆瓣要求写长篇」。

    131 GitHub stars~1k tokensUpdated 18 days ago
    Auto-check passed
  • AI Novel Audit

    Xiaoyangy/novel-studio

    审核一段/一篇小说(或任意叙事性文本)的「AI 创作度」——判断它有多大可能由 AI 生成、或 AI 参与了多少。当用户想知道一段文字是不是 AI 写的、AI 味重不重、是人工还是 AI、AI 辅助了多少、帮忙鉴别/检测/审稿 AI 生成内容、给稿件的「人味/机味」打分时,都使用本技能。触发词包括但不限于:AI 创作度、AI 味、是不是 AI 写的、AI 生成检测、人工还是 AI、鉴别…

    131 GitHub stars~3.1k tokensUpdated 18 days ago
    Auto-check passed
  • Novel Pipeline

    Xiaoyangy/novel-studio

    把各功能串成一条可恢复的流水线:(共创→)写作→评审→重写→交付,按阶段执行、断点续跑。触发:「一条龙写完整本书」「从头跑完整个流程」「中断后接着跑」,想要无人值守端到端、且能中断恢复时使用。

    131 GitHub stars~632 tokensUpdated 18 days ago
    Auto-check passed
  • Novel Write

    Xiaoyangy/novel-studio

    用一句创作需求驱动 novel-studio 走可恢复 pipeline 完整创作(写作→评审→重写→导出)。触发:「帮我写本小说」「按这个设定写」「跑一次创作」,已有明确创作要求且希望无人值守端到端产出章节时使用。

    131 GitHub stars~441 tokensUpdated 18 days ago
    Auto-check passed

Questions about Story Short Analyze

What does Story Short Analyze do?

短篇网文拆文。拆解爆款短篇小说(番茄短篇 / 故事会 / 知乎盐选 / 追妻 / 世情 / 重生 / 虐渣等通俗题材)的故事核、结构、情感线、反转设计、写作手法、共鸣层次。单一全量拆解管道:跑完 Stage 2-6 产出完整拆文报告,落盘到 deconstruction-library/{书名}/,下游 story-short-write 同时读拆文报告 + 情节节点 + 写作手法 + 原文…. Story Short Analyze is an agent skill from Xiaoyangy/novel-studio.

When should I use Story Short Analyze?

Story Short Analyze fits situations like: tasks that involve Creative writing and fiction.

How do I install Story Short Analyze in Claude Code?

Run `npx skills add Xiaoyangy/novel-studio --skill story-short-analyze -a claude-code`. Or copy the skill folder (skills/story-short-analyze in Xiaoyangy/novel-studio) into .claude/skills/story-short-analyze in your project. Claude Code loads it when a task matches its description.

How do I install Story Short Analyze in Codex?

Run `npx skills add Xiaoyangy/novel-studio --skill story-short-analyze -a codex`. Or copy the skill folder (skills/story-short-analyze in Xiaoyangy/novel-studio) into .agents/skills/story-short-analyze in your project. Codex loads it when a task matches its description.

Can I use Story Short Analyze in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Xiaoyangy/novel-studio --skill story-short-analyze -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/story-short-analyze, .gemini/skills/story-short-analyze, .github/skills/story-short-analyze and .opencode/skills/story-short-analyze in your project.

What does Story Short Analyze need to run?

SKILL.md names no scripts, command-line tools or credentials: Story Short Analyze is instructions for the agent only.

Does Story Short Analyze access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Story Short Analyze safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Story Short Analyze use?

Story Short Analyze is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Story Short Analyze use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 65k tokens, read only when the agent opens those files.

What are the alternatives to Story Short Analyze?

Skills that share tags, products or a category with Story Short Analyze: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars), InkOS Creative Harness (Narcooo/inkos, 10k stars) and Novel Art (eternityspring/shuohao-skills, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Story Short Analyze?

Xiaoyangy (a GitHub user) maintains it in Xiaoyangy/novel-studio, which has 131 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on September 23, 2026.

Source: Xiaoyangy/novel-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.