Agent skill

wsdm-author-response

Use when planning author-side communication for WSDM, a venue that historically runs no rebuttal - covers preemptive objection engineering inside the submitted PDF, the narrow legitimate channels to chairs after submission, reading reviews you cannot answer, and converting a rejection into a stronger next-cycle or sibling-venue submission.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-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: 7 KB
Bundled scripts: none
Path: WSDM-Skills/skills/wsdm-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

# WSDM Author Response At most ML and data-mining venues this skill would script a rebuttal. WSDM is different: the venue historically runs **no author response phase** - a fact documented as far back as the 2017 reviewing experiment conducted at the conference itself, and consistent with the short review window (August submission, October notification in the 2026 cycle). Plan as if you will never speak to your reviewers. If the current edition's CFP announces a response phase, that instruction supersedes everything here; check it first. ## Preemptive rebuttal: the objection inventory Since answers must ship inside the PDF, build the rebuttal *before* submission. Two weeks out, run an adversarial read with coauthors playing three WSDM reviewer archetypes - the IR-methods specialist, the applied/industry reader, and the graph/social-data reader - and log every objection in an inventory: ```text # objection-inventory.md (one row per anticipated objection) | # | Likely objection | Archetype | Answer exists? | Where in PDF | Action | | 1 | Position bias not controlled in log data | IR methods | yes | §4.2 + Tab.3 | none | | 2 | Baseline X (WSDM'25) missing | IR methods | no | - | add o

What's inside
Steps it walks through
  1. Preemptive rebuttal: the objection inventory
  2. What channels do exist after submission
  3. Reading reviews you cannot answer
  4. The rejection fork
  5. Worked micro-example: rewriting an answer into the PDF
  6. If the current edition adds a response phase
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the wsdm-author-response skill do?

Use when planning author-side communication for WSDM, a venue that historically runs no rebuttal - covers preemptive objection engineering inside the submitted PDF, the narrow legitimate channels to chairs after submission, reading reviews you cannot answer, and converting a rejection into a stronger next-cycle or sibling-venue submission.

How do I install it?

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