Agent skill

molcell-rebuttal

Use after Molecular Cell reviews arrive to triage the decision, prioritize the (often mechanism-completing) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the mechanistic gaps reviewers demand. Do not run before the experiments and revision are actually done.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill molcell-rebuttal --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Molecular-Cell-Skills/skills/molcell-rebuttal/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

# Reviewer Rebuttal (molcell-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 Molecular Cell reviews Molecular Cell reviewers are usually **molecular specialists** who probe the mechanism hard. The recurring theme is not breadth but **mechanistic completeness and rigor**: they push for the molecular step to be nailed down, alternatives excluded with separation-of-function experiments, and in-vitro claims validated in cells. Expect requests for **point mutants, reconstitutions, orthogonal biochemistry, or an additional structural/genomic control** — 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 a separation-of-function experiment" o

What's inside
Steps it walks through
  1. When to trigger
  2. What's distinctive about Molecular Cell reviews
  3. Step 0: read the editor's letter first
  4. Triage every comment into 4 buckets
  5. Prioritize the experiments (impact × feasibility)
  6. Response-letter format
  7. The "mechanism not established" demand (Molecular Cell-specific)
  8. Structure/genomics-specific reviewer asks
  9. Tone rules
  10. Output format
  11. Anti-patterns
More from Awesome-Journal-Skills
All skills →
About this skill
What does the molcell-rebuttal skill do?

Use after Molecular Cell reviews arrive to triage the decision, prioritize the (often mechanism-completing) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the mechanistic 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 molcell-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 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