camera-ready-finalizer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Camera-Ready Finalizer

Camera-Ready终稿整理器

Finalize an accepted paper so the submitted camera-ready version is consistent, de-anonymized, claim-safe, and ready to hand off to code release or artifact evaluation.

Use this skill when:

a paper has been accepted and the user needs the camera-ready version
author-response or discussion promises must be checked against the final PDF
anonymized submission text must become final author-facing text
acknowledgements, author metadata, code links, project pages, or funding statements must be added
final figures, tables, captions, appendix, supplement, and references must be synchronized
new rebuttal experiments or reviewer-requested edits must be integrated cleanly
the paper needs a final claim/evidence/citation/code-release consistency pass before upload

Do not use this skill for pre-submission readiness. Use

submit-paper

before initial submission. Use

rebuttal-strategist

while reviews are still active. Use

release-code

for the public code repository after paper-facing obligations are clear.

Pair this skill with:

```
rebuttal-strategist
```
to recover reviewer issues, response promises, and promised revisions
```
paper-evidence-board
```
to close final claim/evidence/risk/action links
```
figure-results-review
```
to recheck final figures, captions, and tables after edits
```
citation-audit
```
for final BibTeX, citation, label, and metadata correctness
```
citation-coverage-audit
```
when accepted-paper edits reveal missing related work
```
conference-writing-adapter
```
for final wording of accepted reviewer criticism or limitations
```
submit-paper
```
for final format and compile checks
```
release-code
```
and
```
artifact-evaluation-prep
```
for public code and artifact handoff
```
add-git-tag
```
when marking the accepted/camera-ready milestone
```
research-project-memory
```
when final paper status should persist across sessions

将已被录用的论文整理为符合要求的camera-ready终稿，确保内容一致、完成去匿名化、论点严谨，可顺利交接至代码发布或成果评估环节。

以下场景适用本技能：

论文已被录用，用户需要准备camera-ready终稿
需要对照最终PDF检查作者回复或讨论中承诺的修改事项
需要将匿名提交版本转换为包含作者信息的最终版本
需要添加致谢、作者元数据、代码链接、项目页面或资助声明
需要同步最终图表、表格、标题、附录、补充材料及参考文献
需要将反驳阶段新增的实验或评审要求的修改内容自然整合到论文中
论文在上传前需要进行最终的论点/证据/引用/代码发布一致性检查

请勿在预提交准备阶段使用本技能。初次提交前请使用

submit-paper

技能；评审仍在进行时请使用

rebuttal-strategist

技能；论文相关义务明确后，公开代码仓库请使用

release-code

技能。

可搭配以下技能使用：

```
rebuttal-strategist
```
：找回评审问题、回复承诺及约定的修改内容
```
paper-evidence-board
```
：完成最终论点/证据/风险/行动项的关联闭环
```
figure-results-review
```
：修改后重新检查最终图表、标题及表格
```
citation-audit
```
：确保最终BibTeX、引用、标签及元数据的正确性
```
citation-coverage-audit
```
：当录用论文的修改暴露出相关研究缺失时使用
```
conference-writing-adapter
```
：针对已接受的评审意见或局限性进行最终措辞调整
```
submit-paper
```
：进行最终格式及编译检查
```
release-code
```
和
```
artifact-evaluation-prep
```
：用于公开代码及成果交接
```
add-git-tag
```
：标记已录用/camera-ready里程碑
```
research-project-memory
```
：需要跨会话保留最终论文状态时使用

Skill Directory Layout

技能目录结构

text

<installed-skill-dir>/
├── SKILL.md
└── references/
    ├── claim-evidence-final-lock.md
    ├── de-anonymization.md
    ├── final-submission-audit.md
    ├── memory-writeback.md
    ├── rebuttal-promise-audit.md
    ├── release-handoff.md
    ├── report-template.md
    └── supplement-consistency.md

text

<installed-skill-dir>/
├── SKILL.md
└── references/
    ├── claim-evidence-final-lock.md
    ├── de-anonymization.md
    ├── final-submission-audit.md
    ├── memory-writeback.md
    ├── rebuttal-promise-audit.md
    ├── release-handoff.md
    ├── report-template.md
    └── supplement-consistency.md

Progressive Loading

渐进式加载

Always read

references/rebuttal-promise-audit.md

references/de-anonymization.md

references/claim-evidence-final-lock.md

, and

references/final-submission-audit.md

Read
```
references/supplement-consistency.md
```
when appendix, supplement, checklist, or extra material exists.
Read
```
references/release-handoff.md
```
when code, project page, artifact, data, checkpoints, or reproduction links are involved.
Read
```
references/report-template.md
```
before writing the final report.
Read
```
references/memory-writeback.md
```
when the project has
```
memory/
```
, component
```
.agent/
```
folders, or the user asks for persistent memory.
If venue-specific camera-ready rules matter, verify current official venue instructions before making hard claims about page limits, required sections, licenses, checklists, or upload fields.

务必阅读

references/rebuttal-promise-audit.md

、

references/de-anonymization.md

、

references/claim-evidence-final-lock.md

及

references/final-submission-audit.md

。

当存在附录、补充材料、检查清单或额外内容时，阅读
```
references/supplement-consistency.md
```
。
涉及代码、项目页面、成果、数据、检查点或复现链接时，阅读
```
references/release-handoff.md
```
。
撰写最终报告前，阅读
```
references/report-template.md
```
。
当项目包含
```
memory/
```
目录、组件
```
.agent/
```
文件夹，或用户要求持久化记忆时，阅读
```
references/memory-writeback.md
```
。
若会议特定的camera-ready规则至关重要，在对页数限制、必填章节、许可证、检查清单或上传字段做出明确判断前，请核实当前官方会议指南。

Core Principles

核心原则

Camera-ready is a consistency and obligation closeout, not a new paper rewrite.
Every rebuttal promise should be either fulfilled, explicitly superseded, or documented as not applicable.
De-anonymization must be complete but should not introduce new claims or unsupported links.
Final claims must match final evidence, figures, tables, supplement, and code.
New post-acceptance edits should reduce risk, not reopen novelty or evaluation disputes.
The main paper, appendix, supplement, metadata, and code links must tell the same story.
The final output should leave a clear handoff to release, artifact evaluation, tagging, and archival memory.

Camera-ready阶段是确保一致性和履行承诺的收尾环节，而非重新撰写论文。
每一项反驳阶段的承诺都应要么已完成，要么被明确取代，要么记录为不适用。
去匿名化必须彻底，但不得引入新论点或无依据的关联。
最终论点必须与最终证据、图表、表格、补充材料及代码保持一致。
录用后的新修改应降低风险，而非重新引发创新性或评估争议。
主论文、附录、补充材料、元数据及代码链接必须传达一致的信息。
最终输出应清晰衔接至发布、成果评估、标记及存档记忆环节。

Step 1 - Recover Acceptance Context

步骤1 - 收集录用相关信息

Collect:

paper directory and main LaTeX file
target venue and camera-ready deadline
acceptance email, meta-review, reviews, discussion, and author responses
rebuttal promise list, if available
current accepted draft and current camera-ready draft
final figures, tables, supplement, appendix, checklist, and bibliography
author list, affiliations, acknowledgements, funding, project/code/data links
code release or artifact expectations

project memory IDs such as

CLM-###

EVD-###

RSK-###

ACT-###

REV-###

, or

PROM-###

If no promise list exists, create one from reviews, rebuttal, and discussion before editing the paper.

收集以下材料：

论文目录及主LaTeX文件
目标会议及camera-ready提交截止日期
录用邮件、元评审意见、评审意见、讨论记录及作者回复
若有反驳承诺清单，请提供
当前已录用草稿及当前camera-ready草稿
最终图表、表格、补充材料、附录、检查清单及参考文献
作者列表、所属机构、致谢、资助信息、项目/代码/数据链接
代码发布或成果评估要求

项目记忆ID，如

CLM-###

、

EVD-###

、

RSK-###

、

ACT-###

、

REV-###

或

PROM-###

若没有承诺清单，请在修改论文前根据评审意见、反驳内容及讨论记录创建一份。

Step 2 - Audit Rebuttal Promises

步骤2 - 审核反驳阶段承诺

Read

references/rebuttal-promise-audit.md

Build a promise ledger:

reviewer/source
promise or implied commitment
required paper change
current status
location in final draft
evidence or artifact link
risk if omitted

Statuses:

```
fulfilled
```
```
partially-fulfilled
```
```
superseded
```
```
not-applicable
```
```
missing
```
```
needs-author-decision
```

Do not silently drop a promise because it is inconvenient. If a promise cannot be fulfilled, mark the risk and draft a conservative note or limitation if needed.

阅读

references/rebuttal-promise-audit.md

。

建立承诺台账：

评审者/来源
承诺或隐含的义务
所需的论文修改
当前状态
在最终草稿中的位置
证据或成果链接
遗漏后的风险

状态选项：

```
fulfilled
```
（已完成）
```
partially-fulfilled
```
（部分完成）
```
superseded
```
（已被取代）
```
not-applicable
```
（不适用）
```
missing
```
（未完成）
```
needs-author-decision
```
（需作者决策）

请勿因不便而擅自忽略承诺。若某项承诺无法完成，请标记风险，必要时起草保守说明或局限性内容。

Step 3 - De-Anonymize and Restore Final Metadata

步骤3 - 去匿名化及恢复最终元数据

Read

references/de-anonymization.md

Check:

author names, order, affiliations, emails, and footnotes
acknowledgements, funding, compute grants, institutional resources
code, data, project page, model, and appendix links
self-citations and anonymized references
removed anonymity placeholders
PDF metadata and artifact metadata where applicable
license, copyright, and publisher-specific final metadata if required

Do not invent funding, affiliation, or author-order details. Ask the user if a required personal/institutional detail is missing.

阅读

references/de-anonymization.md

。

检查以下内容：

作者姓名、排序、所属机构、邮箱及脚注
致谢、资助、计算资源资助、机构资源说明
代码、数据、项目页面、模型及附录链接
自引及匿名参考文献
是否已移除匿名占位符
PDF元数据及相关成果元数据（如适用）
若有要求，需符合许可证、版权及出版商特定的最终元数据规范

请勿编造资助、所属机构或作者排序信息。若缺失必要的个人/机构信息，请询问用户。

Step 4 - Lock Claims Against Final Evidence

步骤4 - 锁定论点与最终证据的一致性

Read

references/claim-evidence-final-lock.md

For each main claim:

final paper location
supporting figure/table/theorem/experiment/citation
final status: supported, narrowed, moved-to-appendix, limitation, or cut
whether new rebuttal experiments changed the claim
whether captions and result prose match final numbers
whether supplement and code agree with the paper

If a claim is unsupported, either narrow it, move it to limitations/future work, or cut it.

阅读

references/claim-evidence-final-lock.md

。

针对每一项核心论点：

在最终论文中的位置
支持的图表/表格/定理/实验/引用
最终状态：已支持、已缩小范围、移至附录、列为局限性或已删除
反驳阶段新增实验是否改变了论点
标题及结果描述是否与最终数据一致
补充材料及代码是否与论文内容一致

若论点缺乏支持，请缩小范围、移至局限性/未来工作部分，或删除该论点。

Step 5 - Check Supplement and Appendix Consistency

步骤5 - 检查补充材料及附录一致性

Read

references/supplement-consistency.md

when relevant.

Check:

main paper references to appendix/supplement resolve
appendix numbering, figure/table labels, and cross-references are correct
supplement claims do not contradict the main paper
extra experiments are summarized consistently
reviewer-requested details are easy to find
checklists, ethics, limitations, broader impacts, and reproducibility sections match final venue requirements

当涉及相关内容时，阅读

references/supplement-consistency.md

。

检查以下内容：

主论文对附录/补充材料的引用是否可正常跳转
附录编号、图表标签及交叉引用是否正确
补充材料中的论点是否与主论文矛盾
额外实验的总结是否一致
评审要求的细节是否易于查找
检查清单、伦理说明、局限性、更广泛影响及可复现性章节是否符合最终会议要求

Step 6 - Run Final Submission Audit

步骤6 - 执行最终提交审核

Read

references/final-submission-audit.md

Check:

venue camera-ready instructions and upload requirements
page limits and final formatting
compile status and final PDF sanity
bibliography and metadata
labels, references, figures, tables, algorithms, equations, and appendices
stale TODOs, comments, draft macros, anonymization text, or hidden placeholders
final title, abstract, author metadata, and PDF filename
final link reachability if links are included

Use

citation-audit

and

submit-paper

for detailed checks when needed.

阅读

references/final-submission-audit.md

。

检查以下内容：

会议camera-ready指南及上传要求
页数限制及最终格式
编译状态及最终PDF合理性
参考文献及元数据
标签、引用、图表、表格、算法、公式及附录
过时的TODO、注释、草稿宏、匿名文本或隐藏占位符
最终标题、摘要、作者元数据及PDF文件名
若包含链接，检查最终链接是否可访问

必要时使用

citation-audit

和

submit-paper

技能进行详细检查。

Step 7 - Prepare Release and Artifact Handoff

步骤7 - 准备发布及成果交接

Read

references/release-handoff.md

when relevant.

Produce handoff items for:

```
release-code
```
: repository visibility, README, license, citation file, tag, model/data links, reproduction commands
```
artifact-evaluation-prep
```
: install instructions, expected runtime, minimal demo, hardware, checkpoints, data, troubleshooting
```
add-git-tag
```
: accepted/camera-ready milestone summary
project memory closeout

Keep paper finalization separate from code release, but make obligations explicit.

当涉及相关内容时，阅读

references/release-handoff.md

。

生成以下交接材料：

给
```
release-code
```
的内容：仓库可见性、README、许可证、引用文件、标签、模型/数据链接、复现命令
给
```
artifact-evaluation-prep
```
的内容：安装说明、预期运行时间、最小化演示、硬件要求、检查点、数据、故障排除指南
给
```
add-git-tag
```
的内容：已录用/camera-ready里程碑摘要
项目记忆收尾内容

请将论文终稿整理与代码发布分开处理，但需明确相关义务。

Step 8 - Write the Camera-Ready Report

步骤8 - 撰写Camera-Ready报告

Read

references/report-template.md

If saving to a project and no path is given, use:

text

docs/submission/camera_ready_audit_YYYY-MM-DD_<venue>.md

The report must include:

readiness decision
blocking issues
promise ledger
de-anonymization status
final claim/evidence lock
supplement/appendix consistency
final submission audit
release/artifact handoff
memory update section

阅读

references/report-template.md

。

若需保存到项目且未指定路径，请使用：

text

docs/submission/camera_ready_audit_YYYY-MM-DD_<venue>.md

报告必须包含：

提交就绪决策
阻塞性问题
承诺台账
去匿名化状态
最终论点/证据锁定情况
补充材料/附录一致性检查
最终提交审核结果
发布/成果交接内容
记忆更新部分

Step 9 - Write Back to Project Memory

步骤9 - 写入项目记忆

Read

references/memory-writeback.md

when memory exists.

Update:

```
memory/decision-log.md
```
: acceptance and camera-ready decisions
```
memory/claim-board.md
```
: final claim status
```
memory/evidence-board.md
```
: final paper-ready evidence and artifact links
```
memory/risk-board.md
```
: any residual accepted risks
```
memory/action-board.md
```
: final blockers, release tasks, artifact tasks, and tag tasks
```
paper/.agent/
```
: camera-ready status, final metadata, final PDF path, final upload notes
```
rebuttal/.agent/
```
: promise fulfillment status and accepted outcome

当存在项目记忆时，阅读

references/memory-writeback.md

。

更新以下内容：

```
memory/decision-log.md
```
：录用及camera-ready相关决策
```
memory/claim-board.md
```
：最终论点状态
```
memory/evidence-board.md
```
：最终可用于论文的证据及成果链接
```
memory/risk-board.md
```
：任何剩余的已接受风险
```
memory/action-board.md
```
：最终阻塞项、发布任务、成果任务及标签任务
```
paper/.agent/
```
：camera-ready状态、最终元数据、最终PDF路径、最终上传说明
```
rebuttal/.agent/
```
：承诺完成状态及录用结果

Final Sanity Check

最终合理性检查

Before finalizing:

all rebuttal promises are accounted for
author metadata and acknowledgements are complete
no anonymity placeholders remain
final claims match final evidence
figures/tables/captions/supplement/code links are consistent
final references and labels are clean or routed to
```
citation-audit
```
final format is clean or routed to
```
submit-paper
```
code/artifact/release obligations are routed
project memory records the accepted/camera-ready state

完成终稿前，请确认：

所有反驳阶段承诺均已落实
作者元数据及致谢内容完整
无匿名占位符残留
最终论点与最终证据一致
图表/表格/标题/补充材料/代码链接保持一致
最终引用及标签已清理或已交由
```
citation-audit
```
处理
最终格式已清理或已交由
```
submit-paper
```
处理
代码/成果/发布相关义务已对接
项目记忆已记录已录用/camera-ready状态