T
TUARAN涂阿燃 · 网络日志

Menu

...

检查登录状态…

© 2025—2026 网络日志·关于本站·关于站长·聊合作·留言板·RSS·支持本站·流量统计·提建议·CI Status

AI 项目/Skill 中心/出版社格式校对 Skill

publisher-format-review

出版社格式校对 Skill

已上架创作与分发Codex 可配置

按出版社图书出版规范校对/重写章节内容:序号层级、图表引出、AI 痕迹消除、口语化净化共 11 条规则。

基础信息

触发场景
当用户提交书稿章节、要求"按出版规范改写"、"图书排版校对"、"消除 AI 痕迹"时使用。
输入要求
一段或多段书稿原文(含标题、正文、列表、图表说明) / 可选:对比模式 / 清单模式
产出格式
修改后的完整章节文本 / 可选:前后对比 / 改动清单
验收标准
改写后忠实于原意;序号层级正确;图表引出规范;无 AI 痕迹与口语化表达;可直接交付排版。

内容

出版社格式 11 条规则

11 条
  1. 01

    序号层级

    一级"第一章" / 二级"1.1" / 三级"1.1.1" / 四级"1." / 分类"(1)"后面只能接标题;要列出成段文字时直接用 "1)" "①" "●"。

  2. 02

    图片引出

    引出话术:"XXX,如图 1-1 所示。" 每张图必须有章号-图序,图片居中,"图 1-1 说明文字"放在图片下方。

  3. 03

    标题层级不能混乱

    禁止跳级、禁止同级混用不同符号、禁止纯文字标题没有序号。

  4. 04

    引出话术要有关联

    段落、列表、图表的引出语必须承接上下文,不能突兀。

  5. 05

    消除 AI 生成痕迹

    排查排比堆砌、形容词扎堆、万能开头、套话总结、过度修辞,换成具体、可验证的事实陈述。

  6. 06

    用大模型统一优化

    提示词:"优化文字描述,用名词替代人称代词,无知识性差错、逻辑性差错、上下文不对应、语法语病、标点问题。符合出版社图书出版要求。"

  7. 07

    表格规范(与图相反)

    引出:"XXX,如表 1-1 所示。" 表序放在表格上方(图片相反),"表 1-1 说明"在表头之前。

  8. 08

    标题下加承上启下话术

    每个一级/二级标题正文开始前,加一段衔接性引入,说明这一节要讲什么、为什么讲。

  9. 09

    网址不出现在书中

    禁止正文出现 URL;纸质书印刷后链接易失效。改用"主流应用商店搜索 XXX"等稳定描述。

  10. 10

    整段加工而非逐句改

    把每个三级标题下的完整内容(300-800 字)作为一个单元送 AI 加工,让风格、用词、节奏统一。

  11. 11

    细节规范

    突然冒一句要改成独立段加粗;少用"我/你/他"换成"用户/创作者";模块名词全文统一;引号用 "" 而非 「」;移除恐怖意象(骷髅 / 血色等)。

配置到本地 Codex / 给智能体阅读 / 分享给同事

下载 / 复制 Skill 文件

~/.codex/skills/publisher-format-review

单独下载

SKILL.md
agents/openai.yaml

下载后放到 ~/.codex/skills/publisher-format-review 即可作为本地 Codex Skill 使用。也可直接复制 SKILL.md 粘贴到 Claude Code / Cursor / ChatGPT 当 system prompt。

SKILL.md

---
name: publisher-format-review
description: Use when the user submits book chapter drafts and asks for "publishing-format proofreading", "AI-trace removal", or "出版社规范改写"; rewrite chapters to meet Chinese publisher requirements (numbering, figure/table conventions, de-colloquialization, terminology unification).
---

# Publisher Format Review

Use this skill when the user provides book/manuscript chapter content and asks for publisher-grade proofreading or rewriting.

## When to use

- User pastes one or more chapter sections (titles + body + lists + figure/table mentions)
- User asks "按出版社格式改" / "图书排版校对" / "消除 AI 痕迹" / "书稿规范化"

## 11 rules

1. **Numbering hierarchy**: "第一章" / "1.1" / "1.1.1" / "1." / "(1)" only attach to titles. For listing paragraphs, use "1)" "2)" "①" "●". Never use "1." "2." for body paragraphs.
2. **Figure callout**: "XXX,如图 1-1 所示。" Each figure needs chapter-figure number; figure centered; caption "图 1-1  描述" below image.
3. **No broken hierarchy**: never skip levels; never mix symbols at the same level; every title must carry its number.
4. **Linked transitions**: every paragraph / list / figure / table must have a sentence connecting upstream / downstream context.
5. **Strip AI traces**: parallel-clause overuse, adjective stacking, generic openings ("在数字化时代背景下"), summary clichés ("综上所述"), excessive metaphor → replace with concrete facts.
6. **Bulk LLM rewrite**: send each 3rd-level section (300-800 chars) as a unit with the prompt: "优化文字描述,用名词替代人称代词,无知识性差错、逻辑性差错、上下文不对应、语法语病、标点问题。符合出版社图书出版要求。"
7. **Table convention (inverse of figures)**: callout "XXX,如表 1-1 所示。" Table caption "表 1-1  描述" goes ABOVE the table, not below.
8. **Lead-in paragraph under each title**: every level-1 / level-2 title needs a bridging paragraph explaining what / why before content begins.
9. **No URLs in print**: never include "https://..." in book body; URLs decay after print. Use "在主流应用商店搜索 XXX" style.
10. **Whole-section rewriting, not line-by-line**: process a complete 3rd-level section at once so style/tone/rhythm stay unified.
11. **Detail discipline**:
   - Stray single sentences → wrap into a paragraph with **bold emphasis**
   - Colloquial expressions ("其实你只要点一下") → formal ("用户点击即可")
   - Remove disturbing imagery (骷髅 / 血色 / etc.)
   - Module names unified across entire chapter (don't mix "豆包 APP" / "豆包" / "豆包软件")
   - Personal pronouns (我 / 你 / 他) → nouns (用户 / 创作者 / 读者)
   - Quote marks "" not 「」

## Output

- Default: return the full rewritten chapter text (not just diffs), in Markdown, preserving original heading structure.
- If user asks "对比": two-column table (before / after).
- If user asks "清单": list each change with original snippet + revised snippet.

## Constraints

- Stay faithful to original meaning; never drop information for the sake of "规范化".
- Output must be print-ready; no "XXX" placeholders or "[待补]" markers.
- For AI-trace flagging, point out WHICH sentence is the AI trace.
- Never invent facts (product features, statistics) not in original.

## Shareability

This skill is self-contained and can be:
1. Copied as system prompt into Codex / Cursor / ChatGPT / Claude Code
2. Shared as a link via Claude Code's skill sharing feature
3. Printed as internal editorial guideline (the 11 rules above)

agents/openai.yaml

interface:
  display_name: "Publisher Format Review"
  short_description: "按出版社规范校对/重写书稿章节"
  default_prompt: "Use $publisher-format-review to rewrite the chapter for publishing standards."

policy:
  allow_implicit_invocation: true
← 返回 Skill 中心