micro-author-response
Use when reviews arrive for a MICRO submission and the rebuttal/revision window opens — triaging reviewer objections by what can change a decision, answering methodology attacks with runs and configs rather than promises, keeping anonymity intact, and staying inside MICRO's professional-conduct rules for rebuttals.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.
# MICRO Author Response MICRO 2026 scheduled a combined **rebuttal/revision window, June 3–17** — two full weeks, which is generous by conference standards and changes the strategy: there is time to *run new experiments*, not merely to argue. Whether the cycle permitted an updated PDF versus text-only responses is 待核实 on the live pages; the playbook below works under either mechanic. ## Hour zero: classify before drafting Read all reviews twice, then sort every distinct objection into exactly one bucket: | Bucket | Example | Winning move | |---|---|---| | Factual misread | "No overhead analysis" — but Table 5 exists | Point precisely: "Table 5, rows 3–6" | | Methodology doubt | "Baseline prefetcher looks untuned" | Run the check they imply; report numbers | | Missing experiment | "How does this behave at 16 cores?" | Two weeks is enough — run it | | Scope disagreement | "Should also handle GPUs" | Bound the claim; do not promise a new paper | | Taste / significance | "Gains feel incremental" | Reframe headroom-captured %, cite the oracle bound | Decision-relevant buckets are the middle three. A rebuttal that spends its length on the misreads and the taste disputes has conceded the
- Hour zero: classify before drafting
- The MICRO-specific physics of rebuttals
- Response architecture
- Sentence surgery: weak versus strong response lines
- Prioritization under a length cap
- Coordinating a multi-author response
- After submission of the response
- Output format
What does the micro-author-response skill do?
Use when reviews arrive for a MICRO submission and the rebuttal/revision window opens — triaging reviewer objections by what can change a decision, answering methodology attacks with runs and configs rather than promises, keeping anonymity intact, and staying inside MICRO's professional-conduct rules for rebuttals.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.