Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Qje Referee Strategy

ASecurity

Use when war-gaming likely referee objections for a Quarterly Journal of Economics (QJE) manuscript before submitting, to close gaps pre-emptively given QJE's ~2-week desk screen and ~1-4% acceptance. Anticipates referee reports; it does not write the post-decision response letter (see qje-rebuttal).

1,052 stars
0 votes
0 copies
2 views
Added 6/6/2026
ai-agentsrustgo

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill qje-referee-strategy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Qje Referee Strategy?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Qje Referee Strategy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-qje-referee-strategy/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-qje-referee-strategy)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: qje-referee-strategy
description: Use when war-gaming likely referee objections for a Quarterly Journal of Economics (QJE) manuscript before submitting, to close gaps pre-emptively given QJE's ~2-week desk screen and ~1-4% acceptance. Anticipates referee reports; it does not write the post-decision response letter (see qje-rebuttal).
---

# Referee Strategy (qje-referee-strategy)

## When to trigger

- The paper is nearly submission-ready and you want to stress-test it adversarially
- You suspect a specific weakness a referee will seize on
- You are choosing what to put in the body vs. the appendix to forestall objections
- You want to draft suggested/excluded referees and a strategic cover note

## The QJE refereeing reality

QJE is **the fastest top-5 journal at desk** — its five Harvard-based Editors desk-decide in roughly **two weeks** and desk-reject a clear majority (commonly cited around 60%+), with an unconditional acceptance rate of only **~1-4%**. Review is **double-blind**, so you cannot tailor to a known referee; you must satisfy *the toughest plausible expert*. Two consequences: (1) the paper has to survive a fast, skim-level editor screen before any referee sees it, so the big idea and clean identification must be visible up front; (2) for papers that survive, QJE grants few rounds with demanding referees, so you usually get *one* substantive shot. Anticipate the report you would write if you were the toughest expert in your subfield, and answer it in advance.

## Map the three referee archetypes

| Referee type        | What they attack                                          | Pre-empt by...                                            |
|---------------------|-----------------------------------------------------------|-----------------------------------------------------------|
| The identification hawk | The exogeneity claim; pre-trends; exclusion restriction | Falsification + placebo evidence in the body (see qje-identification) |
| The "so what?" skeptic  | Generality; whether the answer matters to all of econ   | A crisp broad-lesson + magnitude benchmarking (qje-topic-selection) |
| The mechanism doubter   | Whether the proposed channel is the real one            | A testable prediction confirmed in data (qje-theory-model) |

## War-gaming protocol

1. **Pass the desk screen first.** Before refereeing even starts, ask: in two pages, is the big question and the clean source of variation obvious? If not, the editor desk-rejects in ~2 weeks regardless of how good the appendix is.
2. **Write the hostile report.** In 5–8 bullets, list the strongest objections a top expert would raise. Be ruthless; this is cheaper now than after a rejection.
3. **Triage.** For each: is it a *fundamental* threat (kills the claim) or a *robustness* request (adds a table)? Fundamentals must be resolved before submission, not deferred to R&R.
4. **Locate the answer.** For each objection, point to where in the paper it is already answered. If nowhere, add it (body for fundamentals, appendix for robustness).
5. **Decide the framing.** Pre-empt the biggest objection explicitly in the text ("A natural concern is X; we address it in three ways ..."). Showing you saw it coming builds referee trust.

## Cover-letter / referee suggestions

- Suggest referees who are expert and fair; avoid close collaborators and advisors (conflicts), consistent with the AEA disclosure norms QJE follows.
- Note genuine conflicts to exclude, briefly and professionally.
- Keep any cover note short: the question, the design, the headline result, and fit for a general-interest journal — the editor reading it has ~2 weeks and many submissions.

## Checklist

- [ ] The two-page editor-skim test passes (big idea + clean variation visible early)
- [ ] A written hostile report exists with the 5–8 strongest objections
- [ ] Every fundamental threat is resolved in the body before submission
- [ ] Each robustness objection has a pre-emptive appendix answer
- [ ] The single biggest concern is addressed explicitly and early in the text
- [ ] Magnitudes benchmarked so the "so what?" referee is satisfied
- [ ] Suggested referees are expert, fair, and conflict-free

## Anti-patterns

- Submitting with a known fundamental hole, hoping referees miss it (the editor desk-screen catches a lot first)
- Deferring identification fixes to "future R&R" — at ~1-4% acceptance, QJE may not grant the round
- Ignoring the obvious objection rather than naming and answering it
- Suggesting collaborators/friends as referees (signals naivety or conflict)
- A long, defensive cover letter that argues instead of stating the contribution

## Output format

```
【Desk-screen test】big idea + variation visible in 2 pages? [Y/N]
【Hostile report】[5–8 strongest objections]
【Fundamentals】[threats that must be fixed pre-submission] — status each
【Robustness asks】[appendix answers] — status each
【Pre-empted in text】the biggest concern, addressed where: ...
【Referee suggestions】[expert, fair, conflict-free]
【Next step】qje-submission
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →