Agent Skills
› brycewang-stanford/Awesome-Journal-Skills
› jms-rebuttal
jms-rebuttal
GitHub专为JMS R&R回复信设计，指导如何撰写尊重、逐点且完整的反驳信。核心在于向处理编辑证明理论贡献清晰及严谨性达标，涵盖结构搭建、争议处理、冲突协调及多轮次跟进策略，确保满足JMS的高标准学术对话要求。
Trigger Scenarios
收到JMS修改重投（R&R）决定并需起草回复信
审稿人意见矛盾或要求削弱论文，需优雅反驳
需重新明确理论贡献以回应‘贡献不清晰’的质疑
进入第二轮及以上修改，需展示决定性进展
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-rebuttal -g -y
SKILL.md
Frontmatter
{
"name": "jms-rebuttal",
"description": "Use when drafting the response-to-reviewers and revision for a Journal of Management Studies (JMS) R&R — turning a developmental, often multi-round decision letter into a point-by-point response that satisfies the handling editor. Drafts the rebuttal; it does not re-plan the review reading (jms-review-process) or rebuild the theory from scratch (jms-theory-development)."
}
Rebuttal Strategy (jms-rebuttal)
When to trigger
- A JMS R&R (major or minor) has arrived and you are drafting the response letter
- Reviewers disagree and you must decide whom to follow without alienating the other
- A reviewer demands a change that would weaken the paper and you need to push back gracefully
- The contribution must be re-sharpened in response to "the theoretical contribution is unclear"
- You are entering round 2+ and need to show the editor decisive progress
The JMS rebuttal bar
JMS review is developmental and multi-round, so the response letter is itself a piece of scholarship: it must be respectful, point-by-point, and complete, and it must convince the handling editor (not just placate reviewers) that the contribution is now clear and the rigor demands are met. The most consequential thread is almost always the theoretical contribution — center your response there, then handle method/analysis/framing/writing.
Structure the response letter
- Opening to the editor. Thank the editor and reviewers; state the overall change — how the contribution and paper have improved — in a short paragraph. Signal that you took the development seriously.
- Point-by-point, comment-by-comment. Reproduce each comment verbatim, then respond. For each: (a) what you changed, (b) where (section/page/table number in the revision), (c) the brief reasoning. Quote the new text where it helps.
- Where you disagree. Disagree only when you must, with evidence and theory — never with attitude. Offer a compromise (a clarification, a bounded claim, an added robustness check or quote) rather than a flat refusal.
- Reviewer conflicts. When reviewers contradict each other, surface it explicitly and explain the path you took, deferring to the editor's framing.
Handling the signature JMS asks
| Reviewer ask | Strong response |
|---|---|
| "Contribution to theory is unclear" | Re-state the one-sentence contribution up front; show the revised intro/discussion; do not just add citations |
| "This is description, not theory" (qual) | Strengthen the data-structure → model abstraction; add propositions; do not bolt on hypotheses |
| "Endogeneity / CMB unaddressed" (quant) | Add the identification strategy or robustness; report it; state residual limits honestly |
| "Mechanism is asserted, not shown" | Add mediation evidence or richer process tracing; tie it back to the theorised mechanism |
| "Out of scope / wrong conversation" | Re-anchor positioning in a JMS conversation; or concede if truly mis-fit |
Round-2+ discipline
By later rounds the editor is watching for responsiveness and convergence. Make every prior promise visibly kept; flag anything you could not do and why; avoid reopening settled points. A change log mapping comment → action → location speeds the editor's check.
Checklist
- Every comment addressed individually; none silently skipped
- Each response states what changed, where (section/page/exhibit), and why
- The theoretical contribution is re-centered and visibly strengthened
- Disagreements are evidence-based, respectful, and offer a compromise
- Reviewer conflicts surfaced for the editor, not silently resolved
- Qualitative asks answered in the qualitative idiom (no bolted-on hypotheses)
- Tone is collegial and developmental throughout; a change log aids the editor
Anti-patterns
- Defensive or dismissive tone — fatal in a developmental culture
- Cosmetic compliance — claiming a change without actually making it (editors check)
- Citation-stuffing the contribution instead of re-articulating it
- Adding hypotheses to a qualitative paper because a reviewer used quant language
- Silently siding with one reviewer against another without telling the editor
- Reopening settled points in later rounds, signalling non-convergence
Output format
【Decision】R&R major / minor (round N)
【Editor headline】one-paragraph overall improvement statement
【Contribution re-center】revised one-sentence contribution + where shown
【Point-by-point】comment → change → location (section/page/exhibit) → reasoning
【Disagreements】point · evidence · compromise offered
【Conflicts surfaced】… (deferred to editor)
【Change log】comment → action → location
【Next step】resubmit via ScholarOne; if rejected, jms-topic-selection to reframe
Version History
- 1839142 Current 2026-07-05 13:48
