AI Agent Hub
Back to skills
Webnovel Writing Dashboard icon

Webnovel Writing Dashboard

Content Creation Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md to install @user_5e9ef3eb/webnovel-writer-crazy.

About this skill

Problem

Long-form webnovel projects often scatter chapter drafts, character relationships, power systems, worldbuilding notes, and reader-hook metrics across files and local databases. The practical issue is not a lack of source material, but the absence of a stable read-only view: where the draft is, which chapters are planned or missing, whether character and faction relationships stay consistent, and how each chapter performs on hooks and satisfaction density. webnovel-writer-crazy targets that workflow by launching a local read-only dashboard for project status.

How It Works

The skill resolves PROJECT_ROOT, prepares Python module paths, validates frontend artifacts, and starts a local server. It listens on localhost by default and supports --port and --no-browser. After startup, it checks:

  • http://localhost:8080/api/story-runtime/health
  • http://localhost:8080/api/preflight

The dashboard exposes several views:

  • Project overview: title, genre, target word/chapter count, progress, and completion
  • Chapter management: written, planned, and unwritten chapters with word count and review scores
  • Entity graph: character relationships, faction distribution, and location links
  • Setting dictionary: character cards, power system, and key worldbuilding rules
  • Reader-hook data: per-chapter scores, satisfaction density, and hook quality
  • Story Runtime status: main-chain health, latest commit, and fallback notes

Boundaries

This is a read-only panel with no modification interface. File access is constrained to PROJECT_ROOT. Missing dist/, absent .webnovel/state.json, or port conflicts can cause blank pages or incomplete data. It is useful for status checks, pre-review consistency inspection, and setting browsing, not as an online editor or externally exposed service.

Use Cases

  • When writing a long webnovel, open the local dashboard to inspect current progress, chapter status, and unwritten chapters.
  • Before reviewing chapters, inspect character relationship graphs, faction maps, and location links to check setting consistency.
  • When evaluating reader retention, review per-chapter scores, satisfaction density, and hook quality.
  • When checking local project state, inspect Story Runtime health, latest commit status, and fallback notes.

Best For

  • Long-form webnovel authors who need to inspect progress and chapter lists without editing manuscript files.
  • Webnovel reviewers who need to verify character relationships, faction maps, and setting-dictionary consistency.
  • Editors analyzing reader retention who need per-chapter scores, satisfaction density, and hook quality.
  • Local system engineers who need to verify Dashboard, Story Runtime, and project data-file status.