From molcell-skills
Writes Molecular Cell-style Summaries: a single unstructured paragraph (~150 words) that explicitly states the molecular mechanism, quantified results, and physiological consequence for a molecular-biology readership.
How this skill is triggered — by the user, by Claude, or both
Slash command
/molcell-skills:molcell-summaryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Mechanism, framing, and structure are settled (do this late).
Molecular Cell's abstract is the Summary: a single, unstructured paragraph (no subheadings, no citations) of roughly ≤150 words (treat as a ceiling; confirm the current cap). It is written for a molecular-biology readership — you can assume familiarity with the process but must still name the mechanism and quantify. It must convey the molecular question, the mechanism, and why it matters physiologically.
Because Molecular Cell rewards depth, the Summary should make clear the mechanism is established by independent methods, not merely proposed.
Every effect claim should carry a number somewhere in the paper, and the headline belongs in the Summary: a rate, a fold-change, an affinity, a resolution, an occupancy. A Summary with zero numbers is not finished.
Molecular Cell's initial triage is run by professional in-house scientific editors. They decide in minutes whether the paper goes to review, and the Summary plus the title are usually all they read when they decide. Two questions dominate: (1) is there a molecular mechanism here, worked out and validated — or only a phenotype with a proposed cause; and (2) is the mechanism proven by more than one approach. Write the Summary so both answers are visible without the figures. A Summary that names a molecule, a molecular action, and a physiological consequence survives triage; a Summary that lists assays performed does not.
Before (method recap, no mechanism, no number, 39 words):
Here we studied the helicase XYZ using cryo-EM and biochemistry. We solved several structures and performed unwinding assays. XYZ was important for replication. These findings advance our understanding of DNA replication.
After (mechanism named, quantified, physiological stake, ~85 words):
How replicative helicases couple ATP hydrolysis to strand separation at a stalled fork is unclear. Combining a 2.9 Å cryo-EM structure with single-molecule unwinding, we find that the helicase XYZ grips the lagging strand through a conserved β-hairpin and that hydrolysis at a single subunit ratchets one nucleotide per step. A hairpin point mutant uncouples ATPase from unwinding, slowing fork progression 12-fold and sensitizing cells to replication stress. XYZ thus converts nucleotide hydrolysis into processive, strand-selective translocation that safeguards genome duplication.
The "after" version names the actor (XYZ), the molecular mechanism (β-hairpin grip; single-subunit ratchet), a quantified effect (2.9 Å; 12-fold), orthogonal evidence (structure + single-molecule + mutant), and a physiological consequence.
【Summary】 single paragraph (word count: N ≤ ~150)
【Five moves present?】 context / gap / approach+result / mechanism named / physiological consequence
【Mechanism explicit?】 yes/no — the named molecular cause
【Quantified headline result?】 yes/no + the number
【Jargon hits removed】 [...]
【Next】 molcell-highlights
molcell-highlights).The ~150-word cap is a working default — confirm against the current Molecular Cell information-for-authors page.
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin molcell-skillsPolishes a scientific abstract into Cell's Summary format: a single ≤150-word paragraph with explicit mechanism, quantified headline result, and broad significance.
Frames a set of experiments into a single-mechanism Molecular Cell story: molecular question → mechanism → physiological consequence. Use when a manuscript reads as a catalog of techniques rather than one mechanistic arc.
Polishes Science (AAAS) abstracts and one-sentence summaries: quantifies results, removes jargon, enforces ≤125 words. Use late-stage when format is settled.