Agent skill · Code Review & Quality

isr-rebuttal

Use when planning and drafting the response to an Information Systems Research (ISR) revise-and-resubmit — prioritizing the Senior Editor's binding concerns, addressing genre-specific reviewer asks (assumptions/proofs, identification/validity, evaluation), updating the contribution statement, and using the electronic companion. Drafts the revision and response; it runs after isr-review-process.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isr-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: Information-Systems-Research-Skills/skills/isr-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 Rebuttal (isr-rebuttal) ## When to trigger - You received an ISR major-revision (R&R) and must plan the revision and response letter - Reviewers and the SE pull in different directions and you need a priority order - A reviewer challenged your contribution, identification, proof, or evaluation - You need to revise the ~500-word contribution statement for the resubmission ## Revise first, then write the response Do the manuscript work before drafting the letter. ISR review is developmental and SE-led, so the response is a **conversation with the Senior Editor**, organized around their synthesis. ## Prioritize by who decides 1. **Senior Editor's binding concerns first.** The SE makes the final decision; their letter defines what *must* change. Address these completely and visibly, even when individual reviewers disagree among themselves — and when they do, let the SE's framing arbitrate. 2. **Contribution/fit challenges next.** If the SE or a reviewer questioned the **contribution to IS** or the intradisciplinary framing, treat it as primary: strengthen the mechanism/insight, sharpen the silo-bridging claim, and **update the ~500-word contribution statement** to match the revis

What's inside
Steps it walks through
  1. When to trigger
  2. Revise first, then write the response
  3. Prioritize by who decides
  4. Write a point-by-point response
  5. Revision control ledger
  6. Acceptance bar for the revision
  7. Checklist
  8. Anti-patterns
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the isr-rebuttal skill do?

Use when planning and drafting the response to an Information Systems Research (ISR) revise-and-resubmit — prioritizing the Senior Editor's binding concerns, addressing genre-specific reviewer asks (assumptions/proofs, identification/validity, evaluation), updating the contribution statement, and using the electronic companion. Drafts the revision and response; it runs after isr-review-process.

How do I install it?

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