/aejmac-referee-strategy
Use when anticipating the objections referees and coeditors will raise on an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript, and calibrating desk-reject and revision odds, before submission. Pre-empts pushback and plans the review; it does not draft the
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aejmac-referee-strategy --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
/aejmac-referee-strategy
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when anticipating the objections referees and coeditors will raise on an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript, and calibrating desk-reject and revision odds, before submission. Pre-empts pushback and plans the review; it does not draft the
SKILL.md
aejmac-referee-strategy.SKILL.mdname: aejmac-referee-strategy
description: Use when anticipating the objections referees and coeditors will raise on an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript, and calibrating desk-reject and revision odds, before submission. Pre-empts pushback and plans the review; it does not draft the post-decision response letter (use aejmac-rebuttal).
Referee Strategy (aejmac-referee-strategy)
When to trigger
- The draft is near-complete and you want to find the holes a referee will exploit
- You are gauging desk-reject risk or whether the paper is "ready"
- You need to decide which robustness checks to run *before* submitting vs. hold in reserve
- You want to pre-empt the predictable macro objections in the paper itself
How AEJ: Macro review works (verified 2026-06; re-confirm on the official AEA pages)
- Managed by the **Editor** (Ayşegül Şahin, 检索于 2026-06;以官网为准) and **coeditors**; **single-blind** external peer review (the author is known to the referee; referees are anonymous to the author). Note this is **single-blind**, unlike some AEJs/economics venues that anonymize the author.
- **Desk rejection** is possible without referees; editorial decisions weigh the probability of meeting AEJ: Macro standards, **breadth of topic, and interest to the AEJ: Macro audience**.
- After conditional acceptance, the **AEA Data Editor** runs the reproducibility check before publication (see `aejmac-replication-package`).
The predictable macro objections (pre-empt each in the paper)
| Objection a macro referee raises | Where it lands | Pre-emption | |---|---|---| | "The identifying assumption is not defended" (Cholesky ordering, sign set, exclusion) | identification | Argue the assumption economically; show robustness to alternatives (`aejmac-identification`) | | "The shock is anticipated / endogenous" | identification | Show unpredictability from macro history; use narrative/high-frequency instruments | | "This is a Great-Moderation / pre-ZLB artifact" | robustness | Sample splits across the breaks, baseline shown alongside (`aejmac-robustness`) | | "Calibration is undisciplined / free parameters" | theory-model | Source every parameter; targeted + untargeted moments; sensitivity | | "The counterfactual ignores the Lucas critique" | theory-model | Argue policy-invariance of estimated parameters | | "SVAR and LP would disagree" | robustness | Run the cross-method check and show agreement | | "Set-identified results reported as a point" | identification / tables | Report the identified set / median-target with a band | | "Not broad enough for AEJ: Macro" | topic / positioning | Re-frame for general interest; name the audience (`aejmac-topic-selection`) | | "Results not reproducible" | replication | Build the openICPSR package early, incl. simulation code |
Calibrating the odds
- **Desk-reject risk is high when**: breadth is thin (a field-specialist paper), the contribution sentence is missing, or the headline quantity is buried. Fix with `aejmac-topic-selection` / `aejmac-literature-positioning` / `aejmac-writing-style` *before* submitting.
- **R&R is likely when** the question is broad and the result credible but the robustness/identification defense is incomplete — referees will ask for the checks. Pre-running the obvious ones shortens the cycle.
- **Hold-in-reserve strategy**: run the decisive robustness checks before submission; keep a second tier ready to deploy in the response letter rather than front-loading every table.
Suggesting referees & framing the cover
- Suggest referees who span the **theory and empirical** sides if the paper is a hybrid, so neither side is judged only by the other camp.
- The cover letter / framing should state the **broad-interest claim and the headline quantity** plainly — give the editor the breadth argument they need to send it out.
Checklist
- [ ] Each predictable macro objection above has a one-paragraph + one-exhibit answer in the paper
- [ ] Desk-reject risk assessed (breadth, contribution sentence, headline visibility)
- [ ] Decisive robustness/identification checks run before submission
- [ ] Second-tier checks identified to hold in reserve for the response
- [ ] Referee suggestions span the relevant theory/empirical communities
- [ ] Single-blind reviewed: nothing in the paper assumes anonymity of the author
Anti-patterns
- Submitting before the obvious adversarial robustness check is run
- Assuming double-blind anonymity (AEJ: Macro is single-blind)
- A paper a desk editor cannot pitch as broad-interest in one sentence
- Front-loading every conceivable robustness table, leaving nothing for the response
- Suggesting only referees from one camp for a hybrid paper
Output format
【Top 3 objections this paper invites】1) ... 2) ... 3) ...
【Pre-emption status】answered-in-paper / needs-work for each
【Desk-reject risk】low / medium / high + why
【Run-now vs. reserve checks】...
【Referee suggestions span】theory + empirical? [Y/N]
【Next step】aejmac-submission
Read more
name: aejmac-referee-strategy description: Use when anticipating the objections referees and coeditors will raise on an American Economic Journal: Macroeconomics (AEJ: Macro) manuscript, and calibrating desk-reject and revision odds, before submission. Pre-empts pushback and plans the review; it does not draft the post-decision response letter (use aejmac-rebuttal).
Referee Strategy (aejmac-referee-strategy)
When to trigger
- The draft is near-complete and you want to find the holes a referee will exploit
- You are gauging desk-reject risk or whether the paper is "ready"
- You need to decide which robustness checks to run *before* submitting vs. hold in reserve
- You want to pre-empt the predictable macro objections in the paper itself
How AEJ: Macro review works (verified 2026-06; re-confirm on the official AEA pages)
- Managed by the **Editor** (Ayşegül Şahin, 检索于 2026-06;以官网为准) and **coeditors**; **single-blind** external peer review (the author is known to the referee; referees are anonymous to the author). Note this is **single-blind**, unlike some AEJs/economics venues that anonymize the author.
- **Desk rejection** is possible without referees; editorial decisions weigh the probability of meeting AEJ: Macro standards, **breadth of topic, and interest to the AEJ: Macro audience**.
- After conditional acceptance, the **AEA Data Editor** runs the reproducibility check before publication (see `aejmac-replication-package`).
The predictable macro objections (pre-empt each in the paper)
| Objection a macro referee raises | Where it lands | Pre-emption | |---|---|---| | "The identifying assumption is not defended" (Cholesky ordering, sign set, exclusion) | identification | Argue the assumption economically; show robustness to alternatives (`aejmac-identification`) | | "The shock is anticipated / endogenous" | identification | Show unpredictability from macro history; use narrative/high-frequency instruments | | "This is a Great-Moderation / pre-ZLB artifact" | robustness | Sample splits across the breaks, baseline shown alongside (`aejmac-robustness`) | | "Calibration is undisciplined / free parameters" | theory-model | Source every parameter; targeted + untargeted moments; sensitivity | | "The counterfactual ignores the Lucas critique" | theory-model | Argue policy-invariance of estimated parameters | | "SVAR and LP would disagree" | robustness | Run the cross-method check and show agreement | | "Set-identified results reported as a point" | identification / tables | Report the identified set / median-target with a band | | "Not broad enough for AEJ: Macro" | topic / positioning | Re-frame for general interest; name the audience (`aejmac-topic-selection`) | | "Results not reproducible" | replication | Build the openICPSR package early, incl. simulation code |
Calibrating the odds
- **Desk-reject risk is high when**: breadth is thin (a field-specialist paper), the contribution sentence is missing, or the headline quantity is buried. Fix with `aejmac-topic-selection` / `aejmac-literature-positioning` / `aejmac-writing-style` *before* submitting.
- **R&R is likely when** the question is broad and the result credible but the robustness/identification defense is incomplete — referees will ask for the checks. Pre-running the obvious ones shortens the cycle.
- **Hold-in-reserve strategy**: run the decisive robustness checks before submission; keep a second tier ready to deploy in the response letter rather than front-loading every table.
Suggesting referees & framing the cover
- Suggest referees who span the **theory and empirical** sides if the paper is a hybrid, so neither side is judged only by the other camp.
- The cover letter / framing should state the **broad-interest claim and the headline quantity** plainly — give the editor the breadth argument they need to send it out.
Checklist
- [ ] Each predictable macro objection above has a one-paragraph + one-exhibit answer in the paper
- [ ] Desk-reject risk assessed (breadth, contribution sentence, headline visibility)
- [ ] Decisive robustness/identification checks run before submission
- [ ] Second-tier checks identified to hold in reserve for the response
- [ ] Referee suggestions span the relevant theory/empirical communities
- [ ] Single-blind reviewed: nothing in the paper assumes anonymity of the author
Anti-patterns
- Submitting before the obvious adversarial robustness check is run
- Assuming double-blind anonymity (AEJ: Macro is single-blind)
- A paper a desk editor cannot pitch as broad-interest in one sentence
- Front-loading every conceivable robustness table, leaving nothing for the response
- Suggesting only referees from one camp for a hybrid paper
Output format
【Top 3 objections this paper invites】1) ... 2) ... 3) ... 【Pre-emption status】answered-in-paper / needs-work for each 【Desk-reject risk】low / medium / high + why 【Run-now vs. reserve checks】... 【Referee suggestions span】theory + empirical? [Y/N] 【Next step】aejmac-submission
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

