Agent skill

icsme-author-response

Use when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all, answering the PC's specific "Response Recommended" questions with existing evidence, staying anonymous, and doing it in one round with no Major Revision safety net.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-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: ICSME-Skills/skills/icsme-author-response/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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

# ICSME Author Response Use this after ICSME early decisions are released. ICSME gives authors **one speaking turn**, and whether you get it at all is decided first: at the start of the author-response period, papers are sorted into **Accept**, **Reject**, or **Response Recommended**. Only "Response Recommended" papers write a rebuttal, and because there is **no Major Revision round**, that rebuttal is the last word before the final decision. ## First: read which bucket you are in - **Early Accept** — do not write a defensive response; move to camera-ready and the ROSE artifact. - **Early Reject** — no response is requested; a response would not be read. Reroute or rebuild. - **Response Recommended** — you are in contention. The PC has specific questions; the rest of this skill is for you. ## Triage the questions the PC actually asked - Answer the **specific questions the PC raised** in the response invitation first — they are what the discussion will turn on. A rebuttal that ignores the flagged questions to relitigate the reviews' tone is wasted. - Use evidence that **already exists** in the submitted paper or artifact. ICSME cannot accept "we will add this" — there is no revision

What's inside
Steps it walks through
  1. First: read which bucket you are in
  2. Triage the questions the PC actually asked
  3. Structure a single-round ICSME rebuttal
  4. Reviewer pushback patterns
  5. Anonymity in the response (easy to slip)
  6. Calibration
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the icsme-author-response skill do?

Use when drafting an IEEE ICSME author response during the double-anonymous author-response period, covering the early-decision cut that decides whether you respond at all, answering the PC's specific "Response Recommended" questions with existing evidence, staying anonymous, and doing it in one round with no Major Revision safety net.

How do I install it?

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