Agent skill · Data & Analytics

jmgmt-rebuttal

Use when drafting the response-to-reviewers for a Journal of Management (JOM) R&R — the point-by-point letter, the editor-first revision strategy, handling masked-reviewer conflicts, and staying within the 50-page limit across rounds. Drafts and structures the response; it does not run new analyses (jmgmt-data-analysis) or rebuild the theory (jmgmt-theory-development).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmgmt-rebuttal --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Journal-of-Management-Skills/skills/jmgmt-rebuttal/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Rebuttal & Response Letter (jmgmt-rebuttal) ## When to trigger - A JOM R&R arrived and you need a response-letter strategy - Reviewers disagree and you must resolve the conflict for the action editor - You are tempted to argue with a reviewer rather than revise - The revision risks pushing the paper over the **50-page** limit - You need to show, not just assert, that you addressed the theoretical-contribution and method concerns ## The JOM rebuttal stance JOM's review is **developmental and masked**, so the response letter is read by the action editor and the (anonymous) reviewers as evidence of whether the paper can become publishable. Two principles govern everything: **the editor's priorities come first**, and **revise before you rebut** — when you disagree, you must still respond with new analysis, theory, or evidence, not just a counter-argument. A defensive letter that wins arguments but changes nothing is the most common way a viable R&R dies. ## Structure of the response 1. **Cover note to the action editor.** Thank the editor; restate the contribution; summarize the *major* changes; flag any place where reviewers conflicted and how you resolved it. Mirror the editor's st

What's inside
Steps it walks through
  1. When to trigger
  2. The JOM rebuttal stance
  3. Structure of the response
  4. Handling the recurring JOM concerns
  5. Resolving masked-reviewer conflict
  6. Length discipline across rounds
  7. Sample response entry (illustrative)
  8. Preparing for the next round
  9. Checklist
  10. Anti-patterns
  11. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jmgmt-rebuttal skill do?

Use when drafting the response-to-reviewers for a Journal of Management (JOM) R&R — the point-by-point letter, the editor-first revision strategy, handling masked-reviewer conflicts, and staying within the 50-page limit across rounds. Drafts and structures the response; it does not run new analyses (jmgmt-data-analysis) or rebuild the theory (jmgmt-theory-development).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmgmt-rebuttal --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going