infocom-author-response
Use when handling the IEEE INFOCOM post-submission reality — that the venue has traditionally offered no author rebuttal — covering how to write a self-defending submission, how to read and act on an early-reject, what to do after a final reject, and how to use any response window a given cycle does introduce (verify per cycle).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.
# INFOCOM Author Response Use this after submission, and — more importantly — *before* it. The distinctive INFOCOM fact is that there is **traditionally no author rebuttal**: reviewer scores and TPC discussion decide, and you usually never get a turn to reply. So the "author response" that matters most is the one you bake into the PDF. This skill covers the defensive submission, the early-reject checkpoint, the post-reject move, and any actual response window a cycle introduces (**待核实** each year). ## The response that counts: a self-defending submission Because you likely cannot reply, answer the reviewer *in the paper*: - **Pre-empt the top objection per subarea.** A theory reviewer will question an assumption — state and justify it in the system model. A systems reviewer will call a baseline unfair — tune it and document the budget. A measurement reviewer will doubt generalization — scope the claim. - **State limits before a reviewer finds them.** A short "where this does not hold" paragraph disarms the objection you could not otherwise rebut. - **Make every number checkable.** Named simulator, seeds, confidence intervals, and (optionally) released scripts turn "I don't believe
- The response that counts: a self-defending submission
- Reading an early-reject
- After a final reject
- If a cycle introduces a response window (verify first)
- Calibration
- Output format
What does the infocom-author-response skill do?
Use when handling the IEEE INFOCOM post-submission reality — that the venue has traditionally offered no author rebuttal — covering how to write a self-defending submission, how to read and act on an early-reject, what to do after a final reject, and how to use any response window a given cycle does introduce (verify per cycle).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.