icalp-author-response

GitHub

指导作者针对ICALP会议撰写Track B反驳信或处理Track A正确性质询。强调纠正误读、解决具体技术疑问及诚实面对漏洞,严格遵守双盲规则与字数限制,避免争论重要性。

ICALP-Skills/skills/icalp-author-response/SKILL.md brycewang-stanford/Awesome-Journal-Skills

Trigger Scenarios

撰写ICALP Track B初始审稿后的反驳信 回应ICALP Track A关于论文正确性的质询

Install

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-author-response -g -y
More Options

Non-standard path

npx skills add https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICALP-Skills/skills/icalp-author-response -g -y

Use without installing

npx skills use brycewang-stanford/Awesome-Journal-Skills@icalp-author-response

指定 Agent (Claude Code)

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-author-response -a claude-code -g -y

安装 repo 全部 skill

npx skills add brycewang-stanford/Awesome-Journal-Skills --all -g -y

预览 repo 内 skill

npx skills add brycewang-stanford/Awesome-Journal-Skills --list

SKILL.md

Frontmatter
{
    "name": "icalp-author-response",
    "description": "Use when writing an ICALP (EATCS) Track B rebuttal in response to initial reviews, or when handling a Track A correctness query — correcting reviewer misreadings of a proof, pointing to the exact lemma or step that answers an objection, conceding real gaps honestly, and staying within the lightweight double-blind rules and the short rebuttal window."
}

ICALP Author Response

Two very different situations live here, because the tracks differ:

  • Track B gives you a rebuttal window (ICALP 2026: 21-24 March) to respond to initial reviews.
  • Track A has no general rebuttal; authors are contacted only if the PC needs to resolve a correctness issue. If that happens, answer narrowly and precisely.

There is no revision round at ICALP (unlike a journal), so the response is your one and only chance to speak — and it can only move a paper by fixing misreadings and correctness doubts, never by arguing taste.

Track B rebuttal: what it can and cannot do

A rebuttal moves a borderline paper when it:

  • Corrects a factual misreading of a definition, hypothesis, or proof step.
  • Points to the exact place an objection is already answered ("Lemma 4 assumes X, which the reviewer's counterexample violates; see line ...").
  • Supplies a missing clarification a reviewer explicitly asked for (a constant, a boundary case, a comparison to a bound they named).

It does not move a paper when it:

  • Argues the result is more important than the reviewer thinks (taste).
  • Promises to add a proof "in the final version" that is not already written.
  • Re-derives the whole paper instead of answering the specific point.

Triage the reviews first

[Correctness doubt] a reviewer questions a specific step -> HIGHEST priority: resolve it exactly
[Misreading]        a reviewer misstates what you proved -> correct crisply, cite the line
[Missing comparison] "how does this compare to [bound]?" -> give the one-sentence comparison
[Significance/taste] "not surprising / incremental"     -> brief, factual context; do not litigate
[Genuine gap]        a real hole they found             -> concede honestly; state what survives

Spend your limited words on correctness and misreadings, which you can actually change, not on significance debates, which you usually cannot.

Answering a correctness doubt (the make-or-break case)

Because there is no revision round, a real proof gap is usually fatal — but a misperceived gap is very much winnable:

  • If the reviewer misread: quote the exact hypothesis/lemma/line that closes their concern, in two or three sentences. Precision beats volume.
  • If the gap is real but reparable and the repair is already in the full version: point to it precisely; do not claim a fix you have not written.
  • If the gap is real and open: say so. State exactly which results still hold and which are weakened. Honesty preserves your credibility and the salvageable parts.

Track A correctness contact

If Track A reaches out about correctness, treat it like a focused Track B correctness answer: address only the step in question, point to the proof, and provide the missing detail. Do not use it to argue significance or add new claims.

Form and constraints

  • Stay anonymous. The rebuttal is part of lightweight double-blind review — no author names, institutions, or de-anonymizing "as we did in [our other paper]".
  • Be concise and mapped. Answer per reviewer and per point; a reviewer should find their concern addressed without hunting.
  • Lead with the highest-stakes correctness point, then misreadings, then clarifications.
  • No new theorems. You may clarify or point to existing proofs; you may not introduce results the referees have not seen.

Response skeleton (Track B)

Summary (2-3 sentences): what we clarify, and the one correctness point we resolve.

Reviewer 1
  - [Correctness] Concern about Step 3: <exact hypothesis/lemma/line that answers it>.
  - [Misreading] R1 states we assume <X>; we assume <Y> (Def 2). Consequence: <...>.
Reviewer 2
  - [Comparison] vs the bound of [ref]: <one-sentence comparison>.
  - [Clarification] <the requested constant / boundary case>.
Reviewer 3
  - [Conceded] The gap in Lemma 6 is real; Theorems 1-2 are unaffected; Cor 3 weakens to <...>.

Output format

[Track] B (rebuttal window) / A (correctness contact only)
[Triage] correctness doubts / misreadings / comparisons / taste / real gaps — counts
[Priority answers] the correctness/misreading points that can actually change the decision
[Concessions] real gaps, stated honestly, with what survives
[Anonymity] response free of identifying info? yes/no
[Forbidden] new theorems / taste arguments / promised-but-unwritten proofs — present? remove

Version History

  • 9f86f09 Current 2026-07-19 15:53

Same Skill Collection

AAAI-Skills/skills/aaai-artifact-evaluation/SKILL.md
AAAI-Skills/skills/aaai-author-response/SKILL.md
AAAI-Skills/skills/aaai-camera-ready/SKILL.md
AAAI-Skills/skills/aaai-experiments/SKILL.md
AAAI-Skills/skills/aaai-related-work/SKILL.md
AAAI-Skills/skills/aaai-reproducibility/SKILL.md
AAAI-Skills/skills/aaai-review-process/SKILL.md
AAAI-Skills/skills/aaai-submission/SKILL.md
AAAI-Skills/skills/aaai-supplementary/SKILL.md
AAAI-Skills/skills/aaai-topic-selection/SKILL.md
AAAI-Skills/skills/aaai-workflow/SKILL.md
AAAI-Skills/skills/aaai-writing-style/SKILL.md
AAMAS-Skills/skills/aamas-artifact-evaluation/SKILL.md
AAMAS-Skills/skills/aamas-author-response/SKILL.md
AAMAS-Skills/skills/aamas-camera-ready/SKILL.md
AAMAS-Skills/skills/aamas-experiments/SKILL.md
AAMAS-Skills/skills/aamas-related-work/SKILL.md
AAMAS-Skills/skills/aamas-reproducibility/SKILL.md
AAMAS-Skills/skills/aamas-review-process/SKILL.md
AAMAS-Skills/skills/aamas-submission/SKILL.md
AAMAS-Skills/skills/aamas-supplementary/SKILL.md
AAMAS-Skills/skills/aamas-topic-selection/SKILL.md
AAMAS-Skills/skills/aamas-workflow/SKILL.md
AAMAS-Skills/skills/aamas-writing-style/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-editor-strategy/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-evidence-standards/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-literature-synthesis/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-organizing-framework/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-proposal-framing/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-review-process/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-revision/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-submission/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-tables-figures/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-topic-selection/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-workflow/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-writing-style/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-contribution-framing/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-data-analysis/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-literature-positioning/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-methods/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-rebuttal/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-review-process/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-submission/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-tables-figures/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-theory-development/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-topic-selection/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-workflow/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-writing-style/SKILL.md
Academy-of-Management-Review-Skills/skills/amr-contribution-framing/SKILL.md
Academy-of-Management-Review-Skills/skills/amr-data-analysis/SKILL.md

Metadata

Files
0
Version
9f86f09
Hash
911f2a94
Indexed
2026-07-19 15:53

Accueil - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 07:00
浙ICP备14020137号-1 $Carte des visiteurs$