lancet-rebuttal
Use after Lancet reviews arrive (including the statistical reviewer and the editor's letter) to triage the decision, answer statistical and clinical comments, and draft a point-by-point response that quotes the reviewer, gives evidence, quotes the revised manuscript text, and keeps causal language cautious. Do not run before the main text is actually revised.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lancet-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 (lancet-rebuttal) ## When to trigger - A decision letter arrives (reject / major or minor revision). - You have clinical and statistical reviewer comments and need a strategy before writing. - A revision is drafted and you need the point-by-point response letter. ## 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 **emphasises** (load-bearing — address fully). - Any **deal-breaker** the editor names (e.g., "the primary analysis must follow the pre-specified SAP," "registration timing must be clarified," "the causal claim must be softened"). > A "we would consider a revised manuscript" is an invitation gated on the deal-breaker. Don't treat it as a flat reject, but don't under-deliver. ## The statistical reviewer is its own track The Lancet routinely uses a **statistical reviewer**. Treat their comments as a distinct, high-priority track: - Answer with the **pre-specified analysis** and SAP references; show CIs and absolute effects. - If asked to add an analysis, add it and label pre-specified vs post-hoc honestly. - A
- When to trigger
- Step 0: read the editor's letter first
- The statistical reviewer is its own track
- Triage every comment into 4 buckets
- Response-letter format
- Tone and causal-language rules (Lancet-specific)
- Update the Research in context panel if the evidence base changed
- The Lancet-specific reviewer comments and how to land them
- Worked micro-example (illustrative — not a real exchange)
- Output format
- Anti-patterns
What does the lancet-rebuttal skill do?
Use after Lancet reviews arrive (including the statistical reviewer and the editor's letter) to triage the decision, answer statistical and clinical comments, and draft a point-by-point response that quotes the reviewer, gives evidence, quotes the revised manuscript text, and keeps causal language cautious. Do not run before the main text is actually revised.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill lancet-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.