本文へ移動
cccskills
無料GitHub で公開

asq-rebuttal

Use when drafting the response to an Administrative Science Quarterly (ASQ) R&R after the manuscript has been revised — structuring the response letter and handling reviewer/editor comments. Drafts the response; it does not perform the underlying revisions (do those first).

インストール方法を見る

含まれるファイル(1)

  • SKILL.md4.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

R&R Rebuttal (asq-rebuttal)

When to trigger

  • You have an ASQ R&R and have already revised the manuscript
  • You need to structure a point-by-point response document
  • Reviewers disagree and you must navigate between them without contradicting yourself

Revise the paper first. The response letter documents changes you made; it is not a substitute for making them. If you have not revised yet, return to the relevant asq-* skill.

Mindset for an ASQ revision

ASQ's review is developmental — treat reviewers as collaborators who took the idea seriously. The winning posture is gracious, responsive, and intellectually serious: accommodate where they are right, and where you disagree, argue with evidence and respect rather than dismissal. The central question the handling editor (under Editor Beth Bechky, term began July 1, 2025) and reviewers will ask is "did the idea mature?" — consistent with ASQ's emphasis on curating papers that will endure. Foreground how the contribution got deeper, not just which boxes you ticked. A response letter that reads as a checklist of mechanical robustness additions — adequate at some quantitative-leaning journals — will underperform here if the theoretical insight has not sharpened.

Structure of the response

  1. Cover note to the editor. Thank the team; summarize the 3–5 most important changes and how the contribution is now sharper. Address the editor's central theoretical ask explicitly and up front.
  2. Point-by-point responses, grouped by reviewer, then by comment. For each:
    • Quote the comment verbatim (or faithfully paraphrase).
    • State your response: Accepted / Partially accepted / Respectfully disagree.
    • Describe the exact change and cite the new location (page, section, table).
    • Where you disagree, give the reasoned case with evidence, and offer a compromise if possible.
  3. A summary of major changes at the top is helpful for editors tracking a multi-round file.

Handling hard cases

  • Reviewers disagree: state both positions, explain your resolution, and let the editor see you reasoned it through. Do not silently side with one and ignore the other.
  • A request would harm the paper: explain why (theoretical or evidentiary cost), propose an alternative that meets the underlying concern, and defer to the editor.
  • "Deepen the contribution": this is the most common ASQ ask — show concretely how the theory is now sharper, the surprise clearer, the mechanism more specified. Mechanical additions alone will not satisfy it.
  • Out-of-scope requests: politely note scope and, if useful, flag them as future work.

Tone and craft

  • Respectful, specific, and confident — never defensive or dismissive.
  • Make the editor's job easy: clear navigation, change locations, and a quotable summary.
  • Keep the letter self-contained; a reviewer should not need the tracked-changes file to follow it.
  • Ensure consistency: a change made for Reviewer 1 must not contradict a response to Reviewer 2.

Checklist

  • Manuscript revised before writing the letter
  • Editor's central theoretical ask addressed first and explicitly
  • Every comment answered; none skipped or merged away
  • Each response states accept/partial/disagree + the exact change location
  • Disagreements argued with evidence and a proposed compromise
  • Reviewer conflicts navigated without internal contradictions
  • "Deepen the contribution" answered with substance, not just additions
  • Tone gracious and serious throughout; letter is self-contained

Anti-patterns

  • Writing the response before actually revising
  • Defensive or dismissive replies ("the reviewer misunderstood")
  • Claiming a change was made without pointing to where
  • Satisfying one reviewer in a way that contradicts another's response
  • Answering "deepen the contribution" with cosmetic additions
  • A letter that requires the editor to diff the manuscript to verify changes

Output format

【Round】1st / 2nd / later
【Editor's core ask addressed】how + where
【Comments handled】N / N (none skipped)
【Disagreements】[...] + evidence/compromise
【Contribution deepened】how the idea matured
【Consistency check】no cross-reviewer contradictions
【Next step】resubmit via the editorial system

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

brycewang-stanford のスキルをすべて見る

このスキルの問題を報告する