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

Aejpol Referee Strategy

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

Use when anticipating how AEJ: Economic Policy referees and editors will read a manuscript, before submission or before an R&R, to pre-empt the objections that sink policy-evaluation papers. Maps likely pushback to fixes and calibrates expectations; it does not write the response letter (see aejpol-rebuttal) or fix the identification.

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

Install

$ agentstack add skill-brycewang-stanford-awesome-journal-skills-aejpol-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-aejpol-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 Aejpol Referee Strategy? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Referee Strategy — Reading the Manuscript as an AEJ: Policy Referee (aejpol-referee-strategy)

When to trigger

  • Before submitting: you want to find the objections a referee will raise first
  • Deciding whether the paper is ready or needs another round of work
  • Calibrating expectations about the AEA single-blind process and timeline
  • Triaging which weaknesses to fix vs. disclose before submission

How AEJ: Policy referees read

AEJ: Policy reviews are single-blind through the AEA system (referees see the authors; authors do not see referees), refereed by economists who expect both credible causal evidence and a policy-relevant welfare reading. A referee typically tests four things in order; a paper dies at the first one it fails:

  1. Is it a policy paper of broad interest? (the aejpol-topic-selection test) — a clean estimate with no policy lever or welfare reading invites a "better suited to a field journal / AEJ: Applied" rejection.
  2. Is the causal claim credible? (the aejpol-identification test) — staggered TWFE, asserted parallel trends, a weak instrument, or an over-generalized RDD are the usual kill shots.
  3. Does the welfare/policy reading follow? (the aejpol-theory-model test) — a hand-waved "this is welfare-improving" or a sufficient-statistic formula whose assumptions are violated.
  4. Is it robust and reproducible? (the aejpol-robustness / aejpol-replication-package tests).

Pre-empting the predictable objections

| Likely referee objection | Pre-emption to build before submitting | |---|---| | "This isn't a policy paper / not broad-interest" | Lead with the policy question + welfare stake; state the cost-benefit reading in the abstract | | "Staggered TWFE is biased here" | Heterogeneity-robust DID + Bacon decomposition + flat leads, in the main paper | | "Parallel trends is assumed, not shown" | Event-study leads + honest-DID bounds | | "Exclusion restriction is not credible" | Institutional + theoretical defense + falsification | | "The welfare claim is hand-waved" | Explicit sufficient-statistic / MVPF / cost-benefit derivation | | "External validity is unclear" | Heterogeneity by setting; explicit scope of the policy lesson | | "Effect is significant but tiny / not policy-relevant" | Benchmark the magnitude against budget / status quo | | "Not reproducible / data unavailable" | AEA-compliant package + restricted-data access path ready |

Calibrating expectations

  • AEA review is thorough; expect a small number of detailed referee reports and an editor letter. Plan for an R&R rather than a clean accept.
  • Decide in advance which objections you will fix (identification, robustness) vs. bound and disclose (external validity, a calibrated welfare parameter). Disclosing a limitation precisely is stronger than hiding it.

Checklist

  • [ ] The "is this a policy paper?" objection is pre-empted on page one
  • [ ] The single most likely identification objection has a main-text answer (not relegated to the appendix)
  • [ ] The welfare reading is derived, not asserted
  • [ ] Each predictable objection is mapped to an exhibit or paragraph that answers it
  • [ ] Limitations you cannot fix are bounded and disclosed precisely
  • [ ] Reproducibility is ready before the editor asks

Anti-patterns

  • Submitting hoping referees will not notice the staggered-TWFE / pre-trends problem
  • Hiding a known limitation instead of bounding and disclosing it
  • A welfare claim with no derivation, trusting the referee to grant it
  • Putting the decisive robustness check only in an online appendix the referee may skip
  • Mis-calibrating to a generic-journal process and ignoring AEA single-blind norms

Worked vignette (illustrative)

An education-policy paper using a funding-formula RDD anticipates three objections: (1) "local estimate only" → states the estimand and argues the threshold population is the marginal policy population; (2) "manipulation at the cutoff" → CJM density test + donut RDD; (3) "no welfare reading" → translates the test-score effect into a cost-per-standard-deviation and compares to class-size policies. All three answers are in the main text, so no referee can raise them as fatal.

Output format

【Broad-interest verdict】would a referee call this a policy paper? [Y/N + fix]
【Top identification objection】+ main-text pre-emption
【Welfare-reading objection】derived or hand-waved? + fix
【Objection→answer map】[objection → exhibit/paragraph]
【Fix vs. disclose list】what to fix now / what to bound and disclose
【Next step】aejpol-submission (if ready) or back to the named skill

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.