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

Jme Rebuttal

ASecurity

Use after a Journal of Monetary Economics (JME) revise-and-resubmit to plan the response letter and revision — given JME's distinctive "up or out" rule (the resubmission ends in acceptance or rejection, no second R&R) and the ~50% publication-likelihood signal an R&R carries.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jme-rebuttal --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jme Rebuttal?

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

Security grade badge for Jme Rebuttal
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jme-rebuttal/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jme-rebuttal)

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

Download with Pro
Files
SKILL.md
---
name: jme-rebuttal
description: Use after a Journal of Monetary Economics (JME) revise-and-resubmit to plan the response letter and revision — given JME's distinctive "up or out" rule (the resubmission ends in acceptance or rejection, no second R&R) and the ~50% publication-likelihood signal an R&R carries.
---

# R&R Rebuttal Strategy (jme-rebuttal)

## When to trigger

- A JME decision letter invited a revise-and-resubmit
- You are drafting the response-to-referees letter and the revision plan
- You need to prioritize which referee points are make-or-break

## What an R&R means at JME

An R&R at JME is a **strong signal** — editors invite a resubmission **only when they judge at least a 50% likelihood of ultimate publication.** But it is **not** a green light to iterate forever. The defining rule is **"up or out": the resubmission must result in acceptance or rejection — there is no second round of revise-and-resubmit.** Your one revision has to **fully resolve** the editors' and (typically two) referees' concerns. Treat every substantive comment as decision-relevant; an unaddressed major point can flip the outcome to reject because there is no further round to fix it.

Because review is **single anonymized** (referees know who you are), keep the tone collegial and precise, and address each referee directly.

## Building the response

- **Triage**: separate **make-or-break** concerns (identification of the shock, the information-effect critique, a disputed SVAR ordering, a DSGE identification or fit problem) from cosmetic ones. The make-or-break set must be **fully** resolved, not deflected.
- **Point-by-point**: reproduce each comment, state what you changed, and point to the exact revised table/figure/section (and the online supplement where robustness lives).
- **New analysis goes to the supplement**: added robustness, alternative identification, and derivations belong in the **online supplementary appendix** (exempt from the 40-page cap), with the headline result kept in the ≤10 main exhibits.
- **Disagree carefully**: if you decline a request, give a substantive macro/econometric reason — but under "up or out," concede rather than fight on anything the editor flagged.
- **Mind the cap**: a revision can balloon; keep the main text under **40 pages** and **≤10 exhibits**, moving everything else online.

## Checklist

- [ ] Every referee/editor point answered point-by-point with a pointer to the revision
- [ ] All **make-or-break** identification/model concerns **fully** resolved (no deflection)
- [ ] New robustness placed in the online supplement; body still ≤40 pages / ≤10 exhibits
- [ ] Tone collegial and direct (single-blind: referees know you)
- [ ] No fee due on resubmission (JME charges none for revisions)
- [ ] You understand this is the **only** revision — accept or reject follows

## Anti-patterns

- Treating the R&R as one of several rounds (it is **up or out** — no second R&R)
- Deflecting a major identification critique with a footnote
- Letting the revised paper exceed 40 pages / 10 exhibits instead of using the supplement
- A defensive, combative tone toward referees who can see your identity

## Output format

```
【Decision】R&R (⇒ ~50% likelihood; next decision is accept or reject)
【Make-or-break points】[list — must be fully resolved]
【Minor points】[list]
【New analysis location】online supplement (body ≤40pp / ≤10 exhibits)
【Tone】collegial, point-by-point
【Next step】submit the single "up or out" revision
```

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 →