SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsstory-publish

story-publish

Writing & research

View repository

Updated 11-04 03:55

About this skill

story-publish: publishing material preparation

Organize the work's existing settings, outlines, and the author's decisions into the materials required for the publishing platform's book creation form, verify them against platform rules, and save them as 发布资料-<平台>.md. Plot planning and main text writing belong to writing skills such as story-long-write ; when the author only says "start a book", that also goes there; this skill also does not log into the backend, fill out forms, or publish on the author's behalf.

Principles

  • Only what the author confirms is final. Each field is marked with one status:已确认(explicitly specified or accepted by the author),建议(derived from the work materials or newly drafted),待确认(missing, vague, contradictory),待平台核实(platform rules unclear or inconsistent with the interface). Silence does not count as confirmation; if the author accepts an entire set of candidate options, that counts as confirming each item listed in it. Story synopses and outlines provided by the author are source material and are not automatically treated as the platform's "work synopsis".
  • Do not change values the author has already set without permission. If there are problems with the title, synopsis, or pen name, point them out and give suggestions while keeping the original values.
  • Platform candidates are taken only from this skill's platform reference files. Do not rely on memory, do not borrow from ranking scans, deconstruction, or topic selection materials, and do not share between platforms. When there are no story facts, ask first; do not invent characters, plot, or selling points.
  • Preparation complete does not mean published. When the materials are complete, only say "publishing material preparation complete", not "submitted", "under review", or "published".

Read the work materials

Book directory: the author-specified one takes priority, otherwise .active-book; if the reference is unclear or multiple books cannot be distinguished, ask the author and do not guess from the directory name. Read only; do not change settings or start a writing phase.

  • Long-form:设定/题材定位.md 's basic information and "author decisions"; when the protagonist needs to be verified, read 设定/角色/ 's character cards; when the synopsis needs plot support, read 大纲/大纲.md and the related volume outlines and detailed outlines.
  • Short stories:设定.md and 小节大纲.md. The submission lead-in is the beginning of the main text and is not treated as the platform synopsis.
  • 选题决策.md, deconstruction, and ranking scan materials can only support suggestions; provisional titles and character card names do not automatically become final. When no title is written in the settings, use the book directory name as the current title.

Platform

Currently supports Fanqie Novel; read references/fanqie.md, and read candidate files as needed according to its guidance.

Other platforms: explicitly say "not currently adapted" and ask the author to provide a dated screenshot of the book creation form or official documentation; before receiving it, only provide non-platform-specific draft titles and synopses, and do not apply Fanqie rules. When adding a platform, write the reference file following the structure of fanqie.md , noting the verification date and scope.

Workflow

  1. Confirm the target platform and work type (long-form/short story), and state at the beginning of the reply the platform, adaptation status, and the verification date and scope in the platform reference.
  2. Read the work materials, note the values the author has already set, and generate candidates only for the fields the author requests; for candidate titles, first self-check the character count and symbols according to the platform reference's title rules, and mark the character count.
  3. Check the allowed values, quantity limits and lengths field by field against the platform reference; mark limits not stated in the reference as "not specified in the materials".
  4. After the book title and synopsis are confirmed, handle them according to the "Cover" section.
  5. When every field requested in this round has a conclusion (confirmed, or the author has decided not to fill it in), save the file; if it has not been saved yet, give the complete draft in the reply. After saving, the reply should only state what was written this time, what is still missing, and give the file path, without reposting the full text.
  6. The publication materials are the basis for the values entered on the platform. When the confirmed book title is inconsistent with the one in 设定/题材定位.md(for short stories, 设定.md), tell the author after saving; changing the setting and the book directory is left to the writing skill, and this skill does not change them.

Cover

First check which image-generation tools can actually be called in the current session (do not judge by model name), then ask the author to choose "generate directly", "prompt only" or "defer"; if the author has already chosen and it is still executable, do not ask again. Do not automatically switch to a paid API because a tool is missing.

Pass the confirmed book title, synopsis, pen name, platform, genre and character/scene facts to story-cover, and ask again if the pen name is missing: for direct generation, follow its complete flow; for prompt only, follow its Steps 1-3. In both cases, write the full prompt text verbatim into the "Cover" subsection, and if image generation succeeds, additionally record the image path.story-cover If it is unavailable (for example, not discoverable when OpenClaw lacks a Key), fails, or the author defers, write the reason into "Pending author confirmation" without blocking other fields; switching to prompt only after image generation fails requires the author's consent. If there is only a prompt or an unsaved image, do not say "the cover is ready".story-cover Its style and size suggestions do not replace the platform specifications.

Publication materials file

The file name is 发布资料-<目标平台>.md, and for the target platform use the original text of platform in the platform reference metadata (for example, 发布资料-番茄小说.md). Place it in the book directory: for long-form works, it is the parent of 正文/ ; for short stories, it is the directory containing 正文.md ; if there is no main text yet, place it directly under the book directory. If a file with the same name already exists, read it first; if it conflicts with the author's manual edits, ask first and do not overwrite; rearrange the old file according to the format below while preserving the author's handwritten content.

This file will later be read by a program to fill in the backend form, and the format is a fixed contract:

  • At the beginning, one metadata item per line, in order: > 格式版本：1、> 目标平台：<platform>、> 作品类型：长篇 or 短故事、> 核验：<核验日期与范围>。
  • After the metadata comes # 书本名称：<书名>, then the basic fields,## 封面, the platform's tag or category subsection,## 作品简介、## 待作者确认、## 待平台核实、## 来源说明. The basic fields and tag subsection are based on the basics、tag_sections for that work type in the platform reference metadata, with each field on one line as - 字段：值, and multiple values for the same field separated by enumeration commas.
  • Field values have only three kinds: a confirmed value;（不填）, indicating the author has decided not to fill it in; left blank, indicating it is not decided yet and is listed in "Pending author confirmation". If the book title is undecided, write the title as # 书本名称：; if the synopsis is undecided, leave the subsection blank. Suggestions, explanations and placeholder words must never be written into field values.
  • Suggested drafts such as candidate book titles, synopses and tags, as well as matters for the author to check on the backend interface, all go in "Pending author confirmation"; missing rules or unclear scope go in "Pending platform verification"; if a section has no items, write "none". Sources and verification basis go in the final "Source notes".

Long-form example (Fanqie):

> 格式版本：1
> 目标平台：番茄小说
> 作品类型：长篇
> 核验：2026-10-29；标签对照 Web 创建作品弹窗，App 与提交结果未核验

# 书本名称：<书名>

- 作者/笔名：
- 签约模式：
- 目标读者：
- 主角1：
- 主角2：

## 封面

- 模式：<直接生成/仅提示词/暂缓；未选时留空>
- 状态：<提示词与图片的状态分开写>
- 提示词：<完整提示词原文>
- 图片：<已保存的图片路径>

## 阅读标签

- 主分类：
- 主题：
- 角色：
- 情节：

## 内容标签

- 情节：
- 情感：
- 人设：
- 世界观：

## 作品简介

## 待作者确认

## 待平台核实

## 来源说明

Long prompts can be placed in a code block. Do not list the complete candidate list unless the author asks for it.

Format check

After saving, probe in order python3、python、py, and run the one in the root directory of this skill scripts/check-publish-format.py <发布资料文件>The script is read-only: FAIL means the file does not conform to the contract, or contains options and tags that the platform does not have; it must be corrected and rerun. WARN means a confirmed value may be rejected by the platform (such as book title or length); relay this to the author, and do not change it on the author's behalf. When the environment cannot run the script, reread the file and check each item one by one, and tell the author that the automated check was not run.