/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
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aeri-rebuttal --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
/aeri-rebuttal
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
aeri-rebuttal.SKILL.mdname: aeri-rebuttal
description: 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).
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`](../aeri-robustness/SKILL.md)). 5. **Finalize the replication package.** A conditional accept means the AEA Data Editor check is imminent; have the deposit ready ([`aeri-replication-package`](../aeri-replication-package/SKILL.md)). 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`](../aeri-topic-selection/SKILL.md) 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
Read more
name: aeri-rebuttal description: 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).
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`](../aeri-robustness/SKILL.md)). 5. **Finalize the replication package.** A conditional accept means the AEA Data Editor check is imminent; have the deposit ready ([`aeri-replication-package`](../aeri-replication-package/SKILL.md)). 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`](../aeri-topic-selection/SKILL.md) 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
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

