Webnovel Writer plugin
A Claude Code plugin for long web novels: volume planning, chapter writing and review, memory of characters and plot, a state dashboard
- 7,626 ★ on the repository
- Last commit
- GPL-3.0
Broad access
Why this level
- The plugin installs Claude Code hooks that fire in every session and intercept file writes and Bash commands
- The agent runs Python scripts and writes many files into the book directory: chapters, state, index and backups
- Chapter text and queries go to external embedding and reranking services if you set keys
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/webnovel-writerDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The plugin installs Claude Code hooks that fire in every session and intercept file writes and Bash commands
- The agent runs Python scripts and writes many files into the book directory: chapters, state, index and backups
- Chapter text and queries go to external embedding and reranking services if you set keys
This is third-party code. Review the repository files before installing.
What it does
Webnovel Writer guides the author of a long web novel from the idea to hundreds of chapters and keeps world rules, character arcs and planted hooks from getting lost in the text. The plugin installs through the Claude Code marketplace and provides eight commands: `/webnovel-init` builds the book project, `/webnovel-plan` lays out a volume and chapters, `/webnovel-write` writes a chapter, `/webnovel-review` reviews chapters, `/webnovel-query` answers about the state, `/webnovel-learn` records techniques in project memory, `/webnovel-dashboard` opens the dashboard and `/webnovel-doctor` checks files and dependencies. A chapter goes through a strict nine-step chain. First the project is checked, then a context agent prepares the chapter brief, the text is drafted from the brief, and a reviewer checks it against several criteria, with serious findings blocking progress. Next come polish and a final check for traces of machine writing, a data agent extracts the chapter's facts, and they are recorded as an accepted chapter commit. From it the state in `state.json`, the index, the summaries, long-term memory and the vector store are updated. At the end the chapter is backed up. Search over earlier chapters runs in `auto` mode: vector search through an external embedding model first, and BM25 when no key is set. The book has 37 genre templates that can be mixed.
Who it is for. For authors of long Chinese-language web novels who write with Claude Code and want the plot and world of the book to stay consistent over hundreds of chapters.
Good fit when
- A novel is serialized by chapter and by chapter two hundred you need to remember characters' powers, timeline and open hooks
- You need to break a general concept into volumes, chapters and a timeline and keep them in project files
- Each chapter must be checked for consistency, pacing and character voice before publishing
- You want to blend several genres, such as a system novel and a school drama, from ready templates
- You want a dashboard showing characters, relationships, chapters and hook status without edit rights
Not a fit when
- You write in another language: the genre templates, interface and instructions are built for Chinese web novels
- You work in Cursor or Codex: version 6 targets only Claude Code, and the author keeps a separate v8 branch for other setups
- You need a short form without memory and planning: an ordinary model request is enough
- The GPL-3.0 license does not fit your project: the plugin is distributed under it entirely
Example request
Run /webnovel-write 45: prepare the context for chapter forty-five, write it, check it with the reviewer and show a report with findingsLimitations
- The master branch with this version 6 is in maintenance mode: the author fixes only critical bugs. New development happens on the v8 branch built on DeepSeek Harness, where installation differs.
- Vector search needs external embedding and reranking services (ModelScope and Jina by default) with your keys in the book's `.env` file. Chapter text and queries go to those services, and without a key the search falls back to BM25 and works worse.
- The plugin installs Claude Code hooks: at session start it prints a short project status, and before file writes and Bash commands it blocks direct edits to internal state files. The write check can be turned off with the `WEBNOVEL_DISABLE_RUNTIME_GUARD_HOOK` variable.
- The front page carries ads for three third-party model access intermediary services. They are not needed for the plugin to work, and SkillFoxx has not evaluated them.
- The author states the project was built with Claude Code, Gemini CLI and Codex by vibe coding. The license is GPL-3.0.
How to disable. Disable or remove the plugin with the Claude Code plugin commands: `claude plugin uninstall webnovel-writer@webnovel-writer-marketplace`. Uninstalling leaves the book directories (`正文`, `大纲`, `设定集`, `.story-system`, `.webnovel`) alone, so you can keep them as manuscripts or delete them by hand.
FAQ
What steps does `/webnovel-write` consist of?
Nine: a project and Story System health check, refreshing the chapter's runtime contract, a brief from the context agent, a draft, a multi-criteria review, polish with a final check, fact extraction by the data agent, chapter commit and writes to state, index, memory and the vector store, and then a backup. The rules forbid skipping or merging steps.
What happens if the reviewer finds a serious problem?
A serious finding blocks the move to polish and commit. It is fixed in place or settled with the author. Review runs one round, and on a failure only the failed step reruns with no need to roll the whole chapter back.
What is Story System and why `CHAPTER_COMMIT`?
Story System is the plugin's main chain: the `.story-system/` directory holds contracts before a chapter is written and accepted commits after it. The state in `state.json`, the `index.db` index, the summaries and the memory are derived views built from the accepted `CHAPTER_COMMIT`.
Can I do without keys for vector search?
Yes. Without an embedding key the system falls back to BM25 keyword search, and semantic recall of earlier chapters is weaker. Embeddings and reranking can be swapped for any service with an OpenAI-compatible interface.
What does the `/webnovel-dashboard` show?
Read-only views: project state, the relationship graph of characters and objects, chapter text, hooks and reader-retention data. The interface is prebuilt and ships with the plugin, so there is no build to run on your machine.
Discussion
No questions or reviews yet.
Related
PluginsA novel-writing skill with nine agents: setting, volume and chapter plans, prose, a machine-style check and an archive with character memory
A plugin for novels and serial fiction: a muse agent leads from idea to draft, while writer, critic, editor and canon-check agents each handle one job
A set of 13 skills for writing web fiction inside a coding agent: rank scanning, hit deconstruction, outline and prose, AI-flavor cleanup, cover art
24 skills for fiction in Markdown, from premise to print, and a story command that catches plot contradictions before readers do
A skill for writing a complete Chinese novel chapter by chapter: three-layer intake, preference memory, cliffhangers and automatic validation
A Claude Code plugin for the full blog lifecycle: strategy, writing, search and AI-citation optimization, audit and localization
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Webnovel Writer (this entry) | no | 7,626 | |
| chinese-novelist | no | 4,124 | a skill for a Chinese novel written chapter by chapter with an interview, preference memory and autochecks, with no fact base or state dashboard |
| awesome-novel | no | 836 | a novel-writing skill with nine agents |
README in short
The repository's front page, in Chinese, opens with branch information: master holds version 6 for Claude Code, while v8 carries a workspace on DeepSeek Harness. Then come sponsor blocks, an explanation of why the plugin exists, a table of eight commands, a data flow diagram and marketplace installation. After that are the setup for vector search, the chapter writing chain, a final report in three blocks, 37 genres, a list of CLI subcommands, document links, contribution rules, version history and the GPL v3 license. The repository has tests, issue templates and architecture documents.