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

Jfe Referee Strategy

ASecurity

Use when anticipating and pre-empting the objections a Journal of Financial Economics (JFE) referee will raise — endogeneity, fragility, multiple testing, alternative explanations. Builds a defense plan before or during review; it does not draft the post-R&R response letter (jfe-rebuttal).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jfe Referee Strategy?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jfe-referee-strategy
description: Use when anticipating and pre-empting the objections a Journal of Financial Economics (JFE) referee will raise — endogeneity, fragility, multiple testing, alternative explanations. Builds a defense plan before or during review; it does not draft the post-R&R response letter (jfe-rebuttal).
---

# Referee Strategy (jfe-referee-strategy)

## When to trigger

- Before submission, to find the objections a referee will raise first
- After a first round, to plan which battles to fight and which to concede
- When you suspect a specific weakness (a contested instrument, a thin subsample)
- When the paper is strong but you have not "refereed it yourself"

## How JFE referees behave

JFE referees are methodologically demanding experts who expect every plausible alternative explanation to be ruled out and every result to survive thorough robustness. They read the Internet Appendix (appended to the main file). They are quicker to reject for an undefended identification or a fragile result than for a modest contribution. The winning strategy is to referee your own paper first and answer the hard questions in the text.

Two JFE process facts matter for strategy: (1) the journal aims at fast turnaround and **refunds the whole US$850 fee if a decision takes more than 120 days**, which keeps editors moving — so a clean, referee-yourself-first submission is rewarded; (2) refereeing for JFE earns **submission rights** that discount your own future fees, which is why the referee pool is engaged and exacting. Your handling editor is a subfield specialist under Editor-in-Chief Toni M. Whited's small co-editor team; the editor's signal, not the loudest referee, decides the paper.

## Pre-empt the predictable objections

### Identification objections
- "X is endogenous to Y." -> Have the shock/IV/RDD defense and a placebo in the text.
- "Staggered DID is biased." -> Show a heterogeneity-robust estimator and Bacon decomposition.
- "Your instrument violates exclusion." -> Theory + institutional + falsification defense.

### Inference objections
- "Standard errors are understated." -> Cluster correctly; show two-way / wild bootstrap.
- "This is a multiple-testing artifact." -> Adjust and report; show out-of-sample.

### Robustness objections
- "Does it survive an alternative measure / sample / specification?" -> It is already in the body or IA.
- "An alternative story explains this." -> A distinguishing test exists for each rival story.

### Contribution objections
- "Isn't this already known?" -> The positioning text answers it directly.

## Plan the campaign (after reports arrive)

- Sort each comment into: (a) substantive, must address with new analysis; (b) clarification, address in text; (c) genuine disagreement, push back respectfully with evidence.
- Identify the editor's emphasis — the comments the editor flags are the ones that decide the paper.
- Decide where new tests go (main text vs. Internet Appendix) before writing the response.
- Never pick a fight you cannot win with evidence; concede gracefully where the referee is right.

## Checklist

- [ ] You have written, in advance, the three hardest referee questions
- [ ] Each has an answer in the manuscript or Internet Appendix
- [ ] Identification, inference, robustness, and contribution objections each pre-empted
- [ ] Suggested/opposed referees considered within system rules
- [ ] After reports: each comment triaged (substantive / clarification / disagreement)
- [ ] Editor's emphasis identified and prioritized

## Anti-patterns

- Submitting without having refereed your own paper
- Ignoring the obvious endogeneity question and hoping it slips through
- Treating every referee comment as equally important and missing the editor's signal
- Arguing with a referee without new evidence
- Conceding a point that guts the contribution when a defense exists

## Output format

```
【Top-3 anticipated objections】[...]
【Pre-empted in text/IA】[...] | 【Still exposed】[...]
【Editor's emphasis】(if reports received)
【Comment triage】substantive[...] clarify[...] disagree[...]
【New tests location】main / IA
【Next】jfe-rebuttal (to draft the response)
```

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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', ...

693161 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 →