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

Jole Rebuttal

ASecurity

Use when drafting a response letter to a Journal of Labor Economics (JOLE) revise-and-resubmit — addressing single-blind labor referees point by point under the journal's word economy. Strategy and structure; it does not run new estimations for you.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jole Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jole-rebuttal
description: Use when drafting a response letter to a Journal of Labor Economics (JOLE) revise-and-resubmit — addressing single-blind labor referees point by point under the journal's word economy. Strategy and structure; it does not run new estimations for you.
---

# R&R Rebuttal Strategy (jole-rebuttal)

## When to trigger

- A JOLE decision letter arrives with referee reports and an invitation to revise
- You have new results and need to convert them into a referee-by-referee response
- Referees disagree with each other and you must reconcile their demands
- You are unsure how much to concede versus defend on a labor-identification critique

## The JOLE rebuttal context

JOLE review is **single-blind**: referees know who you are, and you are responding to named-but-anonymous labor economists. The revised manuscript stays **non-anonymized** (title page with all co-authors), and it must still respect the **~20,000-word** soft cap with each full-page table/figure counting as **500 words** — so you cannot answer every comment by bolting on five new exhibits; some responses belong in the letter or a tightly bounded online appendix rather than the body. References remain **Chicago author-date**. Because the submission fee already gated the first decision, treat the R&R as the scarce, valuable channel it is.

## Structure of the response

1. **Cover note to the editor** — summarize the 2–3 most important changes and how they address the editor's framing. Keep it short; labor editors triage many revisions.
2. **Per-referee sections** — restate each comment in your own words, then answer. Use a stable numbering (R1.1, R1.2 …) so the referee can map your replies to their report.
3. **Point-by-point format** — for each: (a) quote/paraphrase the comment, (b) what you changed, (c) where in the revised manuscript (section/table/figure/page), (d) the result if it moved.
4. **Reconcile conflicts** — when two referees disagree, state both views, explain your choice, and show it does not undermine the other referee's concern.

## Substantive moves for labor papers

- **Identification challenges** (the most common): if a referee doubts parallel trends, the instrument's exclusion, or AKM limited-mobility bias, answer with diagnostics, not rhetoric — event-study leads, falsification, weak-IV-robust CIs, leave-out / bias-corrected firm effects (see jole-identification-strategy, jole-data-analysis).
- **Robustness demands**: add the check, report it, and say plainly whether the headline holds; do not hide a fragile result.
- **"Is this new for labor?"**: tighten the contribution against the labor literature (see jole-contribution-framing, jole-literature-positioning) rather than adding scope.
- **Magnitude / interpretation**: if asked, recompute and report the effect with units; do not over-claim.
- **Word economy**: relocate long defenses to a bounded online appendix; keep the body within the limit.

## Checklist

- [ ] Cover note states the 2–3 headline changes for the editor
- [ ] Every referee comment has a numbered, point-by-point reply
- [ ] Each reply names the exact location of the change in the revised manuscript
- [ ] Identification critiques answered with diagnostics, not assertion
- [ ] Conflicts between referees reconciled explicitly
- [ ] Revised manuscript still **non-anonymized** and within the ~20,000-word economy
- [ ] No new over-claiming introduced by the revisions

## Anti-patterns

- A defensive letter that argues without changing the manuscript
- Re-anonymizing the manuscript (JOLE is single-blind)
- Adding so many new full-page exhibits that the paper blows the word cap
- Conceding a fatal identification flaw with words instead of evidence
- Ignoring one referee because another disagrees
- Silently dropping a result a referee questioned instead of addressing it

## Output format

```
【Editor note】2–3 headline changes summarized? [Y/N]
【Coverage】every comment answered point-by-point with locations? [Y/N]
【Identification replies】answered with diagnostics? [Y/N]
【Conflicts】reconciled explicitly? [Y/N]
【Compliance】non-anonymized + within ~20,000 words? [Y/N]
【Next step】jole-submission re-check before resubmitting
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — packages for the robustness checks referees request
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — official JOLE URLs and verification status

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 →