/aejmic-referee-strategy
Use when anticipating referee objections or calibrating review expectations for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript before submission. Pre-empts the objections theory referees raise and reads the editorial process; it does not draft the response
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill aejmic-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
/aejmic-referee-strategy
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when anticipating referee objections or calibrating review expectations for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript before submission. Pre-empts the objections theory referees raise and reads the editorial process; it does not draft the response
SKILL.md
aejmic-referee-strategy.SKILL.mdname: aejmic-referee-strategy
description: Use when anticipating referee objections or calibrating review expectations for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript before submission. Pre-empts the objections theory referees raise and reads the editorial process; it does not draft the response letter (see aejmic-rebuttal).
Referee Strategy (aejmic-referee-strategy)
When to trigger
- Before submission, to stress-test the paper against the objections experts will raise
- Deciding whether the contribution clears the desk-reject bar
- Choosing JEL codes / framing that route the paper to the right co-editor
- Unsure what the AEJ: Micro review process looks like
The AEJ: Micro process (检索于 2026-06;以官网为准)
- AEJ: Micro uses **single-blind** review via the AEA submission system: the referee sees the author, but referees are anonymous to authors. There is no anonymization burden — reputation is visible, so the paper must stand on rigor.
- There is a **submission fee** (AEA member $200 high-income / $100 middle / $0 low; nonmember higher — 检索于 2026-06,volatile), and JEL classification per AEA practice helps route the paper to the right co-editor and expert referees.
- Decisions run the usual ladder: desk reject → reject after review → R&R (minor/major) → accept. Theory referees verify proofs; a flawed or non-tight proof is a common reject reason.
- Re-confirm fee, timelines, and co-editor list on the official AEA AEJ: Micro page (see `resources/official-source-map.md`).
Objections AEJ: Micro referees actually raise — and the pre-emption
| Likely objection | Pre-empt it by (skill) | |---|---| | "The result is a knife-edge artifact of assumption A." | Name the load-bearing assumption; show necessity / a counterexample on failure (`aejmic-identification`) | | "This is too specialized / maximal-generality for AEJ: Micro." | Re-frame the broad-interest message; cut generality that hides it (`aejmic-topic-selection`, `aejmic-theory-model`) | | "How does this differ from [closest result]?" | State the theorem-relative delta in one sentence (`aejmic-literature-positioning`) | | "Does it survive [a continuum / asymmetry / perturbation]?" | Provide the earned extension or a clean negative result (`aejmic-robustness`) | | "A step in the proof is asserted, not shown." | Complete the lemma scaffolding; self-contained proofs (`aejmic-replication-package`) | | "The model is overloaded; the mechanism is invisible." | Reduce to the minimal environment; lead with intuition (`aejmic-theory-model`, `aejmic-writing-style`) | | "This is an empirical paper, not theory." | Either restore the theoretical contribution or redirect to AEJ: Applied (`aejmic-topic-selection`) | | (Applied) "Identification / inference is shaky; asterisks used." | Branch B/C identification; SEs not asterisks (`aejmic-identification`, `aejmic-tables-figures`) |
Checklist
- [ ] Listed the three most likely referee objections for *this* paper and mapped each to a fix
- [ ] The load-bearing assumption is named and defended before submission
- [ ] The theorem-relative delta is crisp (one sentence)
- [ ] The broad-interest message is explicit (not specialist-only)
- [ ] Every proof step a referee will check is complete
- [ ] JEL codes chosen to route to the right co-editor (single-blind: no anonymization needed)
- [ ] Decided the venue is right (not actually an AEJ: Applied paper)
Anti-patterns
- Submitting without anticipating the single most obvious expert objection
- Relying on generality to impress when the audience-fit objection is the real risk
- Leaving a checkable proof gap for a referee to find
- Mis-routing via vague JEL codes so a non-expert co-editor handles it
- Assuming anonymity protects a thin result — single-blind means the referee knows whose work it is
Worked vignette (illustrative)
Before submitting a matching paper, the author lists likely objections: (1) "rides on substitutability" → already pre-empted in `aejmic-identification` with a counterexample; (2) "how does it differ from the deferred-acceptance literature?" → one-sentence delta ready; (3) "is the existence proof complete?" → lemma scaffolding done. The remaining risk is audience fit, so the intro is rewritten to foreground the broad market-design message rather than the technical condition. JEL codes C78/D47 route it to a market-design co-editor.
Output format
【Top 3 likely objections】[...] → 【Fix / owning skill】[...]
【Load-bearing assumption defended】[Y/N]
【Delta crisp】[Y/N] 【Broad-interest message explicit】[Y/N]
【Proof gaps closed】[Y/N]
【Routing】JEL codes [...] (single-blind — no anonymization)
【Venue confirmed】AEJ: Micro (not AEJ: Applied)? [Y/N]
【Next step】aejmic-submission
Supplementary resources
- [`../../resources/README.md`](../../resources/README.md) — links to the shared reviewer-objection checklist (applied subset)
Read more
name: aejmic-referee-strategy description: Use when anticipating referee objections or calibrating review expectations for an American Economic Journal: Microeconomics (AEJ: Micro) manuscript before submission. Pre-empts the objections theory referees raise and reads the editorial process; it does not draft the response letter (see aejmic-rebuttal).
Referee Strategy (aejmic-referee-strategy)
When to trigger
- Before submission, to stress-test the paper against the objections experts will raise
- Deciding whether the contribution clears the desk-reject bar
- Choosing JEL codes / framing that route the paper to the right co-editor
- Unsure what the AEJ: Micro review process looks like
The AEJ: Micro process (检索于 2026-06;以官网为准)
- AEJ: Micro uses **single-blind** review via the AEA submission system: the referee sees the author, but referees are anonymous to authors. There is no anonymization burden — reputation is visible, so the paper must stand on rigor.
- There is a **submission fee** (AEA member $200 high-income / $100 middle / $0 low; nonmember higher — 检索于 2026-06,volatile), and JEL classification per AEA practice helps route the paper to the right co-editor and expert referees.
- Decisions run the usual ladder: desk reject → reject after review → R&R (minor/major) → accept. Theory referees verify proofs; a flawed or non-tight proof is a common reject reason.
- Re-confirm fee, timelines, and co-editor list on the official AEA AEJ: Micro page (see `resources/official-source-map.md`).
Objections AEJ: Micro referees actually raise — and the pre-emption
| Likely objection | Pre-empt it by (skill) | |---|---| | "The result is a knife-edge artifact of assumption A." | Name the load-bearing assumption; show necessity / a counterexample on failure (`aejmic-identification`) | | "This is too specialized / maximal-generality for AEJ: Micro." | Re-frame the broad-interest message; cut generality that hides it (`aejmic-topic-selection`, `aejmic-theory-model`) | | "How does this differ from [closest result]?" | State the theorem-relative delta in one sentence (`aejmic-literature-positioning`) | | "Does it survive [a continuum / asymmetry / perturbation]?" | Provide the earned extension or a clean negative result (`aejmic-robustness`) | | "A step in the proof is asserted, not shown." | Complete the lemma scaffolding; self-contained proofs (`aejmic-replication-package`) | | "The model is overloaded; the mechanism is invisible." | Reduce to the minimal environment; lead with intuition (`aejmic-theory-model`, `aejmic-writing-style`) | | "This is an empirical paper, not theory." | Either restore the theoretical contribution or redirect to AEJ: Applied (`aejmic-topic-selection`) | | (Applied) "Identification / inference is shaky; asterisks used." | Branch B/C identification; SEs not asterisks (`aejmic-identification`, `aejmic-tables-figures`) |
Checklist
- [ ] Listed the three most likely referee objections for *this* paper and mapped each to a fix
- [ ] The load-bearing assumption is named and defended before submission
- [ ] The theorem-relative delta is crisp (one sentence)
- [ ] The broad-interest message is explicit (not specialist-only)
- [ ] Every proof step a referee will check is complete
- [ ] JEL codes chosen to route to the right co-editor (single-blind: no anonymization needed)
- [ ] Decided the venue is right (not actually an AEJ: Applied paper)
Anti-patterns
- Submitting without anticipating the single most obvious expert objection
- Relying on generality to impress when the audience-fit objection is the real risk
- Leaving a checkable proof gap for a referee to find
- Mis-routing via vague JEL codes so a non-expert co-editor handles it
- Assuming anonymity protects a thin result — single-blind means the referee knows whose work it is
Worked vignette (illustrative)
Before submitting a matching paper, the author lists likely objections: (1) "rides on substitutability" → already pre-empted in `aejmic-identification` with a counterexample; (2) "how does it differ from the deferred-acceptance literature?" → one-sentence delta ready; (3) "is the existence proof complete?" → lemma scaffolding done. The remaining risk is audience fit, so the intro is rewritten to foreground the broad market-design message rather than the technical condition. JEL codes C78/D47 route it to a market-design co-editor.
Output format
【Top 3 likely objections】[...] → 【Fix / owning skill】[...] 【Load-bearing assumption defended】[Y/N] 【Delta crisp】[Y/N] 【Broad-interest message explicit】[Y/N] 【Proof gaps closed】[Y/N] 【Routing】JEL codes [...] (single-blind — no anonymization) 【Venue confirmed】AEJ: Micro (not AEJ: Applied)? [Y/N] 【Next step】aejmic-submission
Supplementary resources
- [`../../resources/README.md`](../../resources/README.md) — links to the shared reviewer-objection checklist (applied subset)
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

