About this skill

Problem

Publishing chapters in the Fanqie author backend mixes login state, validation, and two different UI flows. Manual publishing can miss cover, category, agreement, and reading-rate steps; short-story body is a React-controlled editor, so direct assignment or slow typing can fail.

How It Works

This skill drives the backend with Playwright headless Chromium and breaks publishing into checkable steps:
- Reads approved drafts from 05-草稿/可发布版/, moves them to 04-章节正文/ after success, and updates progress/project config files.
- Enforces title >= 5 characters, body >= 1000 characters, Arabic chapter numbers, and the 3-chapter daily limit.
- Keeps novel and short-story routes separate; for short stories it inserts body text in chunks via execCommand insertText, handles cover drawer, tree category, agreement checkbox, and sets trial reading through window.adapter.command.payNode.
- Supports dry-run, fill, submit, batch publishing, and login verification, with state in ~/.fanqie-storage.json and ~/.fanqie-publish-state.json.

Boundaries

Login state lasts about 30 days, so cookies need re-importing when expired. If a short-story submission fails, resume from the draft box instead of creating another draft, which can leave empty drafts. Category names must match the live UI, and success should be verified by the published list, draft box, and check_pre response rather than a page string alone.

Screenshots

Use Cases

A long-form author submits proofed chapters from the publishable draft folder to Fanqie.
A short-story author fills title, body, cover, category, and trial reading, then submits.
An operations staff member checks login state and resumes failed drafts within the daily limit.
An editor uses fill mode to verify selectors and form state before full submission.

Best For

Long-form webnovel authors who want proofed chapters submitted and archived automatically.
Short-story authors who need cover, category, agreement, and trial-reading steps handled.
Content operations staff who need daily login checks, draft recovery, and progress tracking.
Python automation engineers who maintain Playwright selectors and publishing validation.