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

Jf Referee Strategy

ASecurity

Use when anticipating referee objections and selecting suggested/opposed reviewers before or during a The Journal of Finance (JF) submission. Plans for review; it does not write the rebuttal (use jf-rebuttal).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jf Referee Strategy?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jf-referee-strategy
description: Use when anticipating referee objections and selecting suggested/opposed reviewers before or during a The Journal of Finance (JF) submission. Plans for review; it does not write the rebuttal (use jf-rebuttal).
---

# Referee Strategy (jf-referee-strategy)

## When to trigger

- Before submitting: anticipating the objections a JF referee will raise
- The portal asks for suggested / opposed reviewers
- A conflict of interest among editors, AEs, or referees needs flagging

## How JF review works (plan around it)

JF, the AFA flagship, runs a demanding multi-round process: a handling **editor** (currently **Antoinette Schoar (MIT)**, with co-editors and 50+ Associate Editors — verify the masthead) screens first, then assigns typically **2–3 referees**. The reality is severe — **~33–45% desk-rejected, ~5% accepted** (afajof.org editor reports, accessed 2026-05-30). Most papers die at desk review, so the first job is surviving the editor, not the referees.

### JF-specific channels
- A **cover letter is normally unnecessary** at JF — use one **only** to flag a conflict of interest (referees/AEs/editors who should be excluded) or to request a code-sharing exemption. Do not pad it (see `jf-submission`).
- Suggested/opposed reviewers, if the portal asks, should be specific and justified.

## Anticipating objections (pre-empt in the paper)

| Likely referee objection            | Where to neutralize it                          |
|-------------------------------------|-------------------------------------------------|
| "This is already in [paper]"        | Contribution paragraph (`jf-literature-positioning`) |
| "Identification is not credible"    | Design section + IA tests (`jf-identification`) |
| "Just data mining / multiple testing" | Disclosed search + adjusted thresholds (`jf-robustness`) |
| "Not general-interest enough"       | Reframe for the broad AFA reader (`jf-topic-selection`) |

## Checklist

- [ ] Top 3 likely referee objections listed and pre-empted in the manuscript
- [ ] Desk-reject risk assessed (general interest, identification, fit)
- [ ] Opposed reviewers (genuine COI) noted only if the portal asks
- [ ] Cover letter used only for COI or code-exemption — otherwise omitted
- [ ] Suggested reviewers are specific and defensible

## Anti-patterns

- Writing a long cover letter JF did not ask for
- Listing opposed reviewers without a real conflict (reads as gaming)
- Ignoring desk-reject risk and over-optimizing for referees
- Leaving the obvious "already known" objection unaddressed

## Output format

```
【Top objections + where pre-empted】...
【Desk-reject risk】low / med / high — why
【COI to flag in cover letter?】yes / no
【Suggested/opposed reviewers (if asked)】...
【Next step】jf-submission → (after decision) jf-rebuttal
```

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 →