Skill: openlark/web-novel-writing-assistant (version 1.0.0)

--- name: web-novel-writing-assistant description: Web novel writing assistant, solving core pain points: context loss, inconsistent style, setting conflicts, pacing issues, multi-plot confusion, unstable quality, and inability to internalize reader feedback. --- # Web Novel Writing Assistant ## Use Cases Use for new book planning, outline design, chapter writing, foreshadowing management, conflict detection, reader feedback analysis, and batch creation quality control. ## Creation Workflow ``` New book planning → Outline design → Chapter writing → Quality review → Publish & iterate ``` Each step uses the corresponding reference template (loaded on demand): | Step | Reference | Core Deliverable | |------|-----------|-----------------| | 1. New Book Planning | [worldbuilding](references/worldbuilding.md) | Setting profile (world/protagonist/supporting cast/conflict) | | 2. Outline Design | [outline](references/outline.md) | Volume→Part→Chapter three-level outline | | 3. Chapter Writing | [chapter](references/chapter.md) | Writing brief + review checklist | | 4. Style Consistency | Style anchors below | Style reference card (~100 chars) | | 5. Multi-plot Management | [plot-threads](references/plot-threads.md) | Status board (🟢🟡🔴) | | 6. Foreshadowing Management | Foreshadowing registry | ID + planted + planned resolution + status | | 7. Conflict Detection | [conflict-check](references/conflict-check.md) | Setting/character/logic/numerical 4D check | | 8. Pacing Diagnosis | [pacing](references/pacing.md) | H/W/P/T pacing curve | | 9. Feedback Loop | [feedback](references/feedback.md) | SABCD grading + decision log | ## Core Operations ### Pre-Write Checklist (5 items) Context review → Foreshadowing status → Character status → Timeline → Pacing position ### Chapter Rhythm Template (6 beats) Hook → Setup → Development → Twist → Climax → Cliffhanger ### Style Anchors Language style, description density, emotional tone, IP signature → check against each chapter ### Foreshadowing Iron Rule Log every planted thread, check off every resolved one. Never rely on memory. ``` | ID | Planted Ch | Content | Planned Resolution Ch | Status | ``` ### Pacing Symbols H=High point W=Twist P=Setup T=Transition. Draw curve every 10-20 chapters for diagnosis. ### Feedback Grading S=Data (retention rate) A=5+ users same feedback B=Specific critique C=Emotional vent D=Contradicts core setting (reject) ### Batch Creation Rhythm Write 5 days (pre-write checks) → Saturday quality review → Sunday planning → Month-end volume review ## Principles - **Settings are law**: Once established, don't change casually; modifications require traceable updates - **Quality from process**: Not from inspiration — from pre-write checks + post-write reviews - **Data doesn't lie**: Retention rate > intuition > individual comments - **Stability over novelty**: Consistency > literary innovation

path: references/chapter.md
content: # Chapter Writing Workflow

## Pre-Write Checklist

Complete in order, produce the **chapter writing brief**:

### 1. Context Review

```
- Previous chapter's ending scene:
- Previous chapter's unresolved conflict/suspense:
- Previous chapter's reader emotional landing (tense/relaxed/anticipating/sad):
- This chapter's starting scene:
```

### 2. Foreshadowing Status

```
【Planned operations for this chapter】
- Foreshadowing to resolve (ID + content):
- New foreshadowing to plant (content + planned resolution chapter):
- Foreshadowing to advance but not resolve (ID + degree of advancement):
```

### 3. Character Status

```
【Characters appearing in this chapter】
- Character A: Current location / current emotion / this chapter's goal / this chapter's function
- Character B: ...
【Characters not appearing but need to remember their status】
- Character C: Currently in XX state at XX location
```

### 4. Pacing Position

```
【Chapter type】 (Climax / Transition / Setup / Twist)
【Position within volume】 (First third / Middle / Closing)
【Emotional design】 (Opening emotion → Process emotion → Ending emotion)
【Information density】 (High / Medium / Low) — how much info reader needs to digest
```

## During Writing

- **First 300 words decide life or death**: must have conflict/suspense/emotion (at least one)
- **Every 2000 words a mini-rhythm**: info release → minor conflict → minor resolution
- **Dialogue must have "subtext"**: what character says ≠ everything they're thinking
- **Scene transitions need "hooks"**: don't let readers put it down when switching scenes
- **Battle/climax scenes**: faster rhythm, shorter sentences

## Post-Write Review

### Basic Checks

- [ ] Did this chapter complete the rhythm beat structure (Hook→Setup→Development→Twist→Climax→Cliffhanger)?
- [ ] Word count within expected range (deviation <20%)?
- [ ] Chapter-ending cliffhanger effective (will readers want to click next)?

### Consistency Checks

- [ ] Character dialogue and behavior match their profile?
- [ ] Any content conflicting with established settings?
- [ ] Timeline coherent (reasonable gap from previous chapter)?
- [ ] Character abilities/levels consistent with setting?

### Foreshadowing Checks

- [ ] New foreshadowing planted this chapter logged?
- [ ] Planned resolutions correctly resolved? Resolution method natural?
- [ ] Any "forgotten" foreshadowing needing advancement?

### Style Checks

- [ ] Dialogue style matches characters?
- [ ] Narrative rhythm matches chapter type? (Climax fast, Setup slow)
- [ ] Emotional tone matches current volume's setting?

## Common Issues & Fixes

| Issue | Diagnosis | Fix |
|-------|-----------|-----|
| Chapter too flat | No hook/twist/climax | Rewrite opening hook, add at least one minor reversal |
| Padding | Info density too low, plot not advancing | Cut excess description/psychology, add event progression |
| Setting conflict | Character ability or rules inconsistent | Check setting profile, fix chapter or update setting |
| Character drift | Personality inconsistent with earlier | Check character profile, rewrite relevant dialogue/behavior |
| Homogenized dialogue | All characters talk the same | Design 1-2 linguistic quirks per character |
| Broken rhythm | Abrupt scene transitions | Add transition sentences / emotional bridges |
| Weak hook | No suspense or anticipation at chapter end | Leave an unanswered question or an impending conflict |


path: references/conflict-check.md
content: # Conflict Detection Matrix

## I. Setting Conflict

Run after writing each chapter:

### Ability/Level Consistency

```
- Character ability matches their current setting level?
  □ Protagonist's overlevel fights have reasonable explanation?
  □ Supporting character abilities consistent with their level?
- Cultivation/advancement rules consistent front to back?
  □ Same-level characters' power gaps reasonable?
```

### World Rule Consistency

```
- World rules "forgotten" or "violated"?
  □ Power system limitations broken (without explanation)?
  □ Special rules consistent across chapters?
  □ If rules are broken, is there foreshadowing and a cost?
```

### Timeline Consistency

```
- Time passage reasonable?
  □ Event intervals proportional to narrative length?
  □ Time contradictions between scenes?
  □ Character ages / seasons / holidays all check out?
```

## II. Character Conflict

### Personality Consistency

```
- Character decisions match their personality profile?
  □ Decisive characters becoming suddenly indecisive?
  □ Rational characters unreasonably dumbed down?
  □ Character emotional reactions match their personality?
```

### Relationship Consistency

```
- Character relationships suddenly changing (no transition)?
  □ Hostile→friendly: reasonable reversal process?
  □ Close→distant: foreshadowing event?
  □ New character interactions match both personalities?
```

### Motivation Consistency

```
- Character actions have clear motivation?
  □ Supporting characters' actions exist only to advance plot?
  □ Character goals contradictory front to back?
```

## III. Plot Logic

### Causal Chain

```
- "Because A, therefore B" logic chain complete?
  □ Any "somehow this happened" moments?
  □ Key reversals have sufficient foreshadowing?
  □ Too many coincidences? (≤1 coincidence per chapter is reasonable)
```

### Information Acquisition

```
- Character info-gathering methods reasonable?
  □ "Overheard the key conversation by coincidence"?
  □ Characters knowing information they "shouldn't know"?
  □ Info reveal rhythm reasonable (too fast or too slow)?
```

### Dumbing-Down Detection

```
- Any of these dumbing-down patterns?
  □ Protagonist not making the simplest reasonable choice at critical moments
  □ Antagonist not killing protagonist when they could (no reasonable explanation)
  □ Supporting cast collectively dumbed down to highlight protagonist
  □ Crisis resolved by "just so happening that..." (deus ex machina)
```

## IV. Numerical Consistency

```
- Cultivation levels: count/name/features recorded and consistent?
- Time data: spans, ages, event intervals self-consistent?
- Money/resources: economic system reasonable?
- Distance/scale: geography, army sizes front-to-back consistent?
```

## V. Conflict Resolution Principles

**When conflicts are found:**

1. **Published chapter settings are "iron law"** → fix unpublished current chapter to align
2. **If published chapter itself has a bug** → post correction notice or silently fix (per platform rules)
3. **If "setting upgrade" not contradiction** → ensure reasonable transition explanation
4. **Log all conflicts and resolutions** → prevent recurrence

## VI. Quick-Reference Mnemonic

```
Abilities check levels, time checks the line
Characters check personality, plot checks causality
Coincidences max three, dumbing-down is the worst crime
Numbers keep clear record, foreshadowing must close the loop
```


path: references/feedback.md
content: # Reader Feedback Analysis & Creative Decision Loop

## I. Feedback Collection Channels

| Channel | Content Collected | Frequency |
|---------|-------------------|-----------|
| Chapter comments / inline comments | Instant per-chapter reactions | Daily |
| Comment section | Overall evaluation, plot discussion | Daily |
| Reader community / group | Deep discussion, character preferences | Weekly |
| Backend data | Retention rate, stickiness, reading duration | Weekly |
| Reviews / ratings | Structured evaluation | Monthly |

## II. Feedback Classification & Weighting

### By Credibility

```
S-level — Backend data (retention rate, stickiness): objective, indisputable
A-level — High-frequency repeated feedback (≥5 people mention the same issue): likely real problem
B-level — Specific criticism with logical basis: worth serious consideration
C-level — Emotional venting without specifics: low reference value
D-level — Demands contradicting core setting: reject on principle
```

### By Impact Scope

```
Systemic issues — Affect majority of readers → priority handling
Local issues — Affect some readers/single chapter → handle as appropriate
Personal preference — Individual reader subjective feeling → reference only
```

## III. Feedback Analysis Template

```
【Analysis time】 After Ch. X publication
【Data summary】
- 24h retention rate: XX% (vs. previous chapter: ±X%)
- Chapter comments: XX (positive/neutral/negative = X/X/X)
- Core discussion topics (TOP3):
  1. XXX
  2. XXX
  3. XXX

【Key feedback】
- Positive (why readers like):
- Negative (what readers are unhappy about):

【Problem diagnosis】
- Quality issue? (writing/pacing/logic)
- Content direction issue? (plot direction/character fate doesn't match expectations)
- Update issue? (breaks/less frequent updates/slow pace)

【Creative decision】
Adopt / Partially adopt / Reject
Reasoning:
Action plan:
```

## IV. Decision Principles

### Should Listen To

- Retention rate dropping → must find cause and adjust
- ≥5 people mention the same specific problem → likely real issue
- "Don't understand" "can't follow" → information delivery problem
- "Too padded" "too slow" → pacing needs adjustment

### Should NOT Blindly Follow

- Demands to change core setting (shakes the book's foundation)
- Demands "write more of character X" when X shouldn't appear yet in plot
- "Hurry up and get together / defeat the villain" → pacing plan shouldn't be disrupted
- Extreme emotional attacks → don't respond, don't internalize

### Flexible Handling

- Dialogue style / description density adjustment (doesn't affect core setting)
- Minor adjustment to supporting character screen time (without affecting main plot)
- Update frequency fine-tuning (within capability)

## V. Decision Log & Tracking

```
═══════════════════════════════════════
【Creative Decision Log】

Decision #01  |  Date: XXXX-XX-XX
Source: Ch. X comments (retention dropped from 75% to 68%)
Issue: Readers report "too many daily chapters, main plot advancing too slowly"
Decision: Compress daily plotline over next 5 chapters, accelerate main plot
Execution:
  - Ch. X: Cut daily dialogue XXX
  - Ch. Y: Compress 3-chapter setup into 2 chapters
  - Ch. Z: Bring forward main plot conflict introduction
Verification: After adjustment, retention rate recovered to 73%
═══════════════════════════════════════
```

## VI. Feedback Loop Check

After each adjustment, observe at least 5 chapters, confirm:

- [ ] Did data improve (retention/stickiness)?
- [ ] Did negative feedback decrease?
- [ ] Did adjustment introduce new problems?
- [ ] Does it deviate from outline's main line?

If adjustment ineffective → possibly misdiagnosed the problem, re-analyze.

## VII. Mindset Management

- **Not all criticism needs response**: web novel reader base is large, can never satisfy everyone
- **Data > Intuition > Individual comments**: one person's problem may just be personal preference
- **Writing well > Writing fast**: rushing to win back readers often backfires
- **Logging beats remembering**: decision log is the most valuable long-term creative asset


path: references/outline.md
content: # Three-Level Outline Template

## I. Complete Book Outline (Volume Level)

```
【Book Basic Info】
- Title, genre, estimated total word count
- Core selling point (one sentence: why readers should read this)
- Target reader profile

【Volume Structure】
Volume 1: "Volume Title" (~XX words, XX chapters)
- Volume theme: What this volume is about
- Opening hook: What grabs readers in the first 3 chapters
- Core conflict: Main tension of this volume
- Key events (≥5):
  1. XXX (approx chapter range)
  2. XXX
  ...
- Volume ending: What is achieved, what suspense is left

Volume 2: "Volume Title" ...
```

## II. Part Outline (Within Each Volume)

Break each volume into 3-5 parts, each with setup-development-turn-resolution:

```
【Part X】 (Ch. X - Ch. Y)
- Part theme:
- Setup (opening): How this story segment begins
- Development (progression): How the story advances
- Turn (twist): Key reversal or revelation
- Resolution (closure): How this part wraps up, setting up next
- Information release: What readers need to learn in this part
- Foreshadowing: What to plant, what to resolve
```

## III. Chapter Outline (Per-Chapter Rhythm Template)

```
【Chapter X: Chapter Title】

Positioning: Climax chapter / Transition chapter / Setup chapter / Twist chapter

Rhythm Beat Design:
1. Hook: What grabs the reader in the first paragraph/scene
2. Setup: Establish this chapter's situation, tell reader what's at stake
3. Development: Plot unfolds, information released
4. Twist: Surprise, conflict, revelation — the chapter's dramatic core
5. Climax: Peak or phased resolution of this chapter's conflict
6. Cliffhanger: Suspense, preview, emotional continuation

Involved plotlines: (Main / Subplot A / Subplot B)
Characters appearing:
New settings/foreshadowing:
Estimated word count:
```

## IV. Outline Flexibility Principles

- **Outline is a map, not railway tracks**: deviation allowed but must return to main line
- **Volume-level outline**: sets direction, not easily changed
- **Part-level outline**: adjustable, but assess impact on subsequent
- **Chapter-level outline**: must do before writing, can adjust during writing
- **Buffer chapters**: reserve 2-3 chapters per volume for insertion or rhythm adjustment

## V. Serialization Rhythm Suggestions

| Words/Day | Type | Strategy |
|-----------|------|----------|
| 4000+ | High-frequency serial | Detailed chapter outlines, backlog ≥30 chapters |
| 2000-4000 | Standard serial | Complete chapter outlines, backlog ≥15 chapters |
| <2000 | Low-frequency serial | Focus on per-chapter quality, outline can be rougher |


path: references/pacing.md
content: # Pacing Diagnosis Tool

## I. Chapter Rhythm Classification

Label each chapter with its rhythm type:

| Type | Symbol | Characteristic | Suggested ratio |
|------|--------|---------------|-----------------|
| Climax | H | Major battle/revelation/reversal, emotional peak | 15-20% |
| Twist | W | Key info revealed, situation reversal | 10-15% |
| Setup | P | Build background, plant foreshadowing | 20-25% |
| Transition | T | Scene change, daily interaction | 40-50% |

## II. Rhythm Curve Drawing

Take the last 20-30 chapters, label each:

```
Chapter: 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
Type:    T  P  P  T  W  T  T  P  T  H  T  T  P  P  T  W  P  T  T  H
```

### Diagnostic Questions

1. **Reader fatigue**: ≥5 consecutive chapters with no H/W? (Too much transition/setup, readers will tire)
2. **Peak fatigue**: ≥3 consecutive H chapters? (Need to give readers breathing room)
3. **Rhythm waves**: H/W distribution even? (Clustered at ends? Hollow in middle?)
4. **Setup payoff**: P chapters followed by H/W? (Setup without payoff = padding)

## III. Information Density Check

Pick a random chapter, check:

```
【Information Density】 (each chapter should give readers at least one "takeaway")
- Plot advancement: □ Yes □ No (if "No," what is this chapter doing?)
- Character growth/revelation: □ Yes □ No
- Foreshadowing advancement/resolution: □ Yes □ No
- Worldbuilding expansion: □ Yes □ No
- Emotional fluctuation: □ Yes □ No

If ALL are No → padding chapter, needs cutting or merging
```

## IV. Volume-Level Rhythm Overview

```
【Volume X Rhythm Overview】 (Ch. XX - YY, XX chapters total)

Peak points:
- Ch. X: XXX (H-level, volume's biggest climax)
- Ch. Y: XXX (H-level, secondary climax)
- Ch. Z: XXX (W-level, key twist)

Valleys/Transitions:
- Ch. A-B: transition segment (X chapters, reasonable range 3-5)

Rhythm Scores:
- Opening engagement: ★★★★☆ (do first 3 chapters have hooks?)
- Mid-section sustainability: ★★★☆☆ (middle dragging?)
- Closing explosiveness: ★★★★★ (ending satisfying?)
```

## V. Reader Fatigue Warning Signals

≥3 of the following signals → likely pacing problem:

- [ ] Retention rate dropping consecutively
- [ ] Comments increasingly mention "padding" "dragging" "boring"
- [ ] Chapter likes/votes decreasing
- [ ] You yourself feel "these recent chapters are kind of flat"
- [ ] Multiple consecutive chapters with no climax scheduled
- [ ] Subplot advancement speed exceeds main plot

## VI. Quick Adjustment Strategies

| Problem | Adjustment |
|---------|-----------|
| Setup too long | Cut redundant description/dialogue, merge 2 chapters into 1 |
| Climax too dense | Insert 1-2 chapters of daily/transition buffer |
| Mid-section slump | Insert an unexpected event / new info / minor conflict |
| Monotonous rhythm | Vary rhythm type — speed up in climax, slow down in setup |


path: references/plot-threads.md
content: # Multi-Plot Management & Status Board

## Plotline Classification

```
【Main Plot】 — Protagonist's core objective line, runs through the entire book
【Major Subplots】 — Secondary lines affecting the main plot (2-4)
【Minor Subplots】 — Character growth / romance / worldbuilding lines (several)
【Hidden Plot】 — Hidden threads, revealed later
```

## Status Board Template

Update after every chapter written. Status: 🟢Active / 🟡Dormant / 🔴Resolved / ⚪Not Started

```
═══════════════════════════════════════
Updated: Chapter X

【Main Plot: XXX】
Current phase: Phase X / Y total
Progressed to: XXX
Next key milestone: XXX (estimated Ch. X)
Associated characters: [list]
Associated foreshadowing: [list IDs]
🟢

【Subplot A: XXX】
Current progress: XXX
Next chapter plan: XXX
Associated characters: [list]
🟡 Dormant until Ch. X
```

## Convergence Planning

When multiple lines need to intersect, plan intersection points:

```
【Convergence Point #1】 (Estimated Ch. X - Y)
Lines converging: Main + Subplot A + Subplot B
Convergence method:
- Location convergence: all characters arrive at same location
- Event convergence: one event simultaneously affects multiple lines
- Information convergence: characters on different lines discover pieces of the same info
Post-convergence direction:
- Merge into one line
- Continue separately but mutually influencing
- One line ends/goes dormant
```

## Priority & Tradeoffs

When "too many lines to write":

1. Main plot has highest priority, cannot go more than 3 chapters without advancing
2. Major subplots sorted by reader interest; low-interest ones can go dormant
3. Dormant lines can't "disappear" — need occasional mentions so readers remember
4. A line not advanced in >50 chapters: consider accelerating resolution or cutting
5. New line must be evaluated: are existing lines already too many?

## Rhythm Distribution Suggestions

Over a 100-chapter cycle:

```
Main plot: 60-70 chapters (maintain core momentum)
Major subplot A: 15-20 chapters (dedicated segments)
Major subplot B: 10-15 chapters
Minor subplots: interspersed, no dedicated chapters
Hidden plot: one clue fragment every 20-30 chapters
```

## Check Questions

Self-check every 30 chapters:
- Which line hasn't advanced in 20+ chapters?
- Which line do readers care about most in comments?
- Has any line "died naturally" (nobody cares)?
- Are intersection points for next phase clear?


path: references/worldbuilding.md
content: # Worldbuilding & Character Setting Template

## I. World Foundation

```
【Era/World Type】
- Era: Ancient / Modern / Future / Alternate
- Type: Xianxia / Fantasy / Urban / Sci-fi / Post-apocalyptic / Game / Historical
- Relation to reality: Parallel world / Historical branch / Pure alternate

【World Rules】
- Power system (cultivation levels / magic classification / tech tier)
- Special rules (what makes this world "different")
- Limitations and costs of the rules

【Geography & Factions】
- Key regions (map overview)
- Faction distribution (nations/sects/organizations, relationship map)
- Resource distribution (what is where, who controls it)
```

## II. Protagonist Profile

```
【Basic Info】
- Name/title, age, appearance (3 memorable traits)
- Personality keywords (≥3): e.g. "reserved, decisive, loyal"
- Personality paradox (adds depth): e.g. "cold exterior, passionate heart"

【Background】
- Origin: family, social class, upbringing environment
- Core trauma/drive: the fundamental force driving the protagonist
- Starting state: situation at the beginning of the story

【Growth Arc】
- Starting state → End state
- Key growth milestones (≥5)
- Cheat/special ability (type, limitations, cost)

【Relationship Network】
- Core relationship characters and relationship evolution directions
```

## III. Supporting Characters

Minimum for each major character:

```
【Name/Role】
【Appearance tag】 (1-2 traits for readers to remember)
【Personality tags】 (2-3 keywords)
【Relationship with protagonist】 and evolution curve
【Narrative function】 (advance plot / create conflict / provide info / emotional support)
【Independent motivation】 (character doesn't exist solely for the protagonist)
```

Character tiers:
- S-tier (throughout the entire book, 3-5 people) → full profile
- A-tier (one volume, 5-10 people) → core profile
- B-tier (one part, functional) → brief notes

## IV. Core Conflict System

```
【Main Conflict】
- Conflict nature: Person vs Person / Person vs Environment / Person vs Self / Person vs Fate
- Opposition: antagonist/hostile faction
- Conflict escalation path: Small → Medium → Large → Ultimate

【Phase Goal Breakdown】
- Volume 1: Achieve XXX
- Volume 2: Achieve XXX
- ...

【Antagonist/Obstacle Design】
- Main antagonist: motivation (must be reasonable), capability, relationship with protagonist
- Phase antagonists: opponents per volume/part
- Non-human obstacles: environment, systems, fate, etc.
```

## V. Setting Consistency Log

```
【Established Iron Laws】 (immutable)
- Rule 1: XXX (established in Ch. X)
- Rule 2: XXX

【Power System】
- Level names, each level's characteristics, advancement conditions
- Protagonist's current level, advancement progress

【Timeline】
- Story start timepoint
- Key event timepoints
```

## Usage Tips

- Complete items I-IV when starting a new book
- Update item V before each volume begins
- Update instantly when introducing new characters/settings
- When conflicts arise, prioritize "iron laws," adjust non-iron-law content


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)