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

Jpe Referee Strategy

ASecurity

Use when running a pre-submission pre-mortem on a Journal of Political Economy (JPE) manuscript to anticipate the price-theory, general-equilibrium, and identification objections a Chicago referee will raise. Builds the threat list and pre-empts it; it does not write the R&R response (see jpe-rebuttal).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgoreact

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jpe Referee Strategy?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jpe-referee-strategy
description: Use when running a pre-submission pre-mortem on a Journal of Political Economy (JPE) manuscript to anticipate the price-theory, general-equilibrium, and identification objections a Chicago referee will raise. Builds the threat list and pre-empts it; it does not write the R&R response (see jpe-rebuttal).
---

# Referee Strategy & Pre-Mortem (jpe-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 economics referee

## How JPE referees read

JPE referees read the paper as an **economic argument** and probe its internal consistency. The prototypical Chicago referee asks: does this respect optimization, prices, incentives, and equilibrium? They are unimpressed by a clean coefficient with no economic meaning, and they will name the alternative mechanism or the GE force you ignored. Anticipating these is worth more than any extra robustness table. The process is selective and demanding, and JPE-specific: a **co-editor** (the board is led by Esteban Rossi-Hansberg and weighted toward University of Chicago faculty) runs the desk screen; review is **single-blind** (referees know who you are); and the **$250 / $125 submission fee is non-refundable even on a desk reject**. A single unanswered first-order objection sinks a paper before that paid-for gate.

## The objection taxonomy (pre-empt each in the text)

1. **"Where is the economics?"** — A reduced-form result with no model/mechanism. *Pre-empt:* `jpe-theory-model` — state the mechanism and the prediction it tests.
2. **"This ignores general equilibrium."** — A partial effect that nets out when prices/quantities adjust. *Pre-empt:* address GE feedback; bound or sign the equilibrium effect.
3. **"Your mechanism vs. the obvious alternative."** — A rival economic story produces the same sign. *Pre-empt:* `jpe-robustness` — a discriminating test.
4. **"Selection / endogeneity."** — Treatment or sample is endogenous. *Pre-empt:* `jpe-identification` — defend the assumption, show falsification.
5. **"What identifies the parameter?"** (structural) — *Pre-empt:* explicit "what identifies what" + untargeted-moment validation.
6. **"So what?"** — credible but unimportant. *Pre-empt:* `jpe-topic-selection` — state the portable lesson and magnitude.
7. **"Internal inconsistency."** — the model's assumption contradicts the empirical setting, or two claims conflict. *Pre-empt:* a consistency pass across model, data, and conclusion.

## Pre-mortem procedure

- Write the referee report you fear, in their voice, listing the three objections most likely to trigger a reject.
- For each, decide: fixable in text now (do it), needs new analysis (do it or scope it), or a genuine limitation (state it honestly and bound its damage).
- Identify the **one** first-order objection that would sink the paper and make sure the manuscript answers it before a referee has to ask.
- Suggesting referees / handling COIs: name scholars who know the literature (and the right field, if you are targeting JPE Micro or JPE Macro) and would engage fairly; note conflicts honestly — the single-blind portal will flag obvious co-author/advisor ties.

## Checklist

- [ ] "Where is the economics?" answered by an explicit mechanism/model
- [ ] General-equilibrium feedback addressed or bounded
- [ ] The leading rival mechanism named and tested against
- [ ] Selection/endogeneity threat defended with a falsification test
- [ ] (Structural) parameter identification made transparent
- [ ] Importance / portable lesson stated, not assumed
- [ ] Model–data–conclusion consistency pass done
- [ ] The single most dangerous objection identified and pre-empted in the text

## Anti-patterns

- Submitting with an obvious GE or selection objection unaddressed, hoping the referee misses it (and forfeiting a non-refundable fee at the desk screen)
- Trying to anonymize for a single-blind journal, or suggesting referees with a conflict the portal will catch
- A robustness section that never tests the *leading* rival mechanism
- Assuming importance instead of demonstrating it
- Hiding a known limitation rather than bounding it (referees find it anyway)
- Treating the pre-mortem as optional polish rather than the cheapest way to avoid a reject

## Output format

```
【Feared report】the 3 objections most likely to trigger reject
【First-order threat】the single objection that would sink it
【Pre-empt plan】per objection: fix-in-text / new-analysis / state-as-limitation
【GE + rival-mechanism status】addressed? [y/n]
【Consistency pass】model–data–conclusion coherent? [y/n]
【Next】jpe-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 →