Agent skill · Documentation

icassp-author-response

Use when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already know you, answering signal-processing reviewers from the four-page record without a revised PDF, and writing for the technical-committee decision rather than for tone.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icassp-author-response --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: ICASSP-Skills/skills/icassp-author-response/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

# ICASSP Author Response Use this after ICASSP reviews are released. First confirm whether the current cycle even runs a rebuttal: ICASSP historically had **no** author-response stage, and a short window is a comparatively **recent addition** (in the 2026 cycle authors could reply until ~22 December 2025). Reopen the current call before promising reviewers anything. ## What the rebuttal is and is not - It is a **short, text-based reply** to the reviews, not a chance to upload a revised PDF or new experiments. Argue from what you already submitted. - ICASSP is **single-blind**, so the reviewers know your identity; write professionally and do not attempt to re-establish anonymity or drop identifying hints to sway a reviewer. - The audience is the **area/technical-committee decision**: give whoever aggregates the reviews a clean reason to accept, not a point-by-point defense that wins arguments but not the paper. ## Triage before drafting 1. Separate **factual errors in the review** (a metric misread, a missed baseline that is in the paper) from **legitimate gaps** (a missing comparison, an unreported condition). 2. Fix the factual errors first with an exact pointer: "Table 2, row 3 a

What's inside
Steps it walks through
  1. What the rebuttal is and is not
  2. Triage before drafting
  3. Signal-processing reviewer pushback patterns
  4. Drafting pattern
  5. Micro-example
  6. Calibration for a short window
  7. Output format
  8. Currency note
More from Awesome-Journal-Skills
All skills →
About this skill
What does the icassp-author-response skill do?

Use when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already know you, answering signal-processing reviewers from the four-page record without a revised PDF, and writing for the technical-committee decision rather than for tone.

How do I install it?

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

Keep going