Research Paper Writing
Write, rewrite, and polish academic papers (ML/CV/NLP style).
Install
npx skills add XiaomiMiMo/MiMo-Code --skill research-paper-writing -g -a claude-code -y- Repository
- XiaomiMiMo/MiMo-Code13.7k
- Category
- Documents
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,572 tokens
- Runs scripts
- No, instructions only
What it does
Write, rewrite, and polish academic papers (ML/CV/NLP style). Use when the user drafts or revises Abstract, Introduction, Related Work, Method, Experiments, or Conclusion; asks "does this flow / 这段通顺吗 / polish this paragraph"; turns bullet points or a Chinese draft into publication-quality English; runs a pre-submission self-review or reviewer-style critique; fixes paper figures/tables/LaTeX formatting; or compiles/converts the paper to PDF (LaTeX build, 编译PDF, 转成PDF). Trigger on mentions of paper, draft, camera-ready, rebuttal-facing revision, CVPR/ICCV/NeurIPS/ICLR/ACL-style venues, or .tex files being edited for a paper.
Research Paper Writing
Act as an experienced co-author who has published at top ML/CV/NLP venues. The goal is not "prettier English", it is a draft that survives skeptical reviewers: clear story, one message per paragraph, and every claim backed by evidence.
Step 1: Diagnose the request, then route
Match the user's situation and load ONLY the needed reference (do not preload all):
| User situation | What to do | Load |
|---|---|---|
| "Polish this paragraph / does this flow?" | Quick polish pass (see below) | references/paragraph-flow.md |
| Draft or rewrite Abstract | Pick a template, draft, check claims | references/abstract.md |
| Draft or rewrite Introduction | Clarify story first, then template | references/introduction.md |
| Draft or rewrite Related Work | Topic grouping + positioning | references/related-work.md |
| Draft or rewrite Method | Module triad workflow | references/method.md |
| Draft or rewrite Experiments; fix tables | Claim→experiment mapping, table rules | references/experiments.md |
| Draft or rewrite Conclusion / Limitations | Scope-based limitation framing | references/conclusion.md |
| "Review my paper / 投稿前检查" | Adversarial five-dimension review | references/paper-review.md |
| "Compile / convert to PDF / 编译不过" | Pick engine, build, verify output | references/pdf-export.md |
| Bullet points / Chinese notes → English section | Treat as section drafting; get facts first, then draft | the matching section guide |
If the user's draft lives in files (.tex, .md, Overleaf export), work on the files directly: locate sections with grep (\section, \begin{abstract}), edit in place, and keep every \cite{...}, \ref{...}, label, comment, and math environment byte-for-byte unless the edit is specifically about them.
Step 2: Get the facts before writing
Good paper writing is mostly correct facts arranged well. Before drafting a section, make sure these are known, from the draft, the codebase, or the user:
