ijoc-rebuttal
Use when drafting the response to an INFORMS Journal on Computing (IJOC) decision letter — turning referee objections (especially about experiments and reproducibility) into a point-by-point response with re-run evidence. Builds the rebuttal and revision plan; it does not run new analysis on its own (route to ijoc-data-analysis).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-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.
# Rebuttal Strategy (ijoc-rebuttal) ## When to trigger - An IJOC **major/minor revision** arrived and you need a response-letter strategy - Referees challenge the **fairness, scale, or reproducibility** of the computational experiments - You disagree with a referee on a method point and must push back **without alienating** the associate editor - You need to convert a long, mixed decision letter into an ordered, checkable revision plan ## The IJOC rebuttal mindset IJOC revisions are won with **evidence, not rhetoric**. Most consequential objections are computational ("the comparison is unfair," "instances too small," "cannot reproduce"), and the strongest response is a re-run that settles the question: more standard instances, a stronger baseline, more seeds, a performance profile, an updated deposit. Because the **associate editor is undisclosed and single-blind**, write to the substance of each report for a technical reader; never speculate about who wrote what. The AE is reading for whether you took the experiments seriously. ## Structure of the response 1. **Open with the changes that matter.** A short summary: the main new experiments, the strengthened baselines, the reproduci
- When to trigger
- The IJOC rebuttal mindset
- Structure of the response
- Mapping common IJOC objections to the response
- Disagreeing well
- Checklist
- Anti-patterns
- Output format
What does the ijoc-rebuttal skill do?
Use when drafting the response to an INFORMS Journal on Computing (IJOC) decision letter — turning referee objections (especially about experiments and reproducibility) into a point-by-point response with re-run evidence. Builds the rebuttal and revision plan; it does not run new analysis on its own (route to ijoc-data-analysis).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-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.