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

Jae Rebuttal

ASecurity

Use when planning revisions and drafting the point-by-point response for a Journal of Accounting and Economics (JAE) revise-and-resubmit — prioritizing the editor's identification and contribution concerns, satisfying economics-trained reviewers with new tests, and noting that resubmissions carry no submission fee.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jae Rebuttal?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jae-rebuttal
description: Use when planning revisions and drafting the point-by-point response for a Journal of Accounting and Economics (JAE) revise-and-resubmit — prioritizing the editor's identification and contribution concerns, satisfying economics-trained reviewers with new tests, and noting that resubmissions carry no submission fee.
---

# R&R Revision & Response for JAE (jae-rebuttal)

## When to trigger

- You received a JAE revise-and-resubmit and must plan the revision
- Reviewers demand additional identification, mechanism, or robustness tests
- You need to write the point-by-point response letter
- You are unsure how to reconcile conflicting reviewer requests

## Revise before you write the letter

Do the empirical and theoretical work **first**; the response letter documents revisions already made, not promises. At JAE the binding hierarchy is: the **Editor's letter first** (the contribution framing and the identification that must hold), then each **reviewer** point. Where the editor and a reviewer conflict, follow the editor and explain the resolution courteously.

## Prioritize what JAE referees care about

Because the decision rests on **economic mechanism and identification**, allocate effort accordingly:

- **Identification challenges**: add the natural experiment, instrument, placebo, or pre-trend evidence the referee wants; if a clean design is impossible, bound the bias and argue robustness honestly.
- **Mechanism**: add cross-sectional partitions showing the effect concentrates where the economic friction is severe — often the single most persuasive response.
- **Alternative explanations**: test them empirically rather than dismissing them in prose.
- **Measurement**: re-run with alternative proxies (accruals, conservatism, information-asymmetry measures) to show results are not proxy-driven.

## Writing the point-by-point response

- Reproduce **each comment verbatim**, then give your response and point to the exact revised text, table, or new analysis (with page/table numbers).
- Be **specific and evidence-based**; show the new result rather than asserting robustness.
- Be **respectful and concise** — economics referees value directness; do not argue past a fair point, and concede gracefully when the referee is right.
- Summarize the major changes in a **cover letter to the editor** up front.

## Practical notes

- **Resubmissions carry no submission fee** at JAE (the USD 650 fee applies only to unsolicited new manuscripts) — revise thoroughly rather than rushing.
- Keep the manuscript **double-anonymized**; do not unmask authorship in the response or new acknowledgments.
- Track changes or a marked-up copy if the editor requests it; keep the clean version submission-ready.

## Checklist

- [ ] Revisions completed *before* drafting the response
- [ ] Editor's framing/identification concerns addressed first
- [ ] Every reviewer comment reproduced and answered with specific pointers
- [ ] New identification / mechanism / robustness tests added where demanded
- [ ] Alternative explanations tested empirically
- [ ] Conflicts resolved in the editor's favor, explained politely
- [ ] Anonymization preserved; clean and marked copies prepared

## Anti-patterns

- **Promising changes** instead of making them.
- **Arguing with the referee** rather than addressing the concern.
- **Cosmetic robustness** that does not engage the identification challenge.
- **Ignoring the editor's letter** while answering reviewers.
- **Unmasking authorship** in the response or new acknowledgments.

## Output format

```
【Editor priorities addressed】identification / contribution framing ...
【Per-reviewer responses】comment → revision → pointer (page/table)
【New analyses added】design / mechanism partition / robustness
【Conflicts resolved】editor-favored, explained
【Cover letter summary】major changes
【Status】ready to resubmit (no fee) / pending tests
```

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 →