Agent skill

sigmetrics-author-response

Use when responding to ACM SIGMETRICS reviews, covering any initial rebuttal and — distinctively — the one-shot revision response letter that must map every item on the reviewers' required-changes list to a concrete change in the revised POMACS paper, resubmitted to a subsequent rolling deadline and re-reviewed once by the original reviewers under double-anonymity.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-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: SIGMETRICS-Skills/skills/sigmetrics-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

# SIGMETRICS Author Response Use this after SIGMETRICS reviews are released. The defining SIGMETRICS response is the **one-shot revision letter**: if you receive a **One-Shot Revision** decision, you get **exactly one** chance to resubmit a revised paper (to one of the next two rolling deadlines) accompanied by a letter that closes the reviewers' **explicit list of required changes**. Any initial-round rebuttal is secondary; the revision letter is where the paper is won. ## Triage - Answer what affects the decision: model rigor, proof correctness, assumption validity, the soundness and fairness of empirical/simulation evidence, novelty, and reproducibility. - Use evidence that already exists or that the revision will concretely add — a completed proof case, a new simulation, a validated assumption — never a vague promise. - Correct factual misreadings first; a reviewer who misread a lemma or a plot is often persuadable. - Preserve **double-anonymity** in any letter that circulates before decision (the Operational Systems Track excepted). ## The one-shot revision response letter (the distinctive SIGMETRICS move) A One-Shot Revision is single-shot: there is no second revision, so the

What's inside
Steps it walks through
  1. Triage
  2. The one-shot revision response letter (the distinctive SIGMETRICS move)
  3. Choosing the resubmission deadline
  4. Reviewer pushback patterns
  5. Anonymity in the letter (easy to slip)
  6. Calibration
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the sigmetrics-author-response skill do?

Use when responding to ACM SIGMETRICS reviews, covering any initial rebuttal and — distinctively — the one-shot revision response letter that must map every item on the reviewers' required-changes list to a concrete change in the revised POMACS paper, resubmitted to a subsequent rolling deadline and re-reviewed once by the original reviewers under double-anonymity.

How do I install it?

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