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

Rje Rebuttal

ASecurity

Use when responding to a revise-and-resubmit from The RAND Journal of Economics (RJE) — answering the two anonymous referees and the handling Editor on an industrial-organization manuscript while respecting the hard page caps and RJE house style. Strategy for the response letter; it does not rewrite the article.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Rje Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: rje-rebuttal
description: Use when responding to a revise-and-resubmit from The RAND Journal of Economics (RJE) — answering the two anonymous referees and the handling Editor on an industrial-organization manuscript while respecting the hard page caps and RJE house style. Strategy for the response letter; it does not rewrite the article.
---

# R&R Rebuttal Strategy (rje-rebuttal)

## When to trigger

- You received an R&R from the RJE handling Editor with two referee reports
- You must reconcile conflicting referee demands without blowing the 50-page cap
- You are drafting the point-by-point response letter

## RJE-specific rebuttal posture

RJE decisions come from a **handling Editor** synthesizing **two anonymous referees** after an upfront screen, so the Editor's letter is the binding document — prioritize the points the Editor flags, then address each referee. Two structural constraints shape the response:

- **Page caps are hard.** Main text **<=40 pp**, total **<=50 pp**, double-spaced. You usually cannot satisfy every referee by adding material. Move new robustness, derivations, and counterfactuals into the **appendix** (counts toward the <=10-page appendix+references budget) or, sparingly, into **supporting information** — but note RJE **discourages supporting information** and may decline it, so do not park core results there.
- **House style persists in the revision.** Keep author-date cites with **no page numbers**, references with **no issue numbers**, unnumbered subsections, and the usage rules (because/as not *since*; whereas/although not *while*; **"article"** not *"paper"*). A revision that drifts off style reads as careless.

## IO-specific responses referees expect

- **Identification / specification.** For structural work: justify functional form, instruments for price (cost shifters, BLP/Gandhi–Houde), and the estimator; show the result survives a reasonable alternative specification. For reduced-form: defend the policy/merger variation and report modern-DID or weak-IV-robust diagnostics.
- **Counterfactual and welfare claims.** IO referees probe out-of-sample counterfactuals hard — bound them and state the maintained assumptions.
- **Market definition and external validity.** Say what the estimated market teaches beyond itself.

## Response-letter mechanics

- One numbered point per referee comment; quote the comment, then the change, then a page/section pointer.
- Lead each reply with the **action taken**, not justification.
- Where you decline, give a crisp reason and an alternative check — never silence.
- Keep a **changes summary** at the top for the Editor, organized around the Editor's priorities.

## Anti-patterns

- Expanding the main text past 40 pp to appease referees instead of using the appendix
- Dumping core results into discouraged supporting information
- Letting the revision drift off RJE house style
- Treating both referees as equal when the Editor signaled which points are decisive

## Output format

```
【Editor's priorities】[ranked list from the decision letter]
【Referee 1 / Referee 2】[major asks each]
【Page budget】main __/40, total __/50 — within cap? [Y/N]
【Where new material goes】main / appendix / (supporting info, justified)
【Style preserved】author-date no page nos., house usage? [Y/N]
【Next step】rje-submission re-preflight before resubmission
```

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 →