ors-rebuttal
Use when responding to an Operations Research (OR) decision letter — writing the point-by-point response, closing proof gaps, adding baselines/instances, and passing the ORJournal code/data reproducibility review across a revision cycle. Drafts the revision and response; it does not parse the decision in the first place (ors-review-process) or run the final preflight (ors-submission).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-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.
# Revision & Response (ors-rebuttal) ## When to trigger - You have a major/minor revision decision from the handling Area Editor and must respond. - A reviewer found a proof gap, a missing baseline, or a reproducibility shortfall. - You are preparing the code/data deposit for the ORJournal pull-request review. ## The OR response letter *Operations Research* revisions are **technical**. Reviewers expect the mathematics and computation to actually change, not just the prose. Structure the response so every point is traceable: - **Point-by-point, verbatim.** Quote each reviewer/editor comment, then give your response and the **exact location** of the change (section, theorem, table, e-companion). - **Honor the editor's synthesis first.** Address the binding points the Area/Associate Editor emphasized before optional reviewer suggestions. - **Be precise about what changed.** "We now prove Theorem 3 without Assumption 2; see the new Lemma 4 and Appendix B" beats "we revised the proof." ## Closing the common technical asks | Reviewer ask | Substantive response | |--------------|----------------------| | "Proof gap / assumption smuggled in" | Repair the proof; state where each assumption
- When to trigger
- The OR response letter
- Closing the common technical asks
- Reproducibility review (ORJournal)
- Length & format discipline through revision
- Anti-patterns
- Output format
What does the ors-rebuttal skill do?
Use when responding to an Operations Research (OR) decision letter — writing the point-by-point response, closing proof gaps, adding baselines/instances, and passing the ORJournal code/data reproducibility review across a revision cycle. Drafts the revision and response; it does not parse the decision in the first place (ors-review-process) or run the final preflight (ors-submission).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-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.