isca-author-response
Use when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and a revised PDF with new experiments, structuring responses that arm a champion at the PC meeting, and avoiding window-burning mistakes.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-author-response --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.
# ISCA Author Response ISCA 2026 gave authors a combined **rebuttal/revision period, February 16 to March 6** — three weeks in which the team could both argue and *change the paper*. That design rewards teams that treat the window as an engineering sprint with a triage phase, and punishes teams that spend it composing indignation. Everything here assumes that verified 2026 structure; the 2027 window's existence, length, and rules are 待核实 until the new CFP posts. ## Day 1-2: triage before any writing or computing Read all reviews twice: once fast for temperature, once slow building the objection ledger. Classify every distinct point: | Class | Definition | Window response | |---|---|---| | **F** — factual error | Reviewer misread something present in the PDF | Quote page/section/figure; one sentence; zero new work | | **E** — evidence gap, closable | Missing experiment your infrastructure can run in days | Run it; report in response; fold into revision if permitted | | **E∞** — evidence gap, not closable | Needs silicon, months, or data you lack | Concede scope honestly; state what the existing evidence does cover | | **D** — design objection | "This breaks under X" / "cost is under
- Day 1-2: triage before any writing or computing
- Day 2: freeze the experiment plan
- Writing the response document
- Using the revision half of the window
- What not to spend the window on
- Window-close checklist
- The three weeks on a calendar
What does the isca-author-response skill do?
Use when ISCA reviews arrive and the rebuttal-plus-revision window opens — triaging objections by what a three-week window can actually fix, deciding between textual rebuttal and a revised PDF with new experiments, structuring responses that arm a champion at the PC meeting, and avoiding window-burning mistakes.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-author-response --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.