agentCLAWHUBUnverified
epic-novel-writer
史诗级长篇网络小说创作skill，包含13阶段写作流程、人物设定、分卷规划、子Agent并行撰写、全文校验、存档管理等完整工作流。覆盖中篇（10-25万字）到超长篇（60-150万字），实测 420,000 字 / 300 章 / 10 卷。支持全局连续编号、只读存档、人物画像 JSON、HTML 导引页生成。 Skill: epic-novel-writer Owner: sunshinejnjn Summary: 史诗级长篇网络小说创作skill，包含13阶段写作流程、人物设定、分卷规划、子Agent并行撰写、全文校验、存档管理等完整工作流。覆盖中篇（10-25万字）到超长篇（60-150万字），实测 420,000 字 / 300 章 / 10 卷。支持全局连续编号、只读存档、人物画像 JSON、HTML 导引页生成。 Tags: creative-writing:1.1.0, latest:1.2.1, longform:1.1.0, novel:1.1.0, storytelling:1.1.0, writer:1.1.0 Version history: v1.2.1 | 2026-09-20T11:30:36.329Z | user v1.2.1: ClawHub security audit remediation. (
OpenClaw
Rank
62
Safety
84
Downloads
1.1k
Updated
Oct 11, 2026
Version
1.2.1
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 1.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
- 1.1K downloadsadoption · observed Oct 11, 2026
- Latest release
- 1.2.1release · observed Sep 20, 2026
- Handshake status
- UNKNOWNsecurity
Install and run
Setup complexity: low.
clawhub skill install s17ehnmpwm46zw2010e8g6j2z583gzv3:epic-novel-writer- 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-sunshinejnjn-epic-novel-writer/snapshot"
Documentation
CLAWHUB
138,160 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
---
name: epic-novel-writer
version: 1.2.1
license: BSD-3-Clause
description: 史诗级长篇网络小说创作skill，包含13阶段写作流程、人物设定、分卷规划、子Agent并行撰写、全文校验、存档管理等完整工作流。覆盖中篇（10-25万字）到超长篇（60-150万字），实测 420,000 字 / 300 章 / 10 卷。支持全局连续编号、只读存档、人物画像 JSON、HTML 导引页生成。
description_zh: "史诗级长篇写作：13 阶段工作流（构思→人物→分卷→章级蓝本→前三章定调→分卷并行撰写→整卷/全文校验→只读存档），全局连续章节编号，人物画像 JSON + HTML 导引页，实测 42 万字 / 300 章 / 10 卷。"
description_en: "Novel writing full workflow — from world-building and character design to chapter planning, manuscript writing, version archiving, and HTML guide generation. Covers medium (100-250k words) to super-long (600k-1.5m words), proven with 420k words / 300 chapters / 10 volumes. Supports global continuous numbering, read-only archives, character JSON, and HTML guides."
homepage: https://clawhub.ai/sunshinejnjn/epic-novel-writer
metadata:
openclaw:
emoji: "🖊️"
compatibility: Pure Markdown workflow, no external dependencies. Requires OpenClaw file I/O and shell execution capabilities.
allowed-tools: Read, Write, Edit, Exec
---
# epic-novel-writer — 史诗级长篇写作 Skill
> **语言说明**：本 skill 的流程文档以中文编写（面向中文网文创作场景，目录与术语为中文）；产出内容（正文、大纲、报告）的语言跟随用户项目语言，不限于中文。英文文档见 `README.md`。
## 适用篇幅
| 篇幅 | 章节数 | 字数范围 |
|------|--------|---------|
| 中篇 | 30-80 章 | 10-25 万字 |
| 长篇 | 80-200 章 | 25-60 万字 |
| 超长篇 | 200-500 章 | 60-150 万字 |
> 实测标杆：420,000 字 / 300 章 / 10 卷
## 核心规则
### 所有编辑必须在 `在编辑稿/` 目录上完成
- 修改 → 操作 `在编辑稿/` 的文件
- 不要修改该目录外的文件
### 存档版本（v1/v2/v3...）是只读的
- 用于对比/核对/历史回溯
- 如需对比先读存档参考，然后修改 `在编辑稿/`
### 存档条件
仅在用户**明确发出存档指令**时执行（"存成 v1"、"终稿了"、"存档"等）；不得把一般性讨论当作存档意图，拿不准先向用户确认。按顺序递增。
### 安全规则
- 小说标题**不得直接拼入 shell 命令**（命令注入风险）：先按 `references/archive-template.md` 的白名单净化，路径展开一律加引号
- 存档/反向合并前必须先向用户确认；反向合并会覆盖 `在编辑稿/`，建议先备份
## 写作流程（13 阶段）
1. **构思沟通** → 故事类型、主题、篇幅、视角 → `01-story-premise.md`
2. **人物设定** → 主角团/配角/关系/时间线 → `references/characters/`
3. **核对修订人物** → 2 遍（年龄/关系/出场顺序/时间线）
4. **分卷规划** → 每卷标题/章节范围/核心冲突 → `03-outline/00-master-outline.md`
5. **卷级大纲** → 章节列表/节奏/伏笔/人物变化 → `03-outline/vol-{N}-outline.md`
6. **章级蓝本** → 场景/人物/情节/伏笔 → `03-outline/vol-{N}/chapter-{XX}-blueprint.md`
7. **撰写前三章** → 2 遍校验 + 润色，用户确认定调
8. **分卷并行撰写** → Sub-Agent 并行，卷内串行
9. **整卷校验** → 通读全卷 + 蓝本核对 → `06-validation/vol-{N}-validation-report.md`
10. **重复 4-9** 依次完成各卷
11. **全卷并行修订** → Sub-Agent 并行，2 遍
12. **全文校验** → 3 遍（全局一致性/连贯性/文笔终检）
13. **存档 v0**（须先经用户明确确认，非自动步骤）→ 按 `references/archive-template.md` 执行（含标题净化、路径加引号、风险确认规则）
**命名规则：** 文件名 = 章编号 = 全局连续三位数。`chapter-001.md`（第 1 章），`chapter-031.md`（卷 2 第 1 章）。
## 存档流程
存档时按 `references/archive-template.md` 执行 8 步：
- 生成人物画像 `char_data.json`（主要角色 + 次要角色）
- 生成 HTML 导引页（暗色主题，响应式，章节全局连续编号）
- 每个存档版本独立只读目录
## 子文件
| 文件 | 内容 |
|------|------|
| `references/project-structure.md` | 项目目录结构定义 + 核心规则 |
| `references/lifecycle.md` | 13 阶段完整流程详情（每阶段产出文件） |
| `references/name-rules.md` | 命名规则（全局连续编号、各文件命名表） |
| `references/archive-template.md` | 存档流程模板（8 步 + 命令示例 + 检查清单） |
| `references/world-setting-template.md` | 世界观设定模板 |
| `references/character-card-template.md` | 人物卡模板 |
| `references/chapterREADME.md
# epic-novel-writer — Epic Novel Writing Full Workflow > An AI-driven creative writing SKILL for long-form serialized novels, covering the entire lifecycle from world-building and character design to chapter planning, writing, version archiving, and HTML guide generation. **Adapted Length: Medium (100-250k words) → Long (250-600k words) → Super Long (600k-1.5m words)** > 💡 **Proven Benchmark**: Used to generate **420,000 words** (300 chapters, 10 volumes), validating global chapter numbering, anti-collapse settings system, and HTML guide generation for super-long-form novels. --- ## 🚀 Why This SKILL? The hardest part of writing a novel isn't "starting" — it's **surviving 300 chapters without things falling apart**. This SKILL solves the most painful problems of long-form writing: ### 1. File Names = Chapter Numbers, Never Get Lost ``` chapter-001.md → Chapter 1 chapter-150.md → Chapter 150 (regardless of which volume) chapter-300.md → Chapter 300 ``` **Restarting from 1 in every volume** is every long-form writer's nightmare. We use **global continuous numbering** — file name IS chapter number, open the folder and you know where you are. > **文件编号 = 章编号**：`chapter-001.md` 就是第 1 章，`chapter-300.md` 就是第 300 章。不管在哪一卷，文件名直接告诉你章节号。打开文件夹就知道写到哪了。 ### 2. One-Click Professional Archive From `references/archive-template.md`, an 8-step flow auto-generates: - ✅ **Full-text merged version** (md + txt dual format) - ✅ **Character profile JSON** (char_data.json with name, role, growth arc, first appearance) - ✅ **HTML guide page** (dark theme, responsive layout, character card grid, continuous chapter links) - ✅ **Plain text table of contents** (chapter numbers + hyperlinks) > **一键专业存档**：8 步流程自动生成全文合并版（md+txt）、人物画像 JSON、HTML 导引页（暗色主题 + 人物卡网格 + 连续章节链接）、纯文本目录。 ### 3. Anti-Collapse Settings System - **World-building template** (`world-setting-template.md`) — geography, history, power system, core conflicts - **Character card template** (`character-card-template.md`) — personality, background, ability growth arcs, appearance tracking - **Chapter blueprint template** (`chapter-blueprint-template.md`) — scene settings, plot outlines, foreshadowing/clue tracking, skill usage records > **防崩设定体系**：三个模板分别覆盖世界观、角色卡、章纲。章纲模板追踪每章伏笔、线索、技能调用，确保剧情不偏离。 ### 4. Read-Only Archives, Free Editing All editing happens in `在编辑稿/` (Work-in-Progress), archive versions (v1/v2/v3…) are **read-only** — compare and trace back anytime; **reverse-merge (overwrites working files) requires explicit user confirmation and a backup first**. > **只读存档**：所有编辑在 `在编辑稿/` 完成，存档版本（v1/v2/v3…）只读，可随时对比、回溯；反向合并会覆盖编辑稿，需用户明确确认并先备份。 --- ## 📋 Contents | File | Purpose | |------|---------| | `SKILL.md` | Core rules, workflow, naming conventions, archive process guide | | `references/project-structure.md` | Project directory structure + core rules | | `references/lifecycle.md` | 13-phase full workflow details (per-phase output files) | | `references/name-rules.md` | Naming rules (global continuous nu
_meta.json
{
"ownerId": "kn7dn131pvgfaveyzzzcrc5xf182yb84",
"slug": "epic-novel-writer",
"version": "1.2.1",
"publishedAt": 1789903836329
}references/archive-template.md
# 版本存档模板
> 本模板定义了版本存档的标准流程与输出结构。存档时参照此模板执行，生成新的 `[小说标题]_vN/` 目录。
---
## 存档触发条件
仅在用户**明确发出存档指令**时执行存档：
- 用户消息中明确包含"存档"、"归档"、"存成 vN"等**指令性表述**时才执行
- **不得**把一般性讨论（如"这章写得不错""差不多可以了吧"）理解为存档意图；拿不准就先问用户"要存档吗？"
- 按创建顺序递增命名：`[小说标题]_v1/`、`[小说标题]_v2/`…
## ⚠️ 操作风险与安全规则
存档流程涉及**目录创建、整树复制、文件格式转换**等批量文件操作。执行前必须：
1. **先向用户确认**本次存档的范围（目标目录名、章节范围），确认后再执行
2. **标题净化（防命令注入）**：用户提供的小说标题**不得直接拼入 shell 命令**——标题中的 shell 元字符（`;`、`|`、`$(`、`>` 等）会被解释为命令。必须先按白名单过滤再引用：
```bash
# $title 为用户提供的小说标题
# 白名单：字母、数字、汉字、空格、_、-、.（UTF-8 locale 下 tr 的 [:alnum:] 包含汉字）
safe_title=$(printf '%s' "$title" | tr -cd '[:alnum:] _.-')
if [ -z "$safe_title" ]; then
echo "Error: 标题净化后为空，请改用不含特殊字符的标题" >&2
exit 1
fi
```
3. **所有路径展开一律加双引号**（`"$safe_title"`、`"$output_file"`），禁止裸展开
4. 写入前校验目标路径确实位于存档目录内（防止 `..`、符号链接逃逸）
5. 能用文件读写工具直接完成的步骤（复制、合并），**优先用文件工具而非拼 shell 命令**
---
## 命名规则（文件编号 = 章编号）
**所有章节文件名使用全局连续三位数编号，不随卷重置：**
| 卷 | 章节范围 | 文件名 |
|----|---------|--------|
| 卷 1 | 第 1-30 章 | `chapter-001.md` ~ `chapter-030.md` |
| 卷 2 | 第 31-60 章 | `chapter-031.md` ~ `chapter-060.md` |
| 卷 3 | 第 61-100 章 | `chapter-061.md` ~ `chapter-100.md` |
| … | … | … |
| 卷 N | 最后一卷 | `chapter-XXX.md` |
**关键规则：**
- ❌ 禁止每卷内从第 1 章重新开始编号（不要出现卷 1 有 1-30 章、卷 2 也有 1-30 章的情况）
- ✅ 文件名直接反映全局章号：`chapter-031.md` = 第 31 章，`chapter-271.md` = 第 271 章
- ✅ 三位数补零：`chapter-001.md`、`chapter-300.md`
---
## 存档目录结构
```
[小说标题]_vN/
├── 01-story-premise.md # 故事设定（复制）
├── 02-world-setting.md # 世界观设定（复制）
├── 03-chapters-written.md # 章节完成状态（复制，反映存档时进度）
├── 03-outline/ # 大纲目录（复制）
│ ├── 00-master-outline.md
│ ├── vol-1-outline.md
│ └── ……
├── 04-chapters/ # 正文文件（txt，按卷分目录）
│ ├── vol-1/
│ │ ├── chapter-001.txt
│ │ ├── chapter-002.txt
│ │ └── ……
│ ├── vol-2/
│ │ ├── chapter-031.txt
│ │ └── ……
│ └── ……
├── 05-reports/ # 过程报告（复制）
├── references/ # 参考文件（复制）
│ ├── ai-ledger/
│ ├── character-relationships.md
│ ├── characters/
│ └── skill-database.md
├── media/ # 图片（复制）
│ └── comfyui/images/
│ └── ……
├── [小说标题]_全文.md # 全文合并版（md）
├── [小说标题]_全文.txt # 全文合并版（纯文本）
├── [小说标题]_目录.txt # 纯文本目录导航
├── [小说标题]_导引.html # ★ HTML 导引文件（核心导航页）
└── char_data.json # 人物数据（JSON，供导引页使用）
```
---
## 执行步骤
### 步骤 1：创建存档目录
```bash
N=下一个序号（从现有最大序号 +1）
# $title 必须先按上方安全规则净化为 $safe_title
mkdir -p "${safe_title}_v${N}/"
```
### 步骤 2：复制只读文件
将 `在编辑稿/` 下的非正文文件原样复制到存档目录：
```bash
cd "${safe_title}_v${N}/"
# 复制根文件
cp ../在编辑稿/01-story-premise.md ./
cp ../在编辑稿/02-world-setting.md ./
cp ../在编辑稿/03-chapters-written.md ./
# 复制大纲目录
cp -r ../在编辑稿/03-outline/ ./
# 复制参考文件
cp -r ../在编辑稿/references/ ./
cp -r ../在编辑稿/media/ ./
# 复制报告
cp -r ../在编辑稿/05-reports/ ./
```
### 步骤 3：复制正文为 txt
`在编辑稿/04-chapters/` 下所有章节已使用全局连续三位数编号，直接转为 txt 复制：
```bash
mkdir -p chapters
for vol_dir in ../在编辑稿/04-chapters/vol-*; do
vol_num=$(basename "$vol_dir")
mkdreferences/chapter-blueprint-template.md
# 章纲模板
> 复制到 [小说项目目录]/03-outline/vol-{N}/chapter-{XX}-blueprint.md
```markdown
# 第 [X] 章：[章名]
## 基本信息
- **位置**: 第 [X] 章（卷 [N] 第 [M] 章）
- **字数目标**: ~1500 字
- **视角**: [主角/其他角色]
## 场景设定
- **时间**:
- **地点**:
- **天气/环境**:
## 出场人物
- [角色名]：状态 + 在本章的作用
## 情节大纲
1. **开场**（~10%）：[快速交代时间/地点/人物状态]
2. **发展**（~40%）：[核心冲突逐步展开]
3. **高潮**（~30%）：[冲突爆发/关键转折]
4. **收尾**（~20%）：[情绪沉淀 + 下章钩子]
## 关键事件
- [事件 1]
- [事件 2]
## 伏笔/线索
- [埋下的伏笔 → 预计在第 X 章回收]
## 技能/设定调用
- [本章节需要展示/用到的设定]
## 注意事项
- [遵守的设定限制]
- [不能做的事情]
```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.
MCPOPENCLAW
Github ReposUpdated 7mo agoRank 70
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
OPENCLAW
Machine-readable data
The same record, as JSON, for agents and crawlers.
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/sunshinejnjn/skills/epic-novel-writer",
"sourceUrl": "https://clawhub.ai/sunshinejnjn/skills/epic-novel-writer",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T06:29:28.766Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-sunshinejnjn-epic-novel-writer/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-sunshinejnjn-epic-novel-writer/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-11T06:29:28.766Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "1.1K downloads",
"href": "https://clawhub.ai/sunshinejnjn/epic-novel-writer",
"sourceUrl": "https://clawhub.ai/sunshinejnjn/epic-novel-writer",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T06:29:28.766Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "1.2.1",
"href": "https://clawhub.ai/sunshinejnjn/epic-novel-writer",
"sourceUrl": "https://clawhub.ai/sunshinejnjn/epic-novel-writer",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-09-20T11:30:36.329Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-sunshinejnjn-epic-novel-writer/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-sunshinejnjn-epic-novel-writer/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 1.2.1",
"description": "v1.2.1: ClawHub security audit remediation. (1) Fixed command-injection in archive-template.md: user-provided novel title is now sanitized via allowlist (tr -cd '[:alnum:] _.-') and all path expansions are quoted (previously unquoted [小说标题] interpolation could be shell-injected). (2) Added Operation Risk & Safety Rules section: confirm scope before archive, verify destination stays inside archive root, prefer file tools over shell. (3) Tightened archive triggers to explicit user commands only; vague phrasing no longer counts. (4) Stage 13 'archive v0' now requires explicit user confirmation (resolves contradiction with read-only-archive policy). (5) Reverse-merge now requires confirmation + backup warning (resolves read-only vs overwrite contradiction). (6) Added language note: docs are Chinese (Chinese web-novel domain), output language follows the project; English README available.",
"href": "https://clawhub.ai/sunshinejnjn/epic-novel-writer",
"sourceUrl": "https://clawhub.ai/sunshinejnjn/epic-novel-writer",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-09-20T11:30:36.329Z",
"isPublic": true
}
]
}Record generated Oct 11, 2026.