submission

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Submission

投稿

Overview

概述

Get a finished manuscript out the door. This skill checks submission readiness, drafts the submission package (query letter, pitch, synopsis, blurb, comp titles), builds the manuscript in submission format, and keeps a tracker of where the book has gone. Package files live under

submission/

in the story project. The author sends every submission themselves; this skill prepares materials and records outcomes.

让已完成的手稿顺利投出去。此 skill 会检查投稿准备度，起草投稿材料包（查询函、pitch、梗概、blurb、对标作品），按投稿格式构建手稿，并维护一份手稿投递去向的追踪表。材料包文件位于故事项目的

submission/

目录下。作者自行发送每一次投稿；此 skill 负责准备材料并记录结果。

Prerequisites

前置条件

A story project with a complete or near-complete draft. Verify

story.md

exists in the project root and read its

status

genre

sub-genre

premise

author

(or

authors

for a co-written book),

contact

, and

language

fields. If

status

is not

complete

revising

, tell the user the package can be drafted now but the readiness check will fail until the draft is finished.

需要一个已有完整或接近完整草稿的故事项目。确认项目根目录存在

story.md

，并读取其中的

status

、

genre

、

sub-genre

、

premise

、

author

（合著书籍则使用

authors

）、

contact

和

language

字段。如果

status

不是

complete

或

revising

，告知用户现在可以起草材料包，但在草稿完成前准备度检查不会通过。

Language And Market

语言与市场

language

(a missing field means

en

) is the book's language. Ask which market the user is submitting to. The query letter, Shunn manuscript format, comp conventions, and word-count norms in the references are the English-language (mainly US and UK) market's. Other markets have their own practice: some publishers take submissions directly rather than through agents, and many ask for a synopsis and sample pages in their own format. Ask the user for the guidelines of the agents or publishers they are targeting and follow those; never present English-market conventions as universal. Write the package in the language the agent or publisher reads, which is usually the book's.

language

（缺少此字段时视为

en

）表示书籍的语言。询问用户要向哪个市场投稿。参考资料中的查询函、Shunn 手稿格式、对标作品惯例和字数规范适用于英语市场（主要是美国和英国）。其他市场有各自的惯例：有些出版社直接接收投稿，而不是通过 Agent；许多出版社会要求按其专有格式提供梗概和样章。应询问用户目标 Agent 或出版社的投稿指南并遵循这些指南；绝不能将英语市场惯例说成普遍规则。材料包应使用目标 Agent 或出版社阅读的语言，通常也就是书籍的语言。

When to Use

何时使用

Checking whether a manuscript is ready to submit
Drafting or revising a query letter, pitch, synopsis, blurb, or comp list
Building a Shunn-format manuscript for agents or magazines
Writing a retailer or back-cover description for self-publishing
Recording queries sent and responses received
Submitting short fiction to magazines, anthologies, or contests: simultaneous or exclusive submissions, rights, response windows, and status queries
Choosing and ordering the stories for a collection, and its previously-published acknowledgements
NOT for self-publishing production (ISBNs, retailer metadata, print interiors, launch, rights deals and contracts): use the
```
publishing
```
skill. This skill still drafts the blurb and retailer description it uses, and records the rights a short-fiction market buys
NOT for pitching a series of several books or writing its series overview (use
```
series-continuity
```
); the query for book one is still drafted here
NOT for revising the manuscript itself (use
```
revision-continuity
```
)
NOT for reader feedback rounds (use
```
feedback-triage
```
)

检查手稿是否已准备好投稿
起草或修订查询函、pitch、梗概、blurb 或对标作品清单
为 Agent 或杂志构建 Shunn 格式手稿
为自出版撰写零售商或封底简介
记录已发出的查询函和收到的回复
向杂志、选集或竞赛投稿短篇小说：同时或独家投稿、权利、回复时限和状态查询
为选集选择和排序故事，并根据既往发表情况撰写致谢
不适用于自出版制作（ISBN、零售商元数据、纸质书内页、发布、版权交易和合同）：使用
```
publishing
```
skill。此 skill 仍会起草自出版所用的 blurb 和零售商简介，并记录短篇小说市场购买的权利
不适用于推介包含数本书的系列或撰写系列概览（使用
```
series-continuity
```
）；第一本书的查询函仍在此起草
不适用于修订手稿本身（使用
```
revision-continuity
```
）
不适用于读者反馈环节（使用
```
feedback-triage
```
）

Hard Rules

硬性规则

Never invent the author's bio, credentials, awards, publication history, platform, or contact details. Ask the user, or leave a clearly marked
```
[TODO: author to supply]
```
placeholder.
Never invent agent, publisher, or market names, submission guidelines, pay rates, rights terms, response times, dates, or responses. Tracker entries come from the user.
Never send, email, or upload anything. The user submits.
Never claim sales figures, bestseller status, awards, or endorsements for comp titles or the author that the user has not confirmed.
Package copy describes the book as written. Read the manuscript and the bible; do not promise events, tone, or an ending the draft does not deliver.

绝不虚构作者简介、资历、奖项、发表经历、平台或联系方式。询问用户，或保留标记清晰的
```
[TODO: author to supply]
```
占位符。
绝不虚构 Agent、出版社或市场名称、投稿指南、稿酬标准、权利条款、回复时间、日期或回复内容。追踪表中的条目必须来自用户提供的信息。
绝不代为发送、电子邮件发送或上传任何内容。投稿由用户自行完成。
除非用户已经确认，否则绝不声称对标作品或作者拥有销量、畅销书地位、奖项或背书。
材料包文案应如实描述已经写出的内容。阅读手稿和故事设定集（bible）；不要承诺草稿并未呈现的情节、基调或结局。

Workflow

工作流

1. Readiness check

1. 准备度检查

Run the deterministic checks and report every finding before drafting:

shell

story reindex .
story wordcount . --write
story check .
story prose .
story report .

Review the output of the commands above:

```
story check .
```
(validate, links, and continuity) has no errors. List warnings for the user to accept or fix.
```
story prose .
```
shows no avoided spellings, and the user has reviewed the other findings. If
```
style-sheet.md
```
is missing or still the scaffold, suggest the
```
voice-style
```
skill first.
No
```
[TODO
```
markers remain in chapter prose.
```
story validate
```
warns about each chapter that still has one.
Open questions and planted promises are resolved, or deliberately left for a sequel (check
```
story.md
```
```
precedes
```
). Once
```
story.md
```
is
```
status: complete
```
, every open question and planned or planted promise or clue is a
```
story continuity
```
error, which fails the story-checks CI. An undecided thread stays open: a promise or clue at
```
planned
```
or
```
planted
```
, or a question at
```
open
```
. Once the user confirms that a thread pays off in the next book, record that decision in
```
continuity/exemptions.md
```
rather than changing the thread's status:
yaml
```
---
type: exemption-log
exemptions:
  - code: complete-with-open-promise
    pattern: "continuity/promises/the-sealed-letter.md is still planted"
    reason: "Pays off in book two."
---
```
Rerun
```
story continuity .
```
and confirm the finding shows as
```
dismissed
```
.

Then check what the CLI does not report:

Every chapter has
```
status: revised
```
,
```
final
```
, or
```
complete
```
. List any still at
```
outline
```
or
```
draft
```
.
The total word count sits inside the range for the category in
```
references/word-count-norms.md
```
. Those ranges are rough conventions for the English-language market only: state the number and the range, and ask the user to confirm current norms for their market. For a book in another language, report the count and ask for that market's norms instead. A Chinese or Japanese book is counted in characters: report
```
story wordcount .
```
's character total, and
```
story validate .
```
checks
```
target-characters
```
against per-form character ranges where a source sets one. Never pad or cut to hit a number without the user's direction. When the count is well outside the range and the user wants to change it, hand the book to
```
revision-continuity
```
's length pass (
```
../revision-continuity/references/pass-checklists.md#length-pass
```
), which budgets the cut or expansion by chapter and arc instead of trimming every chapter evenly.

Give a verdict:

ready

ready-with-caveats

(list them), or

not-ready

(list the blockers and hand them to

revision-continuity

运行确定性检查，并在起草前报告每项检查结果：

shell

story reindex .
story wordcount . --write
story check .
story prose .
story report .

检查上述命令的输出：

```
story check .
```
（校验、链接和连续性）没有错误。列出警告，供用户接受或修复。
```
story prose .
```
没有列出应避免的拼写，并且用户已审阅其他发现。如果
```
style-sheet.md
```
缺失或仍为脚手架，建议先使用
```
voice-style
```
skill。
章节正文中不再残留任何
```
[TODO
```
标记。
```
story validate
```
会警告仍含此类标记的每个章节。
悬而未决的问题和已经埋设的伏笔均已解决，或有意留待续集处理（检查
```
story.md
```
中的
```
precedes
```
）。一旦
```
story.md
```
设为
```
status: complete
```
，每个悬而未决的问题以及处于计划中或已埋设状态的伏笔或线索都会成为
```
story continuity
```
错误，并导致 story-checks CI 失败。尚未决定的情节线应保持开放状态：伏笔或线索保持在
```
planned
```
或
```
planted
```
，问题保持在
```
open
```
。一旦用户确认某条情节线会在下一本书中兑现，应将这项决定记录在
```
continuity/exemptions.md
```
中，而不是更改该情节线的状态：
yaml
```
---
type: exemption-log
exemptions:
  - code: complete-with-open-promise
    pattern: "continuity/promises/the-sealed-letter.md is still planted"
    reason: "Pays off in book two."
---
```
重新运行
```
story continuity .
```
，并确认该项发现显示为
```
dismissed
```
。

然后检查 CLI 未报告的事项：

每个章节的
```
status
```
都是
```
revised
```
、
```
final
```
或
```
complete
```
。列出仍处于
```
outline
```
或
```
draft
```
状态的章节。
总字数应处于
```
references/word-count-norms.md
```
中相应类别的范围内。这些范围仅是英语市场的粗略惯例：说明当前字数和范围，并请用户确认其市场的现行规范。对于其他语言的书籍，报告字数，并询问相应市场的规范。中文或日文书籍按字符数统计：报告
```
story wordcount .
```
返回的字符总数；如果来源为某种体裁设定了字符数范围，
```
story validate .
```
会检查
```
target-characters
```
是否符合相应范围。未经用户指示，绝不通过灌水或删减来凑数字。如果字数明显超出范围且用户希望调整篇幅，应将书籍交给
```
revision-continuity
```
的篇幅处理流程（
```
../revision-continuity/references/pass-checklists.md#length-pass
```
）。该流程按章节和情节弧分配删减或扩写额度，而不是平均削减每个章节。

给出结论：

ready

、

ready-with-caveats

（列出注意事项），或

not-ready

（列出阻碍项并移交给

revision-continuity

）。

2. Pitch and logline

2. Pitch 与 logline

Read
```
story.md
```
(premise, synopsis), the main arc files, and the protagonist's character file.
Draft a one-sentence pitch: protagonist + goal + obstacle + stakes, in under 35 words.
```
../story-init/references/title-logline.md
```
has the logline recipe.
Offer two or three variants; the user picks. Save the chosen pitch at the top of
```
submission/query.md
```
.

阅读
```
story.md
```
（
```
premise
```
、
```
synopsis
```
）、主要情节弧文件和主角角色文件。
起草一句话 pitch：主角 + 目标 + 障碍 + 利害关系，控制在 35 词以内。
```
../story-init/references/title-logline.md
```
中提供了 logline 公式。
提供两到三个版本供用户选择。将选定的 pitch 保存到
```
submission/query.md
```
顶部。

3. Comp titles

3. 对标作品

references/comp-titles.md

. Propose candidates with a one-line reason each, mark every one unverified until the user confirms year, category, and fit, and save the agreed list to

submission/comps.md

遵循

references/comp-titles.md

。提出候选作品并为每部作品给出一句话理由；在用户确认年份、类别和匹配度之前，将所有候选作品标记为未经验证，并将确认后的清单保存到

submission/comps.md

。

4. Query letter

4. 查询函

references/query-letter.md

. Draft

submission/query.md

with the hook, one or two book paragraphs, the metadata line (title, genre, word count rounded to the nearest thousand, comps), and a bio placeholder the author fills in. Keep the letter between 250 and 350 words. If the user names a specific agent, add a personalization line only from facts the user provides.

遵循

references/query-letter.md

。起草

submission/query.md

，其中应包含开场钩子、一到两段书籍介绍、metadata 行（标题、类型、按千字取整的字数、对标作品），以及供作者填写的作者简介占位符。将信件控制在 250 到 350 词之间。如果用户指定了某位 Agent，仅根据用户提供的事实添加个性化语句。

5. Synopsis

5. 梗概

Generate the mechanical draft:

shell

story synopsis . --pages 1 --out submission/synopsis-1-page.md
story synopsis . --pages 3 --out submission/synopsis-3-page.md

The CLI output is a scaffold stitched from the
```
story.md
```
synopsis and each arc's Setup, Rising Action, Climax, and Resolution sections. Rewrite it into polished prose: present tense, third person, main characters' names in capitals on first use, every major turn, and the ending revealed. Agents expect the ending; never withhold it.
Keep the 1-page version near 500 words and the 3-page version near 1,500. Overwrite the generated files with the rewritten versions and add the frontmatter from Conventions below.
If the output is thin, the arc files are thin: fill the missing arc sections with the
```
plot-structure
```
skill, rerun, then rewrite.
```
--out
```
never replaces an existing file in
```
submission/
```
, so to rerun, write to
```
dist/
```
and merge, or delete the generated file first after checking with the user that it holds no rewriting they want to keep.

生成机械化草稿：

shell

story synopsis . --pages 1 --out submission/synopsis-1-page.md
story synopsis . --pages 3 --out submission/synopsis-3-page.md

CLI 输出是一个脚手架，由
```
story.md
```
中的梗概以及每个情节弧的 Setup、Rising Action、Climax 和 Resolution 部分拼接而成。将其改写为流畅的散文：使用现在时和第三人称，主要角色姓名首次出现时使用大写字母，涵盖所有重大转折，并揭示结局。Agent 期待看到结局；绝不隐瞒结局。
将 1 页版本控制在约 500 词，3 页版本控制在约 1,500 词。使用改写后的版本覆盖生成的文件，并添加下方“约定”中的 frontmatter。
如果输出内容单薄，说明情节弧文件也很单薄：使用
```
plot-structure
```
skill 补齐缺失的情节弧部分，重新运行，然后再次改写。
```
--out
```
不会替换
```
submission/
```
中已有的文件，因此如需重新生成，应先输出到
```
dist/
```
再合并，或在确认用户不需要保留其中已改写的内容后先删除生成文件。

6. Blurb and retailer description

6. Blurb 与零售商简介

references/blurb.md

. Draft

submission/blurb.md

with a tagline, the back-cover copy (150-200 words), and, for self-publishing, a retailer description with the same copy plus a comp line if the user wants one. The blurb never reveals the ending.

This skill owns the retailer description:

submission/blurb.md

is its only draft, and the

publishing

skill reads it there. Keep it and the

description

field in

story.md

in step when the user self-publishes.

遵循

references/blurb.md

。起草

submission/blurb.md

，其中包含一句宣传语、封底文案（150 至 200 词），以及用于自出版的零售商简介；如果用户需要，可在同一份文案后加上一行对标作品。Blurb 绝不揭示结局。

本 skill 负责零售商简介：

submission/blurb.md

是其唯一的草稿，

publishing

skill 会从该文件读取内容。用户选择自出版时，应保持该文件与

story.md

中的

description

字段同步。

7. Build the manuscript

7. 构建手稿

For agents and short-fiction markets, build Shunn manuscript format:

shell

story build . --format docx --shunn
story build . --format shunn

These write

dist/<story-id>.shunn.docx

and

dist/<story-id>.shunn.md

. The DOCX has a running head on every page after the first: the author's surname, a short title, and the page number (

Writer / The Last Ember / 2

). The build takes the last word of the first author's name (the first word in a Chinese, Japanese, Korean, or Hungarian book) and the title before any subtitle, and cuts a long one to fit. When either is wrong, such as

Le Guin

, set

surname

short-title

story.md

; the build uses them whole. For a market that takes PDF, add

--pdf

to the

shunn

build: it renders

dist/<story-id>.shunn.pdf

(US Letter, Courier, double-spaced, running head) with a paged-media engine the user has installed, and stops with install hints when there is none.

The PDF and DOCX are US Letter, which North American markets expect. For a market that asks for A4 (most outside North America), add

--paper a4

to the

--pdf

docx --shunn

build; the 1-inch margins stay. Go by the market's guidelines, not the author's language or country. An author who always submits on A4 can set

paper: a4

under a

build

entry in

cli-defaults

story.md

; other builds ignore it.

Confirm

story.md

has

author

(or

authors

) and

contact

first; the title page uses them, joining co-authors with "and". Shunn builds leave out

matter/

pages, as submissions expect. With

form: short-story

form: flash

story.md

they use Shunn's short-story layout: the text runs on from the title block, chapters become sections separated by a centred

, and there are no chapter headings or page breaks. Any other form starts each chapter on a new page. For self-publishing, hand off to the

publishing

skill, which covers EPUB and print builds (

story build . --format epub

--format print --trim 6x9

), retailer metadata, and launch.

For a one-page metadata sheet to check the pitch facts against (title, series, author, word count, description length against retailer limits, keywords, BISAC subjects, and missing fields), run:

shell

story build . --format metadata

story.md

has an

ai-disclosure

, check each agent's or market's policy on AI-assisted work and disclose as they require; see the

editorial-review

skill. Tell the user which file in

dist/

to send, and remind them to check each agent's or market's guidelines for format and attachment rules.

面向 Agent 和短篇小说市场时，按 Shunn 手稿格式构建：

shell

story build . --format docx --shunn
story build . --format shunn

这些命令会生成

dist/<story-id>.shunn.docx

和

dist/<story-id>.shunn.md

。DOCX 第一页之后的每一页都有页眉，内容为作者姓氏、短标题和页码（

Writer / The Last Ember / 2

）。构建时会取第一位作者姓名的最后一个词（对于中文、日文、韩文或匈牙利文书籍则取第一个词），并取副标题之前的标题；内容过长时会截短以适配。如果其中任何一项不正确，例如

Le Guin

，请在

story.md

中设置

surname

或

short-title

；构建时会完整使用这些值。

对于接收 PDF 的市场，在

shunn

构建中添加

--pdf

：使用用户已安装的分页媒体引擎生成

dist/<story-id>.shunn.pdf

（US Letter、Courier、双倍行距、页眉）；如果未安装引擎，则停止并提供安装提示。

PDF 和 DOCX 使用 US Letter，这是北美市场通常采用的规格。对于要求 A4 的市场（北美以外的大多数市场），在

--pdf

或

docx --shunn

构建中添加

--paper a4

；1 英寸页边距保持不变。应遵循目标市场的指南，而不是作者的语言或国家。始终以 A4 投稿的作者可以在

story.md

的

cli-defaults

中某个

build

条目下设置

paper: a4

；其他构建会忽略该设置。

先确认

story.md

中包含

author

（或

authors

）和

contact

；标题页会使用这些信息，合著者之间以“and”连接。Shunn 构建会排除

matter/

页面，因为投稿通常不需要这些页面。当

story.md

中包含

form: short-story

或

form: flash

时，会采用 Shunn 的短篇小说版式：正文从标题块处连续排版，各章变为独立小节，以居中的

分隔，不使用章节标题或分页符。其他任何体裁都会让每章从新的一页开始。对于自出版，应移交给

publishing

skill；该 skill 涵盖 EPUB 和纸质书构建（

story build . --format epub

、

--format print --trim 6x9

）、零售商元数据和发布工作。

如需生成一页 metadata 表，以核对 pitch 中的事实（标题、系列、作者、字数、零售商限制下的简介长度、关键词、BISAC 主题和缺失字段），请运行：

shell

story build . --format metadata

如果

story.md

中包含

ai-disclosure

，检查每位 Agent 或每个市场关于 AI 辅助创作的政策，并按其要求进行披露；参见

editorial-review

skill。

告诉用户应发送

dist/

中的哪个文件，并提醒用户查看每位 Agent 或每个市场的投稿指南，以确认格式和附件规则。

8. Track submissions

8. 追踪投稿

Create

submission/tracker.md

from

references/tracker-template.md

the first time the user reports sending a submission. Add or update a row each time the user reports a submission or a response, using only what they tell you. On request, summarize: queries out, partial and full requests, offers, declines, and entries with no response after the window the user sets.

用户第一次报告已发送投稿时，根据

references/tracker-template.md

创建

submission/tracker.md

。此后每当用户报告投稿或收到回复时，添加或更新一行，并且只使用用户提供的信息。根据用户请求，汇总：已发出的查询函、部分请求和全文请求、邀约、拒绝，以及超过用户设定时限后仍未回复的条目。

9. Short fiction and collections

9. 短篇创作与选集

For a short story, novelette, or novella going to magazines, anthologies, or contests, follow

references/short-fiction-markets.md

instead of steps 2 to 6: the story goes out in full with a short cover letter. Use the short-fiction tracker columns (submission type, rights offered) and the publication history section from that reference, and check the tracker before suggesting a market: a story with an open exclusive submission goes nowhere else, and an exclusive market needs a story with no open submissions. For a market that reads anonymously, add

--anonymous

to the Shunn build, which leaves out every name, the running head's surname included. To assemble a collection, follow its "Assemble a collection" section: choose the stories, find the linking threads, propose an order, and draft the acknowledgements from the publication history.

短篇小说、novelette 或 novella 投稿给杂志、选集或竞赛时，遵循

references/short-fiction-markets.md

，而不是执行第 2 至第 6 步：作品需全文投稿，并附上一封简短的投稿附信。使用该参考资料中的短篇小说追踪表列（投稿类型、所授予的权利）和发表历史部分；在建议目标市场前检查追踪表：处于开放独家投稿状态的作品不能再投往其他市场，而独家市场需要选择没有开放投稿状态的作品。如果目标市场采用匿名评审，请在 Shunn 构建中添加

--anonymous

，这会移除所有姓名，包括页眉中的作者姓氏。要汇编选集，请遵循该参考资料中的“Assemble a collection（汇编选集）”一节：选择故事、寻找串联线索、拟定顺序，并根据发表历史起草致谢。

Conventions

约定

Package files:

submission/query.md

submission/comps.md

submission/synopsis-1-page.md

submission/synopsis-3-page.md

submission/blurb.md

submission/tracker.md

. The

series-continuity

skill owns

submission/series-pitch.md

, the series overview saved in book one; this skill does not draft it.

Each file has YAML frontmatter with a

type

(

query

comps

synopsis

blurb

submission-tracker

, and

series-pitch

for the file

series-continuity

writes) and

updated: YYYY-MM-DD

```
submission/
```
is outside the story model: the CLI does not validate it and builds never include it.
Word counts in submission copy come from
```
story wordcount .
```
, rounded to the nearest thousand (
```
87,000 words
```
). A Chinese or Japanese book gives its length in characters, as
```
story wordcount .
```
reports it (
```
12万字
```
, or sheets of 400字 when a Japanese contest asks for them).

Tracker statuses:

queried

requested-partial

requested-full

offer

declined

no-response

withdrawn

, plus

submitted

and

held

for short fiction.

When the manuscript changes after the package is drafted, reread the package and update anything the revision made untrue.

材料包文件：

submission/query.md

、

submission/comps.md

、

submission/synopsis-1-page.md

、

submission/synopsis-3-page.md

、

submission/blurb.md

、

submission/tracker.md

。

series-continuity

skill 负责

submission/series-pitch.md

，即保存在第一本书中的系列概览；本 skill 不起草该文件。

每个文件都带有 YAML frontmatter，其中包含
```
type
```
（
```
query
```
、
```
comps
```
、
```
synopsis
```
、
```
blurb
```
、
```
submission-tracker
```
，以及由
```
series-continuity
```
写入的
```
series-pitch
```
）和
```
updated: YYYY-MM-DD
```
。
```
submission/
```
位于故事模型之外：CLI 不会校验它，构建也不会包含它。
投稿文案中的字数来自
```
story wordcount .
```
，并按千字取整（
```
87,000 words
```
）。中文或日文书籍的长度按
```
story wordcount .
```
报告的字符数表示（
```
12万字
```
；如果日本竞赛要求，也可按每份 400 字计算）。

追踪状态：

queried

、

requested-partial

、

requested-full

、

offer

、

declined

、

no-response

、

withdrawn

，短篇小说还可使用

submitted

和

held

。

材料包起草后如果手稿发生变化，应重新阅读材料包，并更新所有因修订而不再准确的内容。

CLI Maintenance

CLI 维护

Use the Story CLI when it is available. If

story

is not installed, use the bundled fallback

node ../story-maintenance/scripts/story.js

with the same arguments. Use

node <checkout>/bin/story.js

instead only when the user names a Story Skills repository checkout or you are working in one. Write the script as an absolute path (resolve the fallback relative to this skill folder) and run it from the folder you would run

story

from, so

and other relative paths keep their meaning. Use Node, not Bun or a package script: Bun would load that folder's

bunfig.toml

(which can run code) and

.env

, and a package script runs from the checkout's root. If no CLI is available, perform the readiness checks manually and write the synopsis from the arc files.

After the readiness check, or any manuscript change made for submission:

shell

story reindex .
story wordcount . --write
story check .
story prose .

可以使用 Story CLI 时，优先使用它。如果未安装

story

，则使用捆绑的回退脚本

node ../story-maintenance/scripts/story.js

，并传入相同参数。只有当用户点名 Story Skills 仓库 checkout，或当前正在该仓库中工作时，才改用

node <checkout>/bin/story.js

。将脚本路径写为绝对路径（相对于本 skill 目录解析回退脚本），并从原本应运行

story

的目录执行它，从而保持

和其他相对路径的含义。使用 Node，不要使用 Bun 或 package script：Bun 会加载该目录下的

bunfig.toml

（其中可能执行代码）和

.env

，而 package script 会从 checkout 的根目录运行。如果没有可用的 CLI，则手动执行准备度检查，并根据情节弧文件编写梗概。

完成准备度检查后，或为投稿而修改手稿后，运行：

shell

story reindex .
story wordcount . --write
story check .
story prose .

Reference Files

参考文件

references/query-letter.md
- Query structure (hook, book paragraphs, metadata line, bio), length, personalization, and common mistakes
references/blurb.md
- Back-cover and retailer description formulas for genre fiction, length, and taglines
references/comp-titles.md
- How to choose comparable titles, how to phrase them, and the verification rule
references/word-count-norms.md
- Rough word-count ranges by category for the English-language market only, to confirm with the user

references/tracker-template.md
-

submission/tracker.md

template and status definitions

references/short-fiction-markets.md
- Magazine, anthology, and contest submissions (simultaneous and exclusive, rights, response times and status queries, tracker columns, publication history) and assembling a story collection

references/query-letter.md
- 查询函结构（开场钩子、书籍介绍段落、metadata 行、作者简介）、长度、个性化方式和常见错误
references/blurb.md
- 类型小说的封底文案和零售商简介公式、篇幅及宣传语
references/comp-titles.md
- 如何选择对标作品、如何表述以及验证规则
references/word-count-norms.md
- 仅适用于英语市场的各类别粗略字数范围，需向用户确认

references/tracker-template.md
-

submission/tracker.md

模板和状态定义

references/short-fiction-markets.md
- 杂志、选集和竞赛投稿（同时或独家投稿、权利、回复时间和状态查询）、追踪表列、发表历史，以及故事选集的汇编

Shared Conventions

共享约定

Every story skill follows the shared conventions in

../story-maintenance/references/conventions.md

, resolved relative to this skill folder. Read it before creating, renaming, or linking story files. If that file is missing because this skill was installed without

story-maintenance

, the essentials are: kebab-case ids and filenames, YAML frontmatter on every story-project file,

_index.md

registry tables that

story reindex

rebuilds (never edit them by hand), bidirectional links between entities,

characters

for who is on the page and

mentions

for who is only referred to,

status: deceased

plus

died-in: chapter-{NN}

for deaths, and no project-local generator or build scripts (run only the installed or bundled Story CLI).

每个故事 skill 都遵循

../story-maintenance/references/conventions.md

中的共享约定，该路径相对于本 skill 目录解析。在创建、重命名或链接故事文件之前，应先阅读该文件。如果安装本 skill 时未同时安装

story-maintenance

，导致该文件缺失，则需遵循以下基本要求：id 和文件名使用 kebab-case 格式；每个故事项目文件都包含 YAML frontmatter；

_index.md

注册表由

story reindex

重建（绝不要手动编辑）；实体之间建立双向链接；实际登场的角色使用

characters

，仅被提及的角色使用

mentions

；角色死亡时使用

status: deceased

，并通过

died-in: chapter-{NN}

记录死亡章节；项目内不得放置生成器或构建脚本（只运行已安装或捆绑的 Story CLI）。