AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Aejmac Referee Strategy

skill-brycewang-stanford-awesome-journal-skills-aejmac-referee-strategy · by brycewang-stanford

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).

No reviews yet
0 installs
29 views
0.0% view→install

Install

$ agentstack add skill-brycewang-stanford-awesome-journal-skills-aejmac-referee-strategy

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-brycewang-stanford-awesome-journal-skills-aejmac-referee-strategy)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Aejmac Referee Strategy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.