ecj-referee-strategy
Use when running a pre-submission pre-mortem on a The Economic Journal (EJ) manuscript to anticipate the broad-interest, identification, and mechanism objections a demanding general-interest referee will raise. Builds the threat list and pre-empts it; it does not write the R&R response (see ecj-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecj-referee-strategy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Referee Strategy & Pre-Mortem (ecj-referee-strategy) ## When to trigger - Identification, model, and robustness are in place and you want to harden the paper before submitting - You want to anticipate the report rather than react to it - You sense a likely objection but have not addressed it in the text - You are choosing how to frame the contribution to survive a demanding general-interest refe
What does the ecj-referee-strategy skill do?
Use when running a pre-submission pre-mortem on a The Economic Journal (EJ) manuscript to anticipate the broad-interest, identification, and mechanism objections a demanding general-interest referee will raise. Builds the threat list and pre-empts it; it does not write the R&R response (see ecj-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecj-referee-strategy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.