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 Rebuttal

ASecurity

Use when a Quarterly Journal of Economics (QJE) decision letter arrives (R&R or reject-and-resubmit) and a response strategy and letter are needed. Structures the revision and response; it does not redo the analysis (route to the relevant qje-* skill for that).

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Qje Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: qje-rebuttal
description: Use when a Quarterly Journal of Economics (QJE) decision letter arrives (R&R or reject-and-resubmit) and a response strategy and letter are needed. Structures the revision and response; it does not redo the analysis (route to the relevant qje-* skill for that).
---

# Rebuttal & Revision (qje-rebuttal)

## When to trigger

- A QJE decision letter arrived: revise-and-resubmit, or a conditional/major revision
- You have referee reports and need a response strategy
- You are unsure how to prioritize conflicting referee demands
- The revised manuscript exists and you need to draft the response letter

## QJE reality: few rounds, high stakes

At an unconditional acceptance rate of only **~1-4%**, an R&R from one of QJE's five Harvard-based Editors is a rare and valuable signal — treat it as a near-final opportunity and address everything substantive in this round rather than negotiating across many. The **handling Editor's letter is the contract**: at QJE a single Editor (not a co-editor + AE layer) owns the decision, so that letter tells you which referee points are binding and which are optional. Read it first and let it set priorities.

## Triage protocol

1. **Decode the Editor.** The Editor's letter ranks the issues. A point the Editor underscores is binding; a point only one referee raised and the Editor ignored is lower priority (but still answer it).
2. **Classify every comment.** For each referee point, tag it: *fundamental* (must add analysis), *clarification* (rewrite/explain), or *disagreement* (you will push back, politely, with evidence).
3. **Sequence the work.** Do the analysis first (route fundamentals to `qje-identification` / `qje-robustness` / `qje-theory-model`), update exhibits, *then* write the letter — never write the letter before the manuscript reflects the changes.
4. **Never pick a fight you can win with a robustness check.** If a check settles it, run the check; reserve disagreement for points where the referee is genuinely mistaken.

## Response-letter structure

- **Opening**: thank the Editor and referees; summarize the main changes in a short paragraph.
- **Point-by-point**: quote each comment, then respond. Each response = what you did + where in the revised paper it now appears (section/table/figure/page).
- **Disagreements**: state the referee's point fairly, then give the evidence-based reason you respectfully differ; offer a compromise (e.g., added to the appendix) where possible.
- **Tone**: gracious, concrete, never defensive. Show the referees made the paper better.
- **Change log**: optionally include a brief summary of all changes up front for the Editor's convenience.

## Checklist

- [ ] Editor's priorities decoded and used to rank responses
- [ ] Every referee comment classified (fundamental / clarification / disagreement)
- [ ] All fundamental requests resolved with actual new analysis, not promises
- [ ] Each response cites the exact location of the change in the revised paper
- [ ] Disagreements are evidence-based, fair, and offer a compromise
- [ ] Tone is gracious and concrete throughout
- [ ] Revised manuscript updated *before* the letter was written
- [ ] No new over-claiming introduced while answering reviewers

## Anti-patterns

- Writing the response letter before the manuscript actually reflects the changes
- Promising future work instead of doing the analysis this round (rounds are scarce at ~1-4% acceptance)
- Arguing with a referee where a quick robustness check would settle it
- Defensive or curt tone; treating reports as attacks rather than help
- Answering only the easy points and hand-waving the hard one the Editor flagged
- Vague responses ("we have addressed this") with no location in the paper

## Output format

```
【Decision】R&R / major / conditional
【Editor's binding points】[...]
【Comment classification】fundamental: [...] / clarification: [...] / disagreement: [...]
【Analysis routed to】qje-identification / qje-robustness / qje-theory-model (as needed)
【Letter status】point-by-point with locations? [Y/N]
【Tone check】gracious + concrete? [Y/N]
【Next step】resubmit the single PDF via Editorial Express (qje-submission for file checks)
```

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

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 →