Agent skill · Workflow & Productivity

orgstud-rebuttal

Use when drafting the response to reviewers and the revision plan for an Organization Studies (OS) R&R — turning developmental, theory-level reviewer comments into a credible point-by-point reply and revised manuscript. Plans and drafts the response; it does not redo the underlying analysis (route back to the specialist skills).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill orgstud-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-Studies-Skills/skills/orgstud-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 Strategy (orgstud-rebuttal) ## When to trigger - An OS R&R arrived (read it first with `orgstud-review-process`) and you are drafting the response - Reviewers disagree with each other and you must reconcile their asks without breaking the paper - A reviewer wants a theoretical reframing, deeper engagement, or a different conceptual lens - You need to decide which asks to accept, which to negotiate, and which to (carefully) decline ## OS rebuttals are developmental, not adversarial OS review is **developmental**: reviewers often co-build the theory across rounds, so the response letter is a collaboration, not a defense. The tone is respectful and substantive; the goal is to show that you took each reviewer's intellectual contribution seriously and that the paper is *stronger* for it. The editor reads the letter to judge whether you have engaged in good faith with the **theory-level** asks — those carry the decision. ## Structure the response - **Open with a synthesis.** A short cover note to the editor summarizing the main changes and how you handled the central threads — especially where reviewers diverged. - **Point-by-point, verbatim comments.** Quote each comment, the

What's inside
Steps it walks through
  1. When to trigger
  2. OS rebuttals are developmental, not adversarial
  3. Structure the response
  4. Triage the comments
  5. Handling the hard cases
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the orgstud-rebuttal skill do?

Use when drafting the response to reviewers and the revision plan for an Organization Studies (OS) R&R — turning developmental, theory-level reviewer comments into a credible point-by-point reply and revised manuscript. Plans and drafts the response; it does not redo the underlying analysis (route back to the specialist skills).

How do I install it?

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