Skip to content
cccskills
FreePublished on GitHub

aeri-rebuttal

Use when responding to an American Economic Review: Insights (AER: Insights) conditional-accept decision — addressing the editor's letter within the short window, usually without a second referee round. Drafts a concise, decisive response and revision plan; it does not redo the analysis (see aeri-robustness / aeri-identification).

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

Run score Not tested

See how to install

Files included (1)

  • SKILL.md4.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Conditional-Accept Response (aeri-rebuttal)

When to trigger

  • A conditional accept letter arrived from AER: Insights
  • You must return a revised short paper within the conditional window (~8 weeks)
  • The letter lists changes the editor expects, and you need a tight response
  • You received a reject and are deciding what to do (see end of this skill)

What an AER: Insights conditional accept means (检索于 2026-06;以官网为准)

AER: Insights does not issue traditional revise-and-resubmit decisions. A conditional accept means the editor expects to publish the paper subject to the changes in the decision letter; authors typically get about 8 weeks to return the revision, which is normally not sent back to referees. The conditions are meant to be achievable without substantial uncertainty — this is finishing, not relitigating. So the response is short, complete, and non-defensive: do what the letter asks, document it crisply, and do not reopen settled issues.

How to respond

  1. Treat the letter as a punch list. Map every requested change to a concrete edit; nothing is "optional."
  2. Comply, don't argue. Since there is no referee round to win, push back only where a request is genuinely infeasible or would be wrong — and then offer an alternative that satisfies the underlying concern.
  3. Keep the response letter short. One numbered item per request: the request, what you did, where in the paper (section/exhibit/line). Editors of a short journal reward concision.
  4. Protect the caps. Edits must keep the paper within 7,000 − 200×(#exhibits) words and ≤5 exhibits — added text or an added exhibit can re-breach the gate. Move new material to the Supplemental Appendix (aeri-robustness).
  5. Finalize the replication package. A conditional accept means the AEA Data Editor check is imminent; have the deposit ready (aeri-replication-package).
  6. Keep the single insight intact. Do not let requested additions turn the short paper into a sprawling one.

Response-letter structure

Dear Editor [name],
Thank you for the conditional acceptance. We have addressed each point below.

1. [Editor request, quoted/paraphrased]
   Response: [what we did], now in [Section/Exhibit/Appendix].
2. ...
We confirm the manuscript remains within the word and exhibit limits, and the
replication package is prepared for the AEA Data Editor.

Checklist

  • Every item in the decision letter mapped to a concrete edit
  • Response letter is concise, point-by-point, non-defensive
  • Any pushback is rare, justified, and offers an alternative
  • Revised paper still within word + exhibit caps; new material to the appendix
  • The single insight is unchanged; no scope creep
  • Replication package finalized for the AEA Data Editor check
  • Returned within the conditional window (~8 weeks)

Anti-patterns

  • Arguing with the editor as if this were a multi-round R&R
  • Adding text/exhibits that re-breach the word or exhibit cap
  • A long, defensive response letter for a short paper
  • Letting requested additions sprawl the paper beyond its single insight
  • Leaving the data/code deposit until after the response is sent

If it was a REJECT instead

There is no path to relitigate a reject at AER: Insights. Reframe quickly: the short paper is often a strong fit for an AEJ field journal, or can be expanded into a fuller AER-style paper if the idea supports more. Route back to aeri-topic-selection to decide which.

Output format

【Decision】conditional accept / reject
【Punch list】each request → edit → location
【Caps after revision】words = __ (≤ 7000 − 200×__?), exhibits __/5
【Insight intact】single idea unchanged? [Y/N]
【Data editor】replication package ready? [Y/N]
【If reject】next venue (AEJ / expand to AER) → aeri-topic-selection
【Next step】submit revision within ~8-week window

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