/aistats-author-response
Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aistats-author-response --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/aistats-author-response
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification
SKILL.md
aistats-author-response.SKILL.mdname: aistats-author-response
description: Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification strategy for theory-plus-experiments papers.
AISTATS Author Response
Use this after AISTATS reviews are released. Reopen the current OpenReview instructions and author-discussion policy before drafting because response mechanics are cycle-specific.
Triage
- Answer concerns that affect correctness, novelty, statistical validity, clarity,
reproducibility, or fit for AISTATS.
- Use existing submitted evidence: paper sections, appendices, supplementary material,
theorem statements, experiments, checklist entries, and code/data descriptions.
- Keep the reply anonymous. Do not reveal institution, authorship, grants, private URLs, or
repository ownership.
- Treat discussion as clarification, not revision. Do not depend on uploading a revised paper
or new supplement unless current instructions explicitly allow it.
- If current rules prohibit links, do not use URLs in the discussion. AISTATS 2026
author-reviewer discussion was text-only and links were not allowed.
- Correct factual errors first, then address requests for missing comparisons, uncertainty
estimates, proofs, or hyperparameters.
Drafting pattern
1. State the decision-critical correction or concession. 2. Point to exact submitted evidence. 3. Explain the statistical or theoretical consequence. 4. Promise a camera-ready wording fix only if it does not add unsupported new claims.
Statistician-reviewer pushback patterns
| Pushback | What it signals | AISTATS-ready fix | |---|---|---| | "Assumption A3 seems strong" | The reviewer traced the proof chain | Point to where A3 is verified, weakened, or shown necessary; never dismiss it as standard without a citation | | "The experiments violate the theorem conditions" | Theory-experiment mismatch spotted | Identify which conclusions survive misspecification and cite the robustness simulation that shows it | | "Observed rates do not match the bound" | The reviewer compared empirical slopes against theory | Reference the log-log plot, or explain the constant-dominated regime at the tested sample sizes | | "Comparison with the classical statistical method is missing" | Statistics-literature gap | Anchor to the appendix comparison, or concede and scope a camera-ready clarification |
Response micro-example
Reviewer objection: the minimax claim hides its dependence on dimension d. Reply skeleton:
1. Concede that the d-dependence appears only in the appendix constant. 2. Quote the exact constant from Theorem 2 so the reviewer need not search. 3. Note that the simulation at d = 100 in Figure 4 follows the predicted scaling. 4. Offer one camera-ready sentence making the dependence explicit in the main text.
Discussion-phase calibration
- One decision-critical point per reviewer beats exhaustive replies; AISTATS meta-reviewers
read for whether the central statistical objection was actually resolved.
- Never paste new theorem statements or fresh proofs into the discussion box; sketch the
argument and anchor it in submitted material only.
- Respond early in the window — AISTATS discussion periods are short and reviewers who reply
once rarely reply twice.
- Length and formatting norms vary by cycle; recheck the current discussion instructions
before sending anything.
Output format
[Priority issue] <reviewer concern>
[Decision dimension] correctness / novelty / statistical validity / clarity / reproducibility
[Draft response] <AISTATS-ready anonymous text>
[Evidence anchor] <paper/appendix/supplement item>
[Forbidden content removed] <links, identity leaks, new unsupported claims>
Read more
name: aistats-author-response description: Use when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload, anonymity requirements, statistician-reviewer pushback patterns, and decision-focused clarification strategy for theory-plus-experiments papers.
AISTATS Author Response
Use this after AISTATS reviews are released. Reopen the current OpenReview instructions and author-discussion policy before drafting because response mechanics are cycle-specific.
Triage
- Answer concerns that affect correctness, novelty, statistical validity, clarity,
reproducibility, or fit for AISTATS.
- Use existing submitted evidence: paper sections, appendices, supplementary material,
theorem statements, experiments, checklist entries, and code/data descriptions.
- Keep the reply anonymous. Do not reveal institution, authorship, grants, private URLs, or
repository ownership.
- Treat discussion as clarification, not revision. Do not depend on uploading a revised paper
or new supplement unless current instructions explicitly allow it.
- If current rules prohibit links, do not use URLs in the discussion. AISTATS 2026
author-reviewer discussion was text-only and links were not allowed.
- Correct factual errors first, then address requests for missing comparisons, uncertainty
estimates, proofs, or hyperparameters.
Drafting pattern
1. State the decision-critical correction or concession. 2. Point to exact submitted evidence. 3. Explain the statistical or theoretical consequence. 4. Promise a camera-ready wording fix only if it does not add unsupported new claims.
Statistician-reviewer pushback patterns
| Pushback | What it signals | AISTATS-ready fix | |---|---|---| | "Assumption A3 seems strong" | The reviewer traced the proof chain | Point to where A3 is verified, weakened, or shown necessary; never dismiss it as standard without a citation | | "The experiments violate the theorem conditions" | Theory-experiment mismatch spotted | Identify which conclusions survive misspecification and cite the robustness simulation that shows it | | "Observed rates do not match the bound" | The reviewer compared empirical slopes against theory | Reference the log-log plot, or explain the constant-dominated regime at the tested sample sizes | | "Comparison with the classical statistical method is missing" | Statistics-literature gap | Anchor to the appendix comparison, or concede and scope a camera-ready clarification |
Response micro-example
Reviewer objection: the minimax claim hides its dependence on dimension d. Reply skeleton:
1. Concede that the d-dependence appears only in the appendix constant. 2. Quote the exact constant from Theorem 2 so the reviewer need not search. 3. Note that the simulation at d = 100 in Figure 4 follows the predicted scaling. 4. Offer one camera-ready sentence making the dependence explicit in the main text.
Discussion-phase calibration
- One decision-critical point per reviewer beats exhaustive replies; AISTATS meta-reviewers
read for whether the central statistical objection was actually resolved.
- Never paste new theorem statements or fresh proofs into the discussion box; sketch the
argument and anchor it in submitted material only.
- Respond early in the window — AISTATS discussion periods are short and reviewers who reply
once rarely reply twice.
- Length and formatting norms vary by cycle; recheck the current discussion instructions
before sending anything.
Output format
[Priority issue] <reviewer concern> [Decision dimension] correctness / novelty / statistical validity / clarity / reproducibility [Draft response] <AISTATS-ready anonymous text> [Evidence anchor] <paper/appendix/supplement item> [Forbidden content removed] <links, identity leaks, new unsupported claims>
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Other skills on awesome-journal-skills.
- /aaai-artifact-evaluation
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.
Open skill - /aaai-author-response
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
Open skill - /aaai-camera-ready
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
Open skill - /aaai-experiments
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
Open skill - /aaai-related-work
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
Open skill - /aaai-reproducibility
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
Open skill

