跳到主要内容
知仓学习社ZHICANG

neurips-author-response

Use when drafting or triaging NeurIPS OpenReview author responses, rebuttals, and discussion-period replies under the current year's response mechan…

不碰外部(只输出文字)无严重或高危命中brycewang-stanford/Awesome-Journal-Skills

它会碰到什么

扫了多少1 个文本文件,3 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

NeurIPS Author Response

Use this skill after reviews are released. The goal is to clarify, correct misunderstandings, and

move reviewers and ACs toward a technically accurate decision without implying a revised paper has

replaced the submitted version.

2026 response mechanics to re-check

The 2026 handbook describes a three-phase response/discussion process: initial author response,

author-reviewer-AC discussion, then reviewer/AC discussion. It also states that authors respond

through OpenReview rebuttal buttons, with a per-review 10,000-character limit, no file uploads, no

identity-revealing content, and no links except an anonymized code link to the AC in an Official

Comment when reviewers ask for code. Reopen the current handbook before using these limits.

Response triage

  • Start from decision leverage, not reviewer score. Identify the few objections that ACs can use to

justify rejection: correctness, missing baseline, unclear novelty, weak significance, anonymity,

ethics, or reproducibility.

  • Separate misunderstandings from real gaps. Correct the former directly; acknowledge the latter and

explain what existing evidence in the original submission supports.

  • Do not promise a new paper. New results can clarify, but the original submission remains the basis

for the recommendation.

  • Keep every response anonymous and link-free unless the current official policy gives an explicit

exception.

Drafting pattern

  1. Thank reviewers briefly, then state the central clarification.
  2. Answer the highest-leverage technical objection first.
  3. Point to exact sections, equations, figures, appendix items, or checklist answers.
  4. If adding a small result, state that it supports an existing claim and can be incorporated if

accepted.

  1. Close with the concrete change that would appear in camera-ready, not a broad promise.

Pitfalls

  • Arguing with tone instead of evidence.
  • Spending space on low-confidence praise or score complaints.
  • Uploading files, posting links, or identifying authors.
  • Treating the response as a full revision.
  • Ignoring the meta-review, AC questions, or reviewer-author professional obligations.

Output format

[Response priority] <reviewer/AC issue to address first>
[Decision leverage] High / Medium / Low
[Draft response] <anonymous OpenReview-ready text>
[Evidence cited] <paper section / appendix / checklist item>
[Do not say] <phrases or promises to avoid>

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。