mgsci-rebuttal
Use when planning and drafting the revision and point-by-point response for a Management Science (INFORMS) R&R — prioritizing the Department Editor's binding concerns, addressing analytical-proof or empirical-identification objections, preserving double-anonymization, and keeping the revision within the page cap and Data-and-Code-Disclosure requirements. It handles the post-decision response; it does not run a fresh submission (mgsci-submission).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-rebuttal --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# R&R Rebuttal (mgsci-rebuttal) ## When to trigger - You received a major-revision (R&R) decision from Management Science - You have reviewer reports and a Department Editor letter and must plan the response - You are unsure which concerns are decisive versus advisory - You need to fit a strengthened paper inside the invited-revision page cap ## Read the Department Editor's letter as the map In Management Science the **Department Editor** synthesizes the reviews and signals which concerns are **binding**. Plan the revision around that letter first: list every point from the DE and each reviewer, mark each binding / important / advisory, and resolve any conflicts between reviewers by deferring to the DE's framing (note the conflict explicitly in your response). ## Address objections in the paper's lane - **Analytical lane.** If a reviewer questions an assumption, either defend its necessity or show the result survives relaxing it (add an extension/robustness proposition). If a proof step is challenged, tighten the proof and, where useful, add a numerical illustration. Reframe comparative statics to make the managerial intuition unmistakable. - **Empirical lane.** If identification i
- When to trigger
- Read the Department Editor's letter as the map
- Address objections in the paper's lane
- Response-letter mechanics
- Preserve the rules on resubmission
- Concern-triage table
- Worked micro-example (illustrative): an R&R on a platform field experiment
- Referee-pushback patterns and the venue-specific fix
- Anti-patterns
- Output format
What does the mgsci-rebuttal skill do?
Use when planning and drafting the revision and point-by-point response for a Management Science (INFORMS) R&R — prioritizing the Department Editor's binding concerns, addressing analytical-proof or empirical-identification objections, preserving double-anonymization, and keeping the revision within the page cap and Data-and-Code-Disclosure requirements. It handles the post-decision response; it does not run a fresh submission (mgsci-submission).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-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.