Skip to content
cccskills
FreePublished on GitHub

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 strategy for theory-plus-experiments papers.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md3.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

PushbackWhat it signalsAISTATS-ready fix
"Assumption A3 seems strong"The reviewer traced the proof chainPoint 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 spottedIdentify 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 theoryReference 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 gapAnchor 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>

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

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.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

See all skills by brycewang-stanford

Report a problem with this skill