What makes Web Novel Writing Assistant notable?

1K downloads. Trust evidence available

How should Web Novel Writing Assistant be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Web Novel Writing Assistant

Assists with planning, outlining, writing, pacing, style consistency, conflict detection, multi-plot management, foreshadowing, and reader feedback for web n... Skill: Web Novel Writing Assistant Owner: openlark Summary: Assists with planning, outlining, writing, pacing, style consistency, conflict detection, multi-plot management, foreshadowing, and reader feedback for web n... Tags: latest:1.0.0 Version history: v1.0.0 | 2026-05-28T01:38:05.326Z | auto Initial release of Web Novel Writing Assistant. - Guides users through structured workflows for novel planning, outlining,

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.0k

Updated

Oct 11, 2026

Version

1.0.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.0release · observed May 28, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s1727wv2g20pc729snzcm4nf8183hy72:web-novel-writing-assistant

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-openlark-web-novel-writing-assistant/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

28,919 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
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

_meta.json

{
  "ownerId": "kn75qrtb885pznwsjwsh18dvf1813bv0",
  "slug": "web-novel-writing-assistant",
  "version": "1.0.0",
  "publishedAt": 1779932285326
}

references/chapter.md

# 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

references/conflict-check.md

# 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 silentl

references/feedback.md

# 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 s

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.