rebuttal
Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says \"rebuttal\", \"reply to reviewers\", \"ICML rebuttal\", \"OpenReview response\", or wants to answer external reviews safely.
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill rebuttal --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.
# Workflow 4: Rebuttal Prepare and maintain a grounded, venue-compliant rebuttal for: **$ARGUMENTS** ## Scope This skill is optimized for: - ICML-style **text-only rebuttal** - strict **character limits** - **multiple reviewers** - **follow-up rounds** after the initial rebuttal - safe drafting with **no fabrication**, **no overpromise**, and **full issue coverage** This skill does **not**: - run
What does the rebuttal skill do?
Workflow 4: Submission rebuttal pipeline. Parses external reviews, enforces coverage and grounding, drafts a safe text-only rebuttal under venue limits, and manages follow-up rounds. Use when user says \"rebuttal\", \"reply to reviewers\", \"ICML rebuttal\", \"OpenReview response\", or wants to answer external reviews safely.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill rebuttal --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/Auto-Empirical-Research-Skills, a repository with 3,244 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.