Token导航 LogoToken导航

Agent Skill · 开发

webnovel-serial-pipeline(网络小说串行管道)

webnovel-serial-pipeline 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

webnovel-serial-pipeline 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 1,142。

总安装 38,458周安装 1,571GitHub Stars 公开资料未说明下载 12,442核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.1.4

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:webnovel-serial-pipeline(网络小说串行管道)
来源仓库:https://github.com/jeong-wooseok/webnovel-serial-pipeline
安装命令:
openclaw skills install webnovel-serial-pipeline
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install webnovel-serial-pipeline

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

构建并发布 Quartz 托管的韩国网络小说系列(草稿→封面→webp→剧集 md→lint→发布)。使用 Nano Banana Pro + ffmpeg。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install webnovel-serial-pipeline;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

webnovel-serial-pipeline 怎么安装?

在终端执行 openclaw skills install webnovel-serial-pipeline。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

webnovel-serial-pipeline 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

webnovel-serial-pipeline 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

webnovel-serial-pipeline 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

webnovel-serial-pipeline 用的人多吗?

公开数据是累计安装 38,458 次,近一周安装 1,571 次,下载 12,442 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

webnovel-serial-pipeline 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
webnovel-serial-pipeline

网络小说串行管道 · 本页

38,458—接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
webnovel-serial-pipeline
version
0.1.4
description
Build and publish a Quartz-hosted Korean web-novel serial (draft→cover→webp→episode md→lint→publish). Uses Nano Banana Pro + ffmpeg.

WebNovel Serial Pipeline (Quartz)

⚠️ Security Notice

This skill may trigger antivirus false positives due to:

  • Shell scripts (.sh): Used ONLY for ffmpeg image conversion and dependency checks
  • subprocess calls: Used ONLY to invoke Python linting scripts
  • prepublish_check.py: Security scanner that looks for malicious patterns (ironically flagged by AV)

- Contains regex patterns like curl, wget to DETECT (not execute) malicious code - This is a SECURITY FEATURE, not malware

All code is open source and auditable. No malicious behavior.


This skill documents the end-to-end workflow we used for Quartz-hosted Korean web-novel serials (e.g., Drama/야간조).

Quick Start (copy/paste)

From a terminal:

# 1) Install
clawhub install webnovel-serial-pipeline

# 2) Go to the skill folder
cd skills/webnovel-serial-pipeline

# 3) Set your Quartz root (env var)
export WEBNOVEL_QUARTZ_ROOT="/absolute/path/to/8.quartz"

# 4) Verify deps
bash scripts/check_deps.sh

# 5) After you say “검수 완료”, publish + sync index
bash scripts/publish_review_ok.sh --series "야간조" --episode 2 --slug "불-꺼지면-가지-마세요" --draft-file "/path/to/draft.md"

Goals

  • Episodes are readable (no "writer commentary" tone)
  • Every episode has at least 1 image
  • Images are lightweight for the web: 1K → webp (q 70~80, max 1200px)
  • Publishing is safe: draft in archive → move to Quartz only after review

Design & Requirements (before writing)

This section captures the proposal + requirements analysis process we used (the part *before* the pipeline).

Kickoff 질문(한 번에 던지기, 선택형)

아래 질문을 한 메시지로 던지고, 사용자가 선택/응답하면 그걸로 톤을 고정한다.

  • 장르(선택): 드라마 / 오피스 스릴러 / 블랙코미디 / 로맨스(현실톤)
  • 레퍼런스(선택): (이게 KICK) 사용자가 *이미 아는 드라마 톤*을 고르면, 설명 없이도 문장/연출/감정선이 바로 고정된다.

- 예시: 나의 아저씨 / 미생 / D.P. / 나의 해방일지 / 더 글로리(톤만) / 시그널 / 비밀의 숲 / 나쁜 녀석들 / 괴물 / 마이 네임 - 추천 방식: 메인 1개 + 보조 1개 선택

  • 수위(선택): 12세 / 15세 / 청불
  • 에피소드 길이(선택): 3~5분 분량 / 5~10분 분량(웹소설 체감 길이)
  • 배경(선택): 구도심 / 강남 오피스 / 주거지 / 공공기관
  • 캐릭터(필수): 2~6명 (이름 + 한 줄 성격)

유치함 방지(기본값 8룰)

  • 현실 기반 갈등(일/돈/윤리/관계). 초능력·과장 금지.
  • 밈/유행어/오글 멘트 금지.
  • 설명충 금지: “말로 설명” 대신 “행동/선택”으로 보여주기.
  • 서브텍스트(겉말≠속마음) 1~2번은 반드시 넣기.
  • 선악 이분법 금지: 결함+욕망+두려움 3요소로 캐릭터 설계.
  • 코미디는 ‘사람을 조롱’하지 말고 상황/아이러니로.
  • 과한 효과/폰트/감정 과장 금지(문장 톤도 포함).
  • 엔딩은 해피/불행보다 “후폭풍(대가)”를 남기기.

성숙도(퀄리티) 루브릭 — 자동 체크

  • 오글/밈 대사 0개
  • 설명 대사 비율 20% 이하(대부분 행동/선택)
  • 인물 2명 이상이 서로 다른 목표로 충돌
  • 사건의 결과(대가)가 최소 1개 남음(돈/관계/신뢰/평판)

시즌(10부작) 설계 템플릿

  • EP01: 훅/트리거(사건 씨앗을 “확정”으로 박기)
  • EP02: 첫 사건(한 단계 전진)
  • EP03~04: 구조/연결고리 드러남(우연→패턴)
  • EP05: ‘왜 신고하지 못하는가’ 같은 현실적 제약 공개
  • EP06~07: 선택 강요(관계/돈/윤리의 대가)
  • EP08: 정체/구조의 윤곽(내부자/책임 전가)
  • EP09: 한 번만(돌이킬 수 없는 선택)
  • EP10: 해결보다 “이후”로 마무리(과장 없이)

관계 설계 규칙(절제된 애틋함)

  • “스몰토크로 친해지기” 금지 → 작은 빚 2번으로 관계를 앞으로 당긴다.

- A→B: 사소한 배려 1번(말보다 행동) - B→A: 말 없는 현실 도움 1번(영웅 금지)

  • 호칭은 현실적으로:

- 이름을 알기 전: 최소한(직업/기능 대사 위주) - 이름을 확인한 뒤: “아저씨” 같은 호칭은 피하고 이름(도현 씨)로.


Setup for distribution (paths + optional APIs)

1) Set your Quartz root (deploy folder)

For distribution we do not hardcode machine-specific paths.

Required environment variable:

  • WEBNOVEL_QUARTZ_ROOT = your Quartz vault root (published content folder)

Optional:

  • WEBNOVEL_DRAFT_ROOT = where you keep drafts
  • NANO_BANANA_KEY (only if you generate covers using nano-banana-pro)

Example:

export WEBNOVEL_QUARTZ_ROOT="/absolute/path/to/8.quartz"
export WEBNOVEL_DRAFT_ROOT="/absolute/path/to/drafts"   # optional

2) Dependency check

From inside this skill folder:

bash scripts/check_deps.sh

3) Pre-publish safety check (ClawHub)

Before clawhub publish, run:

python3 scripts/prepublish_check.py

This fails if obvious exfil/download markers are found.

Folder convention

  • Quartz vault root (published):

- $WEBNOVEL_QUARTZ_ROOT (example: /path/to/8.quartz)

  • Example series folder:

- Drama/<series>/index.md (landing + 제작 규칙) - Drama/<series>/<series>-01-....md (published episodes) - Drama/<series>/images/*.webp (covers)

  • Drafts (NOT published):

- $WEBNOVEL_DRAFT_ROOT/<series>_serial_drafts/ (example: /path/to/drafts/yaganjo_serial_drafts/)

Workflow (recommended)

0) Decide the "episode job"

  • EP01: hook/trigger (plant the seed)
  • EP02+: progress (one new event per episode)

1) Create an episode draft

Write the episode in the drafts folder first.

2) Cover image (1K)

Generate cover PNG (1K) using Nano Banana Pro, then convert to WebP.

3) Embed + tags

  • Ensure frontmatter tags include the 6-axis tags:

- domain/topic/format/audience/intent/lang

  • Embed cover early in the episode body using a Quartz wikilink:

- ![[Drama/<series>/images/<cover>.webp]]

4) Lint (style checks)

Before publishing, run a quick linter:

  • ban repetitive patterns: 같아서/것 같아서
  • avoid writer commentary tone: overuse of generalizations
  • keep dialogue natural and short

5) Publish (move to Quartz)

Only after the user says OK.

Recommended publish command (copies draft into Quartz and normalizes filename):

python3 scripts/publish_episode.py \
  --draft-file /path/to/draft.md \
  --quartz-root "$WEBNOVEL_QUARTZ_ROOT" \
  --series-dir "$WEBNOVEL_QUARTZ_ROOT/Drama/<series>" \
  --series "<series>" \
  --episode 2 \
  --slug "불-꺼지면-가지-마세요"

6) Sync index.md episode list (optional, recommended)

Add markers once in Drama/<series>/index.md:

## 에피소드
<!-- episodes:start -->
<!-- episodes:end -->

Then run:

python3 scripts/sync_index.py \
  --index-file "$WEBNOVEL_QUARTZ_ROOT/Drama/<series>/index.md" \
  --series-dir "$WEBNOVEL_QUARTZ_ROOT/Drama/<series>" \
  --series "<series>"

One-shot publish workflow (ONLY after chat confirmation: “검수 완료”)

This is the recommended human-safe workflow: wait for the user to explicitly say 검수 완료, then run:

bash scripts/publish_review_ok.sh \
  --series "야간조" \
  --episode 2 \
  --slug "불-꺼지면-가지-마세요" \
  --draft-file "/path/to/drafts/yaganjo_serial_drafts/야간조-연재-02-불-꺼지면-가지-마세요.md"

It will:

  • lint + asset-check + copy into Quartz (public)
  • sync Drama/<series>/index.md between episode markers

Scripts

A) Create episode stub

python3 scripts/new_episode.py \
  --series "야간조" \
  --series-dir "$WEBNOVEL_QUARTZ_ROOT/Drama/야간조" \
  --episode 2 \
  --slug "불-꺼지면-가지-마세요" \
  --draft-dir "/path/to/drafts/yaganjo_serial_drafts"

B) Convert PNG→WebP (fast)

bash scripts/to_webp.sh \
  /path/to/cover.png \
  /path/to/cover.webp

C) Lint an episode

python3 scripts/lint_episode.py \
  --file /path/to/episode.md

Production rules (the ones we actually used)

  • No writer commentary: remove lines like “그래서 더 진짜였다”
  • Show, don’t explain: replace intention-explanations with actions
  • No pattern spam: especially ~같아서 chains
  • Relationship progression: use two small debts (A→B and B→A), not long small talk
  • Hook: end every episode with a single, sharp next-step trigger

平台分布

OpenClaw

90.11%
按下载量换算11,211

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

未展示

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills