paper-polish-workflow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Purpose

用途

This Skill provides a systematic, top-down workflow for polishing academic papers. It works from structure to logic to expression, with user confirmation at each decision point. Expression options are drawn from reference-driven academic patterns rather than ad hoc rewrites, ensuring professional and consistent output suitable for journal submission.
本Skill提供用于学术论文润色的系统化自上而下工作流,遵循从结构到逻辑再到表达的顺序,每个决策节点都设置了用户确认环节。表达选项均来自参考驱动的学术范式,而非临时改写,可确保输出专业、统一,适合用于期刊投稿。

Trigger

触发条件

Activates when the user asks to:
  • Polish, revise, or improve an academic paper section by section
  • 润色、精修、逐步改进学术论文
Example invocations:
  • "Polish my paper section by section" / "润色论文"
  • "Help me revise my introduction step by step" / "精修论文"
  • "Guide me through polishing this draft" / "帮我逐步润色这篇论文"
用户提出以下需求时激活:
  • 逐段润色、修改或改进学术论文
  • 润色、精修、逐步改进学术论文
调用示例:
  • "Polish my paper section by section" / "润色论文"
  • "Help me revise my introduction step by step" / "精修论文"
  • "Guide me through polishing this draft" / "帮我逐步润色这篇论文"

Modes

模式

ModeDefaultBehavior
interactive
YesFull 4-step flow with user confirmation at each decision point
guided
Multi-pass with confirmation at key checkpoints only
direct
Single-pass polish using defaults; skip AskUserQuestion
batch
Same operation applied across multiple sections sequentially
Default mode:
interactive
Mode inference: "quickly" or "just fix" switches to
direct
. "step by step" or "逐步" confirms
interactive
(already default).
模式默认行为
interactive
完整4步流程,每个决策节点都需要用户确认
guided
多轮处理,仅在关键检查点需要确认
direct
使用默认设置单轮润色,跳过用户提问环节
batch
按顺序对多个段落执行相同操作
默认模式:
interactive
模式推断: 用户输入"quickly"或"just fix"时切换为
direct
模式,输入"step by step"或"逐步"时确认使用
interactive
模式(已为默认)。

References

参考资料

Required (always loaded)

必需项(始终加载)

FilePurpose
references/expression-patterns.md
Academic expression patterns overview and module index
文件用途
references/expression-patterns.md
学术表达范式概览与模块索引

Leaf Hints (loaded when needed)

细分提示文件(按需加载)

FileWhen to Load
references/expression-patterns/introduction-and-gap.md
Polishing introduction or background content
references/expression-patterns/methods-and-data.md
Polishing methods, data, or study area content
references/expression-patterns/results-and-discussion.md
Polishing results or discussion content
references/expression-patterns/conclusions-and-claims.md
Polishing conclusion content
references/expression-patterns/geography-domain.md
Content involves spatial, urban, or planning topics
references/anti-ai-patterns.md
Polishing expression (Step 3) -- screen for AI-sounding phrases
references/journals/ceus.md
Target journal is CEUS
文件加载时机
references/expression-patterns/introduction-and-gap.md
润色引言或背景内容时
references/expression-patterns/methods-and-data.md
润色方法、数据或研究区域内容时
references/expression-patterns/results-and-discussion.md
润色结果或讨论内容时
references/expression-patterns/conclusions-and-claims.md
润色结论内容时
references/expression-patterns/geography-domain.md
内容涉及空间、城市或规划主题时
references/anti-ai-patterns.md
润色表达环节(第3步)—— 筛查AI风格表述时
references/journals/ceus.md
目标期刊为CEUS时

Loading Rules

加载规则

  • Load expression patterns overview at start; select the appropriate leaf based on section type.
  • Load anti-AI patterns when polishing expression (Step 3).
  • Load journal template when target journal is specified.
  • Load
    geography-domain.md
    when spatial, urban, or planning content is detected.
  • If a reference file is missing, warn the user and proceed with reduced capability.
  • 启动时加载表达范式概览,根据段落类型选择对应的细分文件。
  • 润色表达环节(第3步)加载反AI范式文件。
  • 指定目标期刊时加载对应期刊模板。
  • 检测到空间、城市或规划相关内容时加载
    geography-domain.md
  • 如果参考文件缺失,警告用户后以受限能力继续运行。

Ask Strategy

提问策略

Before starting, ask about:
  1. Target journal (if not already known)
  2. Which section to work on
  3. Preferred mode (if ambiguous from trigger)
Rules:
  • Never ask more than 3 questions before producing initial output.
  • In
    direct
    mode, skip pre-questions if the user provided enough context.
  • In
    batch
    mode, skip per-item questions; apply settings from the first item.
  • Use Structured Interaction when available; fall back to plain-text questions otherwise.
  • See
    skill-conventions.md > AskUserQuestion Enforcement
    for full rules.
启动前需询问:
  1. 目标期刊(如果尚未知晓)
  2. 需要处理的段落
  3. 偏好模式(如果触发指令未明确说明)
规则:
  • 产出初始输出前提问不得超过3个。
  • direct
    模式下,如果用户提供了足够上下文,跳过前置提问。
  • batch
    模式下,跳过单项目提问,沿用首个项目的设置。
  • 优先使用结构化交互,否则回退到纯文本提问。
  • 完整规则参见
    skill-conventions.md > AskUserQuestion Enforcement

Workflow

工作流

Step 1: Collect Context

第1步:收集上下文

  • Determine input type (file path or pasted text).
  • Load required references (expression-patterns overview).
  • Identify target journal; load journal template if specified.
  • Read input content using the Read tool; extract key numbers, claims, and data points.
  • Locate example/reference papers if the user provides them (use Read tool for PDFs).
  • In
    interactive
    or
    guided
    mode: confirm scope with the user before proceeding.
  • 确定输入类型(文件路径或粘贴的文本)。
  • 加载必需参考资料(表达范式概览)。
  • 确认目标期刊,如已指定则加载对应期刊模板。
  • 使用Read工具读取输入内容,提取关键数字、主张和数据点。
  • 如果用户提供了示例/参考论文,使用Read工具读取PDF文件。
  • interactive
    guided
    模式下:继续执行前与用户确认处理范围。

Step 2: Structure & Logic Confirmation

第2步:结构与逻辑确认

  • Analyze section macro structure (e.g., Abstract = Background + Gap + Method + Results + Contribution).
  • Present a structure table for user confirmation.
  • Break content into sentences; assign a logic function to each.
  • Present the logic chain for user confirmation.
  • Checkpoint: user confirms structure and logic before expression work begins.
  • In
    direct
    mode: run structure and logic analysis internally, proceed to Step 3 automatically.
  • 分析段落宏观结构(例如:摘要 = 背景 + 研究缺口 + 方法 + 结果 + 贡献)。
  • 展示结构表格供用户确认。
  • 将内容拆分为句子,为每个句子分配逻辑功能。
  • 展示逻辑链供用户确认。
  • 检查点:用户确认结构和逻辑后,再开始表达润色工作。
  • direct
    模式下:内部执行结构和逻辑分析,自动进入第3步。

Step 3: Expression Polish & Consistency

第3步:表达润色与一致性检查

  • Load the section-appropriate expression pattern leaf and anti-AI patterns.
  • For each sentence with expression issues, present 2-3 options via AskUserQuestion (
    interactive
    mode) or apply the best option automatically (
    direct
    mode).
AskUserQuestion({
  question: "Which expression do you prefer for [sentence function]?",
  options: [
    { label: "[Expression A]", description: "[full sentence with expression A]" },
    { label: "[Expression B]", description: "[full sentence with expression B]" },
    { label: "[Expression C]", description: "[full sentence with expression C]" }
  ]
})
  • Reference paper consultation: when the user questions professionalism, use the Read tool to load example papers and extract expression patterns.
  • Journal style check: apply journal-specific requirements from the loaded template.
  • Repetition and coherence pass: check for repeated expressions and missing transitions; suggest fixes.
  • Cross-section consistency: verify numbers, terminology, and claims across sections.
  • 加载对应段落的表达范式细分文件和反AI范式文件。
  • 对每个存在表达问题的句子,通过AskUserQuestion提供2-3个选项供用户选择(
    interactive
    模式),或自动应用最优选项(
    direct
    模式)。
AskUserQuestion({
  question: "Which expression do you prefer for [sentence function]?",
  options: [
    { label: "[Expression A]", description: "[full sentence with expression A]" },
    { label: "[Expression B]", description: "[full sentence with expression B]" },
    { label: "[Expression C]", description: "[full sentence with expression C]" }
  ]
})
  • 参考论文查询: 当用户质疑专业性时,使用Read工具加载示例论文,提取表达范式。
  • 期刊风格检查: 应用已加载模板中期刊的特定要求。
  • 重复与连贯性检查: 检查重复表达和缺失的过渡内容,给出修复建议。
  • 跨段落一致性: 核对不同段落的数字、术语和主张是否一致。

Step 4: Output

第4步:输出

  • Generate highlights if the journal requires them (for CEUS, see
    references/journals/ceus.md
    ).
  • Suggest a read-aloud final check to catch awkward phrasing.
  • Compile all confirmed content into the final version.
  • Present the final version with word count for user confirmation.
  • Write to
    *_polished.md
    after confirmation (or automatically in
    batch
    mode).
  • Report word count and any journal constraint notes.
  • 如果期刊要求提供要点(针对CEUS,参见
    references/journals/ceus.md
    ),生成相应要点。
  • 建议用户通过朗读做最终检查,找出别扭的表述。
  • 将所有确认后的内容汇编为最终版本。
  • 展示最终版本及字数,供用户确认。
  • 确认后写入
    *_polished.md
    文件(
    batch
    模式下自动写入)。
  • 报告字数和所有期刊限制相关说明。

Output Contract

输出约定

OutputFormatCondition
polished_text
Markdown file (
*_polished.md
) or conversation output
Always produced
change_summary
Markdown in sessionAlways produced
Word countIntegerAlways reported
Journal compliance notesBullet listWhen a target journal is specified
输出格式触发条件
polished_text
Markdown文件(
*_polished.md
)或对话输出
始终生成
change_summary
会话内Markdown内容始终生成
字数整数始终报告
期刊合规说明无序列表指定目标期刊时生成

Edge Cases

边界情况处理

SituationHandling
Unprofessional word flaggedPresent 2-3 alternatives via AskUserQuestion; accept if user insists
Section too long for single passSplit into paragraph-level sub-passes; maintain cross-paragraph coherence
No journal specifiedDefault to general academic style; note in output
Mixed language inputDetect dominant language; ask user to confirm target language
Reference paper provided as PDFUse Read tool to load PDF; extract style patterns for expression matching
Abrupt sentence transitionProvide transition options via AskUserQuestion
Repetition detected between sectionsIdentify repeated content; suggest which occurrence to rephrase
Logic structure needs modificationReturn to Step 2 to re-confirm structure before continuing
场景处理方式
标记到不专业的用词通过AskUserQuestion提供2-3个替代选项;如果用户坚持使用原表述则接受
段落过长无法单次处理拆分为段落级的子处理环节,保持段落间连贯性
未指定期刊默认使用通用学术风格,在输出中注明
混合语言输入检测主流语言,询问用户确认目标语言
用户提供PDF格式的参考论文使用Read工具加载PDF,提取风格范式用于表达匹配
句子过渡突兀通过AskUserQuestion提供过渡选项
检测到段落间内容重复识别重复内容,建议对其中一处进行改写
逻辑结构需要修改回到第2步重新确认结构后再继续

Fallbacks

降级方案

ScenarioFallback
Structured Interaction unavailableAsk 1-3 plain-text questions covering highest-impact gaps; do not block workflow
Reference file missingLog the missing file, proceed with reduced capability, warn the user
Target journal not specifiedAsk once; if declined, use general academic style
PDF reference paper unreadableAsk user to paste relevant excerpts instead

Skill: paper-polish-workflow Conventions: references/skill-conventions.md
场景降级处理
无法使用结构化交互提出1-3个覆盖最高优先级信息缺口的纯文本问题,不阻塞工作流
参考文件缺失记录缺失文件,以受限能力继续运行,警告用户
未指定目标期刊询问一次;如果用户拒绝说明,使用通用学术风格
无法读取PDF格式的参考论文要求用户粘贴相关节选内容代替

Skill: paper-polish-workflow Conventions: references/skill-conventions.md