research-paper-craft
Use when writing, structuring, or revising a state-of-the-art scientific research paper, review, preprint, or thesis chapter and you want it to read well and land. Covers the craft of paper architecture, the narrative spine, the title and abstract, figures as the paper UI, reproducible methods.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- research-paper-craft
- metadata
- { "type": "skill", "origin": "fork-2026-06-30-RESEARCH_PHENIBUT" }
- description
- Use when writing, structuring, or revising a state-of-the-art scientific research paper, review, preprint, or thesis chapter and you want it to read well and land. Covers the craft of paper architecture, the narrative spine, the title and abstract, figures as the paper UI, reproducible methods.
03 SKILL.md 正文
research-paper-craft — writing a SOTA scientific paper
A paper is a UI for an idea. Almost no one reads it linearly. A reader skims title → abstract → figures → conclusions, then decides whether to read the body. So the paper must work at every altitude — the title alone, the abstract alone, the figures alone — and reward whoever goes deeper. Optimize for the skim and the deep read. (Readers gauge relevance from title+abstract and skim figures before committing — Royal Society 2024; Editage.)
The two-move process (do these in order)
- Outline first (Whitesides' method). Before any prose, write the outline as the figures and tables in final order, each with a one-sentence claim. The paper IS that figure sequence plus the argument connecting them. If the outline doesn't tell a story, prose won't save it. (Whitesides, Adv. Mater. 2004.)
- Write backwards. Decide the take-home messages (the 1–3 novel claims) → write Results around the figures → Methods → sharpen Discussion → Introduction (the funnel down to your gap) → Abstract → Title last. You cannot write a tight intro or abstract until you know exactly what you are claiming. (the "writing backwards" strategy, Mar. Life Sci. Technol. 2021 / PMC10077155.)
The narrative spine
Every strong paper is one story: broad context → the specific GAP (the tension) → your question → your answer → the so-what. The gap is the hook — name what is missing, wrong, or unknown, and make the reader feel it before you resolve it. Beginning–middle–end; problem-posed-then-solved. Narrative-style papers measurably engage readers more (PMC10491847). Write the one-sentence version first: "We show that X, which matters because Y." If you can't, you're not ready to write.
Per-section playbook
The engagement / keeping-interesting layer
The reviewer / editor lens
Modern SOTA (2024-era)
Workflow checklist
Sources
04 同仓库更多 Skills
clarify-requirements
Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.
openmm-md
Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein / protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.
visual-review
Take screenshots of web pages and UI using Playwright for visual review and iteration
status
Diagnostic status report — shows metaswarm installation state, project setup, and potential issues
start
Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work
setup
Interactive project setup — detects your project, configures metaswarm, writes project-local files