brycewang-stanford/Auto-Empirical-Research-Skills / skills/11-James-Traina-compound-science/skills/submission-guide
submission-guide
VerifiedThis skill covers academic journal submission, referee responses, and revision management. Use when the user is preparing a manuscript for submission, formatting for a specific journal, responding to referees, or managing revisions. Triggers on "submit", "referee", "revision", "R&R", "response letter", "journal", "formatting", "submission", "resubmit", "cover letter", "referee report", "revise and resubmit".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.0 KB |
| references/journal-profiles.md | markdown | 9.4 KB |
| references/referee-response-templates.md | markdown | 6.7 KB |
| references/referee-tactics.md | markdown | 10.1 KB |
references/referee-response-templates.md
View on GitHub# Referee Response Templates and Revision Routing
## Response Architecture
Every referee response consists of three documents:
1. **Cover letter** (1 page): Summary of changes, gratitude, overall framing
2. **Point-by-point response** (bulk): Each comment addressed in order
3. **Marked-up manuscript** (optional but recommended): Changes highlighted
---
## Comment Classification
Before drafting, classify each referee comment:
| Type | Definition | Response strategy |
|------|-----------|-------------------|
| **Factual error** | Referee misread the paper | Politely correct with specific page reference |
| **Legitimate concern** | Valid critique requiring real change | Concede, describe change, quote revised text |
| **Scope extension** | Wants a different paper | Explain what this paper does; add robustness if reasonable |
| **Identification challenge** | Questions causal validity | Treat seriously; add robustness, clarify assumptions |
| **Robustness request** | Wants additional specification | Add if reasonable; justify omission if not |
| **Presentation issue** | Clarity, notation, organization | Fix it; brief acknowledgment |
| **Citation request** | "You should cite X" | Add if relevant; briefly explain if not |
NEVER argue that a legitimate concern is wrong without making a change -- revise first, then explain.
ALWAYS implement at least a partial accommodation of each concern, even if you disagree.
---
## Point-by-Point Format
```
**Referee 1, Comment 3:** [Quote the exact comment here]
**Response:** [Your response -- one of three forms:]
Form A (Accept): We thank the referee for this observation. We have revised [Section X]
to address this concern. Specifically, [describe change]. The revised text now reads:
> "[Quote the new text verbatim]"
Form B (Partial accept): We agree with the spirit of this comment. We have added [X]
but do not [Y] because [brief justification focused on the paper's scope].
The revised text reads: > "[Quote new text]"
Form C (Polite decline): We appreciate the referee's suggestion. As the paper focuses
on [specific question], adding [Y] would take us [beyond scope / require different data].
We have clarified this in [Section X]: > "[Quote clarifying text]"
```
---
## Identification Challenges: High-Stakes Responses
When a referee challenges the identification strategy, use this framework:
1. **Do not concede identification failure unless the critique is decisive.** An incomplete argument is not an invalid one.
2. **Restate the identification assumption clearly and precisely** -- often this alone resolves the concern.
3. **Add targeted robustness**: if the concern is "X could confound your result", add a specification that controls for X or a falsification test.
4. **Invoke the relevant literature**: if the exclusion restriction is standard in the field (e.g., distance-to-college IV for education), cite the papers that defend it.
### Standard robustness additions for identification challenges
| Challenge | Standard robustness addition |
|-----------|------------------------------|
| "Parallel trends may be violated" | Pre-trends test + Rambachan-Roth (2023) sensitivity; add covariates to DiD; Sant'Anna-Zhao (2020) doubly robust |
| "Instrument is weak" | Report Montiel Olea-Pflueger effective F; Anderson-Rubin CI; LIML vs. 2SLS comparison |
| "Instrument is not excludable" | Conley-Hansen-Rossi plausibly exogenous bounds; partial identification with Roy-Tchetgen bounds |
| "Omitted variable bias" | Oster (2019) bounds (delta and Rmax); coefficient stability table across specifications |
| "Selection into sample" | Heckman selection correction; Lee (2009) bounds; attrition test |
| "Bunching at cutoff" | Formal McCrary/rddensity test; donut RDD |
| "Wrong functional form" | Nonparametric local polynomial; Robinson partial linear model |
---
## Journal-Specific Tone Calibration
| Journal | Appropriate tone | Key emphasis |
|---------|-----------------|--------------|
| **AER/ECMA/JPE/QJE** | Formal, thorough, no shortcuts | Every comment gets a full response; no dismissals |
| **REStud/JME/JPubE** | Professional, can be more direct | Depth on methodological comments |
| **JHR/AEJ-Applied** | Practical, policy-focused framing | Emphasize empirical validity and policy implications |
| **Field journals** | Collegial, can acknowledge scope tradeoffs | Reviewer likely knows the data; acknowledge domain expertise |
| **Top theory** (ECMA/TE) | Formal, precise, mathematical | Proofs must be complete; no handwaving |
---
## Cover Letter Template
```
Dear Editor [Name],
We are pleased to submit the revised version of "[Paper Title]" (MS #XXXX).
We thank the editor and referees for their careful reading and constructive suggestions,
which have substantially improved the paper.
[2-3 sentences summarizing the main changes:]
The most significant revisions include: (i) [Main change addressing Referee 1's central concern];
(ii) [Main change addressing Referee 2's concern]; and (iii) [any other major revision].
[If identification was challenged:] We have strengthened the identification section by [X],
which directly addresses the concerns raised by Referee [N] about [specific issue].
The paper is [shorter/longer] by approximately [N] pages. We believe these revisions
fully address the referees' concerns and hope you find the revised manuscript suitable
for publication.
We look forward to your decision.
Sincerely,
[Authors]
```
---
## Tracking Revisions Across Rounds
Organize revision correspondence as:
```
correspondence/
round1/
referee1_report.md
referee2_report.md
response_letter.md
changes_summary.md # What changed and where (for round 2 reference)
round2/
...
```
Use `changes_summary.md` to track:
- Which referee comments led to which changes
- What robustness was added vs. what was declined
- Page/section numbers of all changes
This becomes the foundation for a round-2 response letter that can say "as discussed in our previous response, [X] is addressed in [Section Y]."
---
## Revision Routing
Classify each referee comment before responding:
| Classification | Meaning | Route to |
|---------------|---------|----------|
| **NEW ANALYSIS** | Requires new estimation, robustness check, or data work | `/workflows:work` then update response |
| **CLARIFICATION** | Requires text edits to explain existing results | Direct text revision |
| **DISAGREE** | Author disagrees with referee's premise | Construct argument with evidence |
| **MINOR** | Quick fix (typo, formatting, citation) | Fix immediately |
Process: classify all comments first, then batch by type. NEW ANALYSIS items go through the full work->review cycle. CLARIFICATION and DISAGREE items are drafted in the response letter. MINOR items are fixed inline.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |