novelops-skill

Coordinate long-form fiction writing with stateful workflows and JSON outputs.

17|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/qiyan233/novelops-skill --skill novelops-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: novelops-skill
Source: https://github.com/qiyan233/novelops-skill/tree/main
Command: npx skills add https://github.com/qiyan233/novelops-skill --skill novelops-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Coordinating long-form fiction writing is hard when world state, chapter continuity, and multi-chapter planning drift across drafts. NovelOps Skill provides a stateful workflow that centralizes truth files, chapter summaries, hooks, and relationships to maintain consistency across many chapters.

Core Features & Use Cases

  • Load and manage durable truth files (story_bible.md, current_state.md, chapter_summaries.md, hooks, etc.) to enforce world rules and continuity.
  • Build next-chapter context, draft constrained chapters, audit for continuity, and extract state updates in a single pipeline.
  • Coordinate multi-chapter workflows: state updates, revisions, and audits with JSON outputs for automation and auditing.

Quick Start

Initialize a new project with python scripts/novelops_cli.py init /path/to/project 'Book Title' to scaffold the workflow and begin long-form writing.

Frequently Asked Questions about novelops-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain world state and continuity across multiple long-form fiction chapters?

A stateful workflow coordinates long-form fiction by storing durable truth files such as story bibles and chapter summaries, ensuring world rules and continuity are preserved across many chapters.

How do I automate chapter drafting and continuity audits for a novel?

Automate chapter drafting and continuity audits using a unified CLI pipeline that builds next-chapter context, drafts constrained chapters, and extracts state updates with deterministic JSON outputs for auditing.

What is the best way to plan multi-chapter fiction workflows without losing plot consistency?

Planning multi-chapter fiction workflows without plot drift requires a structured truth-file architecture that tracks current state, chapter summaries, and hooks to enforce consistency across revisions.

Do I need a specific environment to run stateful fiction writing workflows with deterministic JSON outputs?

Running stateful fiction writing workflows with deterministic JSON outputs requires a Python environment to execute CLI scripts that initialize projects, scaffold workflows, and orchestrate OpenClaw-based storytelling automation.

Can I use truth files and state updates for novel revisions in an automated pipeline?

Truth files and state updates support novel revisions in automated pipelines by providing structured contracts and chapter summaries that enable continuity auditing and multi-chapter workflow orchestration with deterministic outputs.