| name | sci-cover-letter |
| description | Use when writing the editor-facing cover letter for Science (AAAS) — a tight, significance-forward pitch, not a summary, that lets the editor decide within two minutes whether the paper clears the broad-interest bar and should go out for external review. |
Cover Letter & Editor Pitch (sci-cover-letter)
When to trigger
- Ready to submit and need the editor-facing letter.
- The current letter is a formality ("please find enclosed…") with no argument.
- You need to argue broad significance explicitly to survive triage.
What the cover letter is for
Science editors triage fast. The letter must let an editor decide, in under two minutes, that the paper is plausibly broad enough to review. It is a significance argument, not a summary.
Structure (≈ 250–400 words, one page)
- Opening claim (2–3 sentences). The one-sentence advance (
sci-framing) plus why it matters to a broad audience. Lead with the result, not the background.
- Why Science specifically (2–3 sentences). Why this is general-interest, not specialist — what communities beyond your own will care and why now (
sci-framing why-now trigger).
- What's new vs. prior work (2–3 sentences). The decisive distinction from the closest prior papers, including any concurrent work. Pre-empt "isn't this known?".
- Format & logistics (short). "We submit this as a Report/Research Article. The work has not been published and is not under consideration elsewhere."
- Optional: suggested/excluded reviewers, competing interests, related submissions, and any embargo/press considerations.
The significance paragraph test
The editor should be able to copy your second paragraph into a referee-invitation email. If it reads as specialist or hedged, rewrite it.
Logistics to include
Tone
- Confident, specific, quantified — but not grandiose. Editors discount "groundbreaking/unprecedented".
- No jargon walls; a chemistry editor should grasp a biology letter and vice versa.
- Short paragraphs; the whole letter fits on one page.
Cover-letter pass for Science
Use this as a second-pass capability check. First lock the broad discovery claim, decisive evidence, uncertainty/limitations, and why the result belongs in a general-science weekly; then test whether the manuscript addresses general-science reviewers and editors who ask whether the result changes a broad field, is technically decisive, and can be understood outside the subdiscipline.
- Primary move: Make the letter a routing document: discovery, breadth, decisive evidence, policy/field implication, and compliance in one editor-facing argument.
- Decision ledger: return
claim / evidence / blocker / next edit rows so the next pass can patch the manuscript directly.
- Neighbor test: compare against Nature for similar broad-scope novelty, PNAS for academy-wide breadth, specialist journals when the claim is field-internal; if the neighboring outlet has the stronger audience claim, recommend re-routing before polishing.
- Verification floor: before submission-ready advice, re-open
resources/official-source-map.md for volatile rules and name the one unresolved fact that could change the recommendation.
Before/after: the significance paragraph
The second paragraph is the one an editor pastes into a referee invitation. Make it copy-ready:
- Weak (summary register): "In this manuscript we report the results of our study of protein T, which we characterized using cryo-EM and functional assays, revealing several interesting features of its conformational cycle."
- Strong (significance register): "We show that transporter T uses a previously unseen occluded intermediate to move substrate — a gating step that current models of secondary active transport omit. Because this state is conserved across the superfamily, the finding revises how a broad membrane-biology and biophysics community should model transport, and it explains prior anomalous kinetics that had no mechanistic account."
The strong version names the advance, the breadth (who beyond the subfield cares), and the consequence (what changes) — in three sentences an editor can forward unedited.
Common cover-letter failure modes (and the fix)
| Failure mode | Why it triggers a bounce | Fix |
|---|
| Reads as an abstract | Editor learns what you did, not why it's broad | Lead paragraph 2 with the consequence for a field |
| Superlatives, no numbers | Editors discount "groundbreaking" | Replace each adjective with a quantity or a decisive comparison |
| Omits concurrent work | Looks naive or evasive | One sentence: "Concurrent work X did Y; we differ by Z" |
| No originality statement | Administrative bounce | Add the not-published / not-under-review line explicitly |
| Buries the hook after logistics | Hook is missed in a 2-minute read | First sentence carries the advance |
Output format
【One-line advance restated】 "..."
【Broad-significance paragraph】 reviewer-invitation-ready? yes/no
【Novelty vs closest prior/concurrent work】 stated? yes/no
【Manuscript type + length】 ...
【Logistics checklist】 originality / COI / suggested-opposed reviewers / related subs
【Next】 sci-submission
Anti-patterns
- Do not summarize the abstract; argue significance instead.
- Do not use unsupported superlatives — quantify the advance.
- Do not omit the originality/exclusivity statement.
- Do not bury the hook below logistics; the first sentence carries the advance.
