Agent skill · Workflow & Productivity

orgsci-rebuttal

Use after an Organization Science R&R to plan the revision and draft the point-by-point response letter, following the journal's codified author-response norms — verbatim italic quoting of each comment, no duplicated responses across reviewers, and a non-combative, non-effusive tone, while prioritizing the autonomous senior editor's concerns.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-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: 5 KB
Bundled scripts: none
Path: Organization-Science-Skills/skills/orgsci-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

# R&R Revision & Response Letter (orgsci-rebuttal) ## When to trigger - You received a major/minor R&R and need to plan revisions and write the response - Reviewers disagree with each other or with the senior editor - You are unsure how to format the response letter for this venue ## Revise the manuscript before you write the letter A response letter is only as good as the revision behind it. Re-derive the **overall contribution** the SE asked for (`orgsci-contribution-framing`), strengthen the **mechanism and design logic** where identification is impossible (`orgsci-methods` / `orgsci-data-analysis`), and update the exhibits. Then write the letter to a manuscript you have actually changed. ## Follow the journal's codified author-response norms Organization Science's official length policy spells out **how to write the response**, and editors expect it: - **Quote each editor/reviewer comment verbatim, in italics**, immediately above your response, so the reader sees exactly what you are answering. - **Do not duplicate responses across reviewers.** When two reviewers raise the same point, answer it once and cross-reference, rather than pasting the same paragraph repeatedly. - **Avo

What's inside
Steps it walks through
  1. When to trigger
  2. Revise the manuscript before you write the letter
  3. Follow the journal's codified author-response norms
  4. Prioritize by who decides
  5. Mechanics
  6. SE-centered revision ledger
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the orgsci-rebuttal skill do?

Use after an Organization Science R&R to plan the revision and draft the point-by-point response letter, following the journal's codified author-response norms — verbatim italic quoting of each comment, no duplicated responses across reviewers, and a non-combative, non-effusive tone, while prioritizing the autonomous senior editor's concerns.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgsci-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