aejpol-referee-strategy
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.
Install / Use
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-referee-strategyInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of aejpol-referee-strategy
aejpol-referee-strategy scores 85/100 on our quality scale, 2680th of 4,702 Development & Engineering skills we index.
Its SKILL.md is 4.9 KB long, well organised into 9 sections with 1 code example: a solid amount of guidance for an agent.
With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so aejpol-referee-strategy is actively maintained.
- Our last check on 2026-11-05 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
aejpol-referee-strategy compared with similar skills
All 4 of these similar skills score higher than aejpol-referee-strategy; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| aejpol-referee-strategy (this skill)by brycewang-stanford | 85 | 1.2k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install aejpol-referee-strategy?
- Run
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aejpol-referee-strategy. The install tabs above show the steps for each supported agent. - Which AI agents does aejpol-referee-strategy work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is aejpol-referee-strategy safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is aejpol-referee-strategy still maintained?
- The repository was last updated about 2 months ago, so aejpol-referee-strategy is actively maintained.
Skill content
View source on GitHubname: aejpol-referee-strategy description: 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.
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:
- Is it a policy paper of broad interest? (the
aejpol-topic-selectiontest) — a clean estimate with no policy lever or welfare reading invites a "better suited to a field journal / AEJ: Applied" rejection. - Is the causal claim credible? (the
aejpol-identificationtest) — staggered TWFE, asserted parallel trends, a weak instrument, or an over-generalized RDD are the usual kill shots. - Does the welfare/policy reading follow? (the
aejpol-theory-modeltest) — a hand-waved "this is welfare-improving" or a sufficient-statistic formula whose assumptions are violated. - Is it robust and reproducible? (the
aejpol-robustness/aejpol-replication-packagetests).
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
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
