cell-summary
Use to write Cell's Summary — a single unstructured paragraph of ≤ ~150 words that conveys the complete story, the mechanism, and the broad significance, quantified and readable by a general life-scientist. Late-stage polish.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cell-summary --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.
# Summary / Abstract (cell-summary) ## When to trigger - Significance, framing, and structure are settled (do this late). - The abstract reads like a method recap with no mechanism or result. - It exceeds ~150 words, uses subheadings, or is dense with acronyms. - It states *that* something happens but never *how* (no mechanism). ## What Cell calls it Cell's abstract is the **Summary**: a **single, unstructured paragraph** (no subheadings, no citations) of roughly **≤150 words**, written for a broad life-sciences readership — not your subfield. It must convey the **complete story**: the question, the mechanism, and why it matters, with quantification. ## Five-move structure (no labels in the text) 1. **Context / stakes** (1 sentence) — the broad biological problem. 2. **Gap / question** (1 sentence) — what was unknown. 3. **What we did + what we found** (2–3 sentences) — the mechanism, with the key quantified results and the converging evidence that makes it a complete story. 4. **Mechanism stated explicitly** — name the molecular/cellular cause, not just the phenotype. 5. **Significance** (1 sentence) — why a broad community should care. Because Cell demands completeness, the Summa
- When to trigger
- What Cell calls it
- Five-move structure (no labels in the text)
- Hard constraints
- Jargon blacklist (rewrite on sight)
- Quantification check
- What the in-house editor reads first
- Worked micro-example (before → after)
- Output format
- Anti-patterns
What does the cell-summary skill do?
Use to write Cell's Summary — a single unstructured paragraph of ≤ ~150 words that conveys the complete story, the mechanism, and the broad significance, quantified and readable by a general life-scientist. Late-stage polish.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cell-summary --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.