SkillAgentSearch skills...

aeja-referee-strategy

Use when anticipating the objections a sophisticated American Economic Journal: Applied Economics (AEJ: Applied) referee will raise, so a manuscript pre-empts them before submission or addresses them in revision.

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeja-referee-strategy

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Supported Platforms

Universal

Tags

Our assessment of aeja-referee-strategy

aeja-referee-strategy scores 85/100 on our quality scale, 2674th of 4,702 Development & Engineering skills we index.

Its SKILL.md is 4.8 KB long, well organised into 8 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.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so aeja-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 found

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.

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.

aeja-referee-strategy compared with similar skills

All 4 of these similar skills score higher than aeja-referee-strategy; compare them before choosing.

SkillScoreStarsUpdatedFormat
aeja-referee-strategy (this skill)by brycewang-stanford851.2k2mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install aeja-referee-strategy?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill aeja-referee-strategy. The install tabs above show the steps for each supported agent.
Which AI agents does aeja-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 aeja-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 aeja-referee-strategy still maintained?
The repository was last updated about 2 months ago, so aeja-referee-strategy is actively maintained.

name: aeja-referee-strategy description: Use when anticipating the objections a sophisticated American Economic Journal: Applied Economics (AEJ: Applied) referee will raise, so a manuscript pre-empts them before submission or addresses them in revision. Plans the defense; it does not draft the response letter (aeja-rebuttal) or run the submission preflight (aeja-submission).

Referee Strategy (aeja-referee-strategy)

When to trigger

  • The paper is near submission and you want to stress-test it against the referees it will draw
  • You need to decide which robustness checks to run before submitting vs. hold in reserve
  • An R&R arrived and you must map referee concerns to concrete responses
  • You want to understand how AEJ: Applied's single-blind peer-review process shapes strategy

How AEJ: Applied review works (plan around it)

AEJ: Applied uses single-blind review through the AEA ScholarOne system: author identities are visible to referees, while referee identities remain anonymous to authors. An editor assigns the paper to a coeditor or handles it directly, and before a first R&R the handling coeditor consults a second coeditor. Referees here are identification-literate applied microeconomists; the modal report attacks the credibility of the design first, then magnitude/mechanism, then external validity. The editor weighs whether the contribution is novel and the design clears the bar. Plan to pre-empt the predictable objections in the paper itself, leaving the response letter for genuinely new asks.

The objection map (pre-empt in the paper)

| Referee objection (by design) | Pre-emption to build in now | |-------------------------------|-----------------------------| | "TWFE is biased under staggered timing" | heterogeneity-robust estimator + Bacon decomposition already in the paper | | "Parallel trends is not credible" | clean pre-trend leads + honest-DID sensitivity bound | | "Instrument is not excludable" | institutional + theoretical exclusion argument + falsification tests | | "RD jump is manipulation / bandwidth-driven" | density test + bandwidth sensitivity + donut | | "Effect is just selection / confounding" | Oster δ / coefficient-stability bounds | | "Local/ITT effect ≠ the policy-relevant effect" | explicit estimand + calibrated external-validity discussion | | "Inference too narrow (few clusters)" | wild-cluster bootstrap / randomization inference | | "Mechanism is a black box" | a test that distinguishes the proposed channel from rivals | | "Not reproducible" | the openICPSR package built and referenced (aeja-replication-package) |

Strategy craft

  1. War-game the design. For each identifying assumption, write the sentence a hostile referee would use; if you cannot answer it in one paragraph + one exhibit, that is a hole to fix before submission.
  2. Pre-empt, do not hide. Address the obvious weakness head-on in the text; referees punish papers that ignore the elephant.
  3. Sequence robustness. Put decisive checks in the main paper; hold secondary ones for the appendix/online appendix so the paper stays readable.
  4. Anticipate the external-validity ask. It is almost guaranteed for a local design — have the estimand and scope statement ready.
  5. Make reproducibility visible. A referee who sees a clean package is less inclined to suspect specification search.

The shared, venue-neutral objection catalog is in ../../resources/README.md (links to the empirical-methods hub) — walk it before drafting.

Checklist

  • [ ] Title/byline/front matter align with AEJ: Applied's single-blind process
  • [ ] Each identifying assumption has a written hostile-referee sentence and a one-paragraph+one-exhibit answer
  • [ ] The paper's biggest weakness is addressed in the text, not hidden
  • [ ] Decisive robustness in the main paper; secondary checks in the appendix
  • [ ] Estimand + external-validity scope stated to pre-empt the guaranteed ask
  • [ ] Reproducibility package referenced so specification-search suspicion is defused
  • [ ] Mechanism evidence distinguishes the proposed channel from rivals

Anti-patterns

  • Ignoring the obvious design weakness and hoping no referee notices
  • Writing self-citations or acknowledgments as if the venue required anonymous review
  • Dumping every robustness check into the main text so the paper becomes unreadable
  • No estimand statement, guaranteeing an external-validity round-trip
  • Treating the replication package as someone else's problem until acceptance

Output format

【Front matter】single-blind title/byline and disclosures ready? [Y/N]
【Objection map】per assumption: [objection → pre-emption in paper]
【Biggest weakness】addressed in text? [Y/N] — how: ___
【Robustness placement】main vs appendix split: ___
【External validity】estimand + scope stated? [Y/N]
【Reproducibility visible】package referenced? [Y/N]
【Next step】aeja-submission

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions