cell-rebuttal
Use after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cell-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.
# Reviewer Rebuttal (cell-rebuttal) ## When to trigger - A decision letter arrives (reject / reject-but-resubmit / major or minor revision). - You have reviewer comments and need a strategy before running experiments. - A revision is drafted and you need the point-by-point response letter. ## What's distinctive about Cell reviews Cell reviews are typically **detailed and demanding**, and frequently request **substantial new experiments** to make the story **airtight**. The recurring theme is **completeness**: reviewers push for the mechanism to be fully nailed down, alternatives excluded, and causality proven. Expect to do real bench work, not just rewriting. ## Step 0: read the editor's letter first The **editor's** framing **outranks** individual reviewers. Identify: - The decision type and whether a new review round is implied. - Which concerns the editor **emphasizes** (load-bearing — address fully). - Any **deal-breaker** the editor names (e.g., "the central mechanism needs an independent line of evidence"). > The editor often signals which reviewer requests are essential versus optional. Weight the response accordingly — do not treat all three reviewers as equal if the editor
- When to trigger
- What's distinctive about Cell reviews
- Step 0: read the editor's letter first
- Triage every comment into 4 buckets
- Prioritize the experiments (impact × feasibility)
- Response-letter format
- The "completeness" demand (Cell-specific)
- Tone rules
- Output format
- Anti-patterns
What does the cell-rebuttal skill do?
Use after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cell-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/Awesome-Journal-Skills, a repository with 909 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.