submission

Submission Acceptance Diagnosis (submission)

Writing well doesn't necessarily mean you can get a contract. This skill examines the manuscript fromthe editor/signing perspectiveto help authors pass acceptance.

When to use

• Preparing to submit/sign, want to self-check first
• Writing/optimizing the book title, synopsis, and tags
• Golden three chapters acceptance checkup
• "Why wasn't my book signed / how do I improve my acceptance rate"

Workflow

A. Acceptance checkup (most commonly used)

1. Confirm the target platform (Fanqie/Jinjiang/Qidian/UC/Zhihu Yanxuan/Webnovel) → call references/submission-guide.md + references/platform-profiles.md
2. Check the length/word count threshold(call references/length-standards.md): Fanqie short stories must be ≥6000 to sign, long-form first signing ≥20,000, all-platform distribution ≥80,000; if the word count hasn't reached the threshold, first remind the author to add enough before submitting.
3. Check the first three chapters item by item according to the "golden three chapters acceptance standard" (call submission-guide's self-check list)
4. OutputSigning likelihood assessment + fatal discouragement points + item-by-item fixes：

【目标平台】
【签约可能性】高/中/低 + 一句话结论
【致命劝退点】最可能被拒的 1-3 点（按编辑视角排序）
  - 开篇是否 3 句抓人
  - 金手指/卖点上线时机
  - 三章内有无小高潮
  - 有无大段背景说明文（头号劝退）
  - 单章字数/节奏是否合平台
【逐条改法】每个问题给具体改法
【优先级】先改哪个最能提过稿率

B. Book title/synopsis/tags

• Book title: 3 candidates, highlighting the core selling point and payoff
• Synopsis: use the formula 身份钩 + 金手指转折 + 爽点预期 + 悬念尾钩(see submission-guide)
• Tags: suggest 3–5, the first = core selling point; for current popular tags use trends to check online

C. Submission strategy

• Platform adaptation suggestions for simultaneous submissions (Fanqie cut the setup, Qidian add worldbuilding, Jinjiang add a romance line)
• Reminders about stockpiled chapters and daily update assessments

D. Submission record linkage (record "why it didn't pass")

Link with the creation profile 06_投稿记录.md (format see references/project-memory.md, template templates/submission-log-template.md）：

• Before submitting: first read 06_投稿记录.md, pull out the historicalhigh-frequency rejection reason tags(such as #slow opening #late payoff #homogenization), and focus this checkup on these to avoid repeating them.
• After submitting: the user tells you the result,append a record: platform/date/result/editor feedback/your judgment/changes/review tags.
• Summarize: rejection reason tags accumulated 3 or more times = systemic problems; point them out clearly and give targeted fixes.

If there is no creation profile, prompt to use memory to create one.

Principles

• Look fromthe perspective of editors and system data, not from the perspective of the author's self-indulgence.
• The most common reason for rejection is "the opening setup is too long/the payoff is too slow"—check this first.
• Platform policies change; when it involves "what themes current platforms want", prompt to use trends to verify online.

Next steps

If problems are found in the checkup → use hook to revise the opening,idea to adjust the selling points,expand to rewrite the three chapters,review to recheck.

Before submitting, use proofread to go through it once moreTypos + sensitive/prohibited words(like Tomato's backend highlighting in red + one-click replacement), to avoid being rejected due to typos or triggering review.