[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPF5PXZSWJVMQKDJ3RG50K":3,"skill-same:01M7EPF5PXZSWJVMQKDJ3RG50K":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M7EPF5PXZSWJVMQKDJ3RG50K","ml-paper-writing",null,"Write publication-ready ML\u002FAI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-ml-paper-writing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ml-paper-writing\ndescription: Write publication-ready ML\u002FAI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.\nversion: 1.0.0\nauthor: Orchestra Research\nlicense: MIT\ntags: [Academic Writing, NeurIPS, ICML, ICLR, ACL, AAAI, COLM, LaTeX, Paper Writing, Citations, Research]\ndependencies: [semanticscholar, arxiv, habanero, requests]\n---\n\n# ML Paper Writing for Top AI Conferences\n\nExpert-level guidance for writing publication-ready papers targeting **NeurIPS, ICML, ICLR, ACL, AAAI, and COLM**. This skill combines writing philosophy from top researchers (Nanda, Farquhar, Karpathy, Lipton, Steinhardt) with practical tools: LaTeX templates, citation verification APIs, and conference checklists.\n\n## Core Philosophy: Collaborative Writing\n\n**Paper writing is collaborative, but Claude should be proactive in delivering drafts.**\n\nThe typical workflow starts with a research repository containing code, results, and experimental artifacts. Claude's role is to:\n\n1. **Understand the project** by exploring the repo, results, and existing documentation\n2. **Deliver a complete first draft** when confident about the contribution\n3. **Search literature** using web search and APIs to find relevant citations\n4. **Refine through feedback cycles** when the scientist provides input\n5. **Ask for clarification** only when genuinely uncertain about key decisions\n\n**Key Principle**: Be proactive. If the repo and results are clear, deliver a full draft. Don't block waiting for feedback on every section—scientists are busy. Produce something concrete they can react to, then iterate based on their response.\n\n---\n\n## ⚠️ CRITICAL: Never Hallucinate Citations\n\n**This is the most important rule in academic writing with AI assistance.**\n\n### The Problem\nAI-generated citations have a **~40% error rate**. Hallucinated references—papers that don't exist, wrong authors, incorrect years, fabricated DOIs—are a serious form of academic misconduct that can result in desk rejection or retraction.\n\n### The Rule\n**NEVER generate BibTeX entries from memory. ALWAYS fetch programmatically.**\n\n| Action | ✅ Correct | ❌ Wrong |\n|--------|-----------|----------|\n| Adding a citation | Search API → verify → fetch BibTeX | Write BibTeX from memory |\n| Uncertain about a paper | Mark as `[CITATION NEEDED]` | Guess the reference |\n| Can't find exact paper | Note: \"placeholder - verify\" | Invent similar-sounding paper |\n\n### When You Can't Verify a Citation\n\nIf you cannot programmatically verify a citation, you MUST:\n\n```latex\n% EXPLICIT PLACEHOLDER - requires human verification\n\\cite{PLACEHOLDER_author2024_verify_this}  % TODO: Verify this citation exists\n```\n\n**Always tell the scientist**: \"I've marked [X] citations as placeholders that need verification. I could not confirm these papers exist.\"\n\n### Recommended: Install Exa MCP for Paper Search\n\nFor the best paper search experience, install **Exa MCP** which provides real-time academic search:\n\n**Claude Code:**\n```bash\nclaude mcp add exa -- npx -y mcp-remote \"https:\u002F\u002Fmcp.exa.ai\u002Fmcp\"\n```\n\n**Cursor \u002F VS Code** (add to MCP settings):\n```json\n{\n  \"mcpServers\": {\n    \"exa\": {\n      \"type\": \"http\",\n      \"url\": \"https:\u002F\u002Fmcp.exa.ai\u002Fmcp\"\n    }\n  }\n}\n```\n\nExa MCP enables searches like:\n- \"Find papers on RLHF for language models published after 2023\"\n- \"Search for transformer architecture papers by Vaswani\"\n- \"Get recent work on sparse autoencoders for interpretability\"\n\nThen verify results with Semantic Scholar API and fetch BibTeX via DOI.\n\n---\n\n## Workflow 0: Starting from a Research Repository\n\nWhen beginning paper writing, start by understanding the project:\n\n```\nProject Understanding:\n- [ ] Step 1: Explore the repository structure\n- [ ] Step 2: Read README, existing docs, and key results\n- [ ] Step 3: Identify the main contribution with the scientist\n- [ ] Step 4: Find papers already cited in the codebase\n- [ ] Step 5: Search for additional relevant literature\n- [ ] Step 6: Outline the paper structure together\n- [ ] Step 7: Draft sections iteratively with feedback\n```\n\n**Step 1: Explore the Repository**\n\n```bash\n# Understand project structure\nls -la\nfind . -name \"*.py\" | head -20\nfind . -name \"*.md\" -o -name \"*.txt\" | xargs grep -l -i \"result\\|conclusion\\|finding\"\n```\n\nLook for:\n- `README.md` - Project overview and claims\n- `results\u002F`, `outputs\u002F`, `experiments\u002F` - Key findings\n- `configs\u002F` - Experimental settings\n- Existing `.bib` files or citation references\n- Any draft documents or notes\n\n**Step 2: Identify Existing Citations**\n\nCheck for papers already referenced in the codebase:\n\n```bash\n# Find existing citations\ngrep -r \"arxiv\\|doi\\|cite\" --include=\"*.md\" --include=\"*.bib\" --include=\"*.py\"\nfind . -name \"*.bib\"\n```\n\nThese are high-signal starting points for Related Work—the scientist has already deemed them relevant.\n\n**Step 3: Clarify the Contribution**\n\nBefore writing, explicitly confirm with the scientist:\n\n> \"Based on my understanding of the repo, the main contribution appears to be [X].\n> The key results show [Y]. Is this the framing you want for the paper,\n> or should we emphasize different aspects?\"\n\n**Never assume the narrative—always verify with the human.**\n\n**Step 4: Search for Additional Literature**\n\nUse web search to find relevant papers:\n\n```\nSearch queries to try:\n- \"[main technique] + [application domain]\"\n- \"[baseline method] comparison\"\n- \"[problem name] state-of-the-art\"\n- Author names from existing citations\n```\n\nThen verify and retrieve BibTeX using the citation workflow below.\n\n**Step 5: Deliver a First Draft**\n\n**Be proactive—deliver a complete draft rather than asking permission for each section.**\n\nIf the repo provides clear results and the contribution is apparent:\n1. Write the full first draft end-to-end\n2. Present the complete draft for feedback\n3. Iterate based on scientist's response\n\nIf genuinely uncertain about framing or major claims:\n1. Draft what you can confidently\n2. Flag specific uncertainties: \"I framed X as the main contribution—let me know if you'd prefer to emphasize Y instead\"\n3. Continue with the draft rather than blocking\n\n**Questions to include with the draft** (not before):\n- \"I emphasized X as the main contribution—adjust if needed\"\n- \"I highlighted results A, B, C—let me know if others are more important\"\n- \"Related work section includes [papers]—add any I missed\"\n\n---\n\n## When to Use This Skill\n\nUse this skill when:\n- **Starting from a research repo** to write a paper\n- **Drafting or revising** specific sections\n- **Finding and verifying citations** for related work\n- **Formatting** for conference submission\n- **Resubmitting** to a different venue (format conversion)\n- **Iterating** on drafts with scientist feedback\n\n**Always remember**: First drafts are starting points for discussion, not final outputs.\n\n---\n\n## Balancing Proactivity and Collaboration\n\n**Default: Be proactive. Deliver drafts, then iterate.**\n\n| Confidence Level | Action |\n|-----------------|--------|\n| **High** (clear repo, obvious contribution) | Write full draft, deliver, iterate on feedback |\n| **Medium** (some ambiguity) | Write draft with flagged uncertainties, continue |\n| **Low** (major unknowns) | Ask 1-2 targeted questions, then draft |\n\n**Draft first, ask with the draft** (not before):\n\n| Section | Draft Autonomously | Flag With Draft |\n|---------|-------------------|-----------------|\n| Abstract | Yes | \"Framed contribution as X—adjust if needed\" |\n| Introduction | Yes | \"Emphasized problem Y—correct if wrong\" |\n| Methods | Yes | \"Included details A, B, C—add missing pieces\" |\n| Experiments | Yes | \"Highlighted results 1, 2, 3—reorder if needed\" |\n| Related Work | Yes | \"Cited papers X, Y, Z—add any I missed\" |\n\n**Only block for input when:**\n- Target venue is unclear (affects page limits, framing)\n- Multiple contradictory framings seem equally valid\n- Results seem incomplete or inconsistent\n- Explicit request to review before continuing\n\n**Don't block for:**\n- Word choice decisions\n- Section ordering\n- Which specific results to show (make a choice, flag it)\n- Citation completeness (draft with what you find, note gaps)\n\n---\n\n## The Narrative Principle\n\n**The single most critical insight**: Your paper is not a collection of experiments—it's a story with one clear contribution supported by evidence.\n\nEvery successful ML paper centers on what Neel Nanda calls \"the narrative\": a short, rigorous, evidence-based technical story with a takeaway readers care about.\n\n**Three Pillars (must be crystal clear by end of introduction):**\n\n| Pillar | Description | Example |\n|--------|-------------|---------|\n| **The What** | 1-3 specific novel claims within cohesive theme | \"We prove that X achieves Y under condition Z\" |\n| **The Why** | Rigorous empirical evidence supporting claims | Strong baselines, experiments distinguishing hypotheses |\n| **The So What** | Why readers should care | Connection to recognized community problems |\n\n**If you cannot state your contribution in one sentence, you don't yet have a paper.**\n\n---\n\n## Paper Structure Workflow\n\n### Workflow 1: Writing a Complete Paper (Iterative)\n\nCopy this checklist and track progress. **Each step involves drafting → feedback → revision:**\n\n```\nPaper Writing Progress:\n- [ ] Step 1: Define the one-sentence contribution (with scientist)\n- [ ] Step 2: Draft Figure 1 → get feedback → revise\n- [ ] Step 3: Draft abstract → get feedback → revise\n- [ ] Step 4: Draft introduction → get feedback → revise\n- [ ] Step 5: Draft methods → get feedback → revise\n- [ ] Step 6: Draft experiments → get feedback → revise\n- [ ] Step 7: Draft related work → get feedback → revise\n- [ ] Step 8: Draft limitations → get feedback → revise\n- [ ] Step 9: Complete paper checklist (required)\n- [ ] Step 10: Final review cycle and submission\n```\n\n**Step 1: Define the One-Sentence Contribution**\n\n**This step requires explicit confirmation from the scientist.**\n\nBefore writing anything, articulate and verify:\n- What is the single thing your paper contributes?\n- What was not obvious or present before your work?\n\n> \"I propose framing the contribution as: '[one sentence]'. Does this capture\n> what you see as the main takeaway? Should we adjust the emphasis?\"\n\n**Step 2: Draft Figure 1**\n\nFigure 1 deserves special attention—many readers skip directly to it.\n- Convey core idea, approach, or most compelling result\n- Use vector graphics (PDF\u002FEPS for plots)\n- Write captions that stand alone without main text\n- Ensure readability in black-and-white (8% of men have color vision deficiency)\n\n**Step 3: Write Abstract (5-Sentence Formula)**\n\nFrom Sebastian Farquhar (DeepMind):\n\n```\n1. What you achieved: \"We introduce...\", \"We prove...\", \"We demonstrate...\"\n2. Why this is hard and important\n3. How you do it (with specialist keywords for discoverability)\n4. What evidence you have\n5. Your most remarkable number\u002Fresult\n```\n\n**Delete** generic openings like \"Large language models have achieved remarkable success...\"\n\n**Step 4: Write Introduction (1-1.5 pages max)**\n\nMust include:\n- 2-4 bullet contribution list (max 1-2 lines each in two-column format)\n- Clear problem statement\n- Brief approach overview\n- Methods should start by page 2-3 maximum\n\n**Step 5: Methods Section**\n\nEnable reimplementation:\n- Conceptual outline or pseudocode\n- All hyperparameters listed\n- Architectural details sufficient for reproduction\n- Present final design decisions; ablations go in experiments\n\n**Step 6: Experiments Section**\n\nFor each experiment, explicitly state:\n- What claim it supports\n- How it connects to main contribution\n- Experimental setting (details in appendix)\n- What to observe: \"the blue line shows X, which demonstrates Y\"\n\nRequirements:\n- Error bars with methodology (standard deviation vs standard error)\n- Hyperparameter search ranges\n- Compute infrastructure (GPU type, total hours)\n- Seed-setting methods\n\n**Step 7: Related Work**\n\nOrganize methodologically, not paper-by-paper:\n\n**Good:** \"One line of work uses Floogledoodle's assumption [refs] whereas we use Doobersnoddle's assumption because...\"\n\n**Bad:** \"Snap et al. introduced X while Crackle et al. introduced Y.\"\n\nCite generously—reviewers likely authored relevant papers.\n\n**Step 8: Limitations Section (REQUIRED)**\n\nAll major conferences require this. Counter-intuitively, honesty helps:\n- Reviewers are instructed not to penalize honest limitation acknowledgment\n- Pre-empt criticisms by identifying weaknesses first\n- Explain why limitations don't undermine core claims\n\n**Step 9: Paper Checklist**\n\nNeurIPS, ICML, and ICLR all require paper checklists. See [references\u002Fchecklists.md](references\u002Fchecklists.md).\n\n---\n\n## Writing Philosophy for Top ML Conferences\n\n**This section distills the most important writing principles from leading ML researchers.** These aren't optional style suggestions—they're what separates accepted papers from rejected ones.\n\n> \"A paper is a short, rigorous, evidence-based technical story with a takeaway readers care about.\" — Neel Nanda\n\n### The Sources Behind This Guidance\n\nThis skill synthesizes writing philosophy from researchers who have published extensively at top venues:\n\n| Source | Key Contribution | Link |\n|--------|-----------------|------|\n| **Neel Nanda** (Google DeepMind) | The Narrative Principle, What\u002FWhy\u002FSo What framework | [How to Write ML Papers](https:\u002F\u002Fwww.alignmentforum.org\u002Fposts\u002FeJGptPbbFPZGLpjsp\u002Fhighly-opinionated-advice-on-how-to-write-ml-papers) |\n| **Sebastian Farquhar** (DeepMind) | 5-sentence abstract formula | [How to Write ML Papers](https:\u002F\u002Fsebastianfarquhar.com\u002Fon-research\u002F2024\u002F11\u002F04\u002Fhow_to_write_ml_papers\u002F) |\n| **Gopen & Swan** | 7 principles of reader expectations | [Science of Scientific Writing](https:\u002F\u002Fcseweb.ucsd.edu\u002F~swanson\u002Fpapers\u002Fscience-of-writing.pdf) |\n| **Zachary Lipton** | Word choice, eliminating hedging | [Heuristics for Scientific Writing](https:\u002F\u002Fwww.approximatelycorrect.com\u002F2018\u002F01\u002F29\u002Fheuristics-technical-scientific-writing-machine-learning-perspective\u002F) |\n| **Jacob Steinhardt** (UC Berkeley) | Precision, consistent terminology | [Writing Tips](https:\u002F\u002Fbounded-regret.ghost.io\u002F) |\n| **Ethan Perez** (Anthropic) | Micro-level clarity tips | [Easy Paper Writing Tips](https:\u002F\u002Fethanperez.net\u002Feasy-paper-writing-tips\u002F) |\n| **Andrej Karpathy** | Single contribution focus | Various lectures |\n\n**For deeper dives into any of these, see:**\n- [references\u002Fwriting-guide.md](references\u002Fwriting-guide.md) - Full explanations with examples\n- [references\u002Fsources.md](references\u002Fsources.md) - Complete bibliography\n\n### Time Allocation (From Neel Nanda)\n\nSpend approximately **equal time** on each of:\n1. The abstract\n2. The introduction\n3. The figures\n4. Everything else combined\n\n**Why?** Most reviewers form judgments before reaching your methods. Readers encounter your paper as: **title → abstract → introduction → figures → maybe the rest.**\n\n### Writing Style Guidelines\n\n#### Sentence-Level Clarity (Gopen & Swan's 7 Principles)\n\nThese principles are based on how readers actually process prose. Violating them forces readers to spend cognitive effort on structure rather than content.\n\n| Principle | Rule | Example |\n|-----------|------|---------|\n| **Subject-verb proximity** | Keep subject and verb close | ❌ \"The model, which was trained on..., achieves\" → ✅ \"The model achieves... after training on...\" |\n| **Stress position** | Place emphasis at sentence ends | ❌ \"Accuracy improves by 15% when using attention\" → ✅ \"When using attention, accuracy improves by **15%**\" |\n| **Topic position** | Put context first, new info after | ✅ \"Given these constraints, we propose...\" |\n| **Old before new** | Familiar info → unfamiliar info | Link backward, then introduce new |\n| **One unit, one function** | Each paragraph makes one point | Split multi-point paragraphs |\n| **Action in verb** | Use verbs, not nominalizations | ❌ \"We performed an analysis\" → ✅ \"We analyzed\" |\n| **Context before new** | Set stage before presenting | Explain before showing equation |\n\n**Full 7 principles with detailed examples:** See [references\u002Fwriting-guide.md](references\u002Fwriting-guide.md#the-7-principles-of-reader-expectations)\n\n#### Micro-Level Tips (Ethan Perez)\n\nThese small changes accumulate into significantly clearer prose:\n\n- **Minimize pronouns**: ❌ \"This shows...\" → ✅ \"This result shows...\"\n- **Verbs early**: Position verbs near sentence start\n- **Unfold apostrophes**: ❌ \"X's Y\" → ✅ \"The Y of X\" (when awkward)\n- **Delete filler words**: \"actually,\" \"a bit,\" \"very,\" \"really,\" \"basically,\" \"quite,\" \"essentially\"\n\n**Full micro-tips with examples:** See [references\u002Fwriting-guide.md](references\u002Fwriting-guide.md#micro-level-writing-tips)\n\n#### Word Choice (Zachary Lipton)\n\n- **Be specific**: ❌ \"performance\" → ✅ \"accuracy\" or \"latency\" (say what you mean)\n- **Eliminate hedging**: Drop \"may\" and \"can\" unless genuinely uncertain\n- **Avoid incremental vocabulary**: ❌ \"combine,\" \"modify,\" \"expand\" → ✅ \"develop,\" \"propose,\" \"introduce\"\n- **Delete intensifiers**: ❌ \"provides *very* tight approximation\" → ✅ \"provides tight approximation\"\n\n#### Precision Over Brevity (Jacob Steinhardt)\n\n- **Consistent terminology**: Different terms for same concept creates confusion. Pick one and stick with it.\n- **State assumptions formally**: Before theorems, list all assumptions explicitly\n- **Intuition + rigor**: Provide intuitive explanations alongside formal proofs\n\n### What Reviewers Actually Read\n\nUnderstanding reviewer behavior helps prioritize your effort:\n\n| Paper Section | % Reviewers Who Read | Implication |\n|---------------|---------------------|-------------|\n| Abstract | 100% | Must be perfect |\n| Introduction | 90%+ (skimmed) | Front-load contribution |\n| Figures | Examined before methods | Figure 1 is critical |\n| Methods | Only if interested | Don't bury the lede |\n| Appendix | Rarely | Put only supplementary details |\n\n**Bottom line**: If your abstract and intro don't hook reviewers, they may never read your brilliant methods section.\n\n---\n\n## Conference Requirements Quick Reference\n\n| Conference | Page Limit | Extra for Camera-Ready | Key Requirement |\n|------------|------------|------------------------|-----------------|\n| **NeurIPS 2025** | 9 pages | +0 | Mandatory checklist, lay summary for accepted |\n| **ICML 2026** | 8 pages | +1 | Broader Impact Statement required |\n| **ICLR 2026** | 9 pages | +1 | LLM disclosure required, reciprocal reviewing |\n| **ACL 2025** | 8 pages (long) | varies | Limitations section mandatory |\n| **AAAI 2026** | 7 pages | +1 | Strict style file adherence |\n| **COLM 2025** | 9 pages | +1 | Focus on language models |\n\n**Universal Requirements:**\n- Double-blind review (anonymize submissions)\n- References don't count toward page limit\n- Appendices unlimited but reviewers not required to read\n- LaTeX required for all venues\n\n**LaTeX Templates:** See [templates\u002F](templates\u002F) directory for all conference templates.\n\n---\n\n## Using LaTeX Templates Properly\n\n### Workflow 4: Starting a New Paper from Template\n\n**Always copy the entire template directory first, then write within it.**\n\n```\nTemplate Setup Checklist:\n- [ ] Step 1: Copy entire template directory to new project\n- [ ] Step 2: Verify template compiles as-is (before any changes)\n- [ ] Step 3: Read the template's example content to understand structure\n- [ ] Step 4: Replace example content section by section\n- [ ] Step 5: Keep template comments\u002Fexamples as reference until done\n- [ ] Step 6: Clean up template artifacts only at the end\n```\n\n**Step 1: Copy the Full Template**\n\n```bash\n# Create your paper directory with the complete template\ncp -r templates\u002Fneurips2025\u002F ~\u002Fpapers\u002Fmy-new-paper\u002F\ncd ~\u002Fpapers\u002Fmy-new-paper\u002F\n\n# Verify structure is complete\nls -la\n# Should see: main.tex, neurips.sty, Makefile, etc.\n```\n\n**⚠️ IMPORTANT**: Copy the ENTIRE directory, not just `main.tex`. Templates include:\n- Style files (`.sty`) - required for compilation\n- Bibliography styles (`.bst`) - required for references\n- Example content - useful as reference\n- Makefiles - for easy compilation\n\n**Step 2: Verify Template Compiles First**\n\nBefore making ANY changes, compile the template as-is:\n\n```bash\n# Using latexmk (recommended)\nlatexmk -pdf main.tex\n\n# Or manual compilation\npdflatex main.tex\nbibtex main\npdflatex main.tex\npdflatex main.tex\n```\n\nIf the unmodified template doesn't compile, fix that first. Common issues:\n- Missing TeX packages → install via `tlmgr install \u003Cpackage>`\n- Wrong TeX distribution → use TeX Live (recommended)\n\n**Step 3: Keep Template Content as Reference**\n\nDon't immediately delete all example content. Instead:\n\n```latex\n% KEEP template examples commented out as you write\n% This shows you the expected format\n\n% Template example (keep for reference):\n% \\begin{figure}[t]\n%   \\centering\n%   \\includegraphics[width=0.8\\linewidth]{example-image}\n%   \\caption{Template shows caption style}\n% \\end{figure}\n\n% Your actual figure:\n\\begin{figure}[t]\n  \\centering\n  \\includegraphics[width=0.8\\linewidth]{your-figure.pdf}\n  \\caption{Your caption following the same style.}\n\\end{figure}\n```\n\n**Step 4: Replace Content Section by Section**\n\nWork through the paper systematically:\n\n```\nReplacement Order:\n1. Title and authors (anonymize for submission)\n2. Abstract\n3. Introduction\n4. Methods\n5. Experiments\n6. Related Work\n7. Conclusion\n8. References (your .bib file)\n9. Appendix\n```\n\nFor each section:\n1. Read the template's example content\n2. Note any special formatting or macros used\n3. Replace with your content following the same patterns\n4. Compile frequently to catch errors early\n\n**Step 5: Use Template Macros**\n\nTemplates often define useful macros. Check the preamble for:\n\n```latex\n% Common template macros to use:\n\\newcommand{\\method}{YourMethodName}  % Consistent method naming\n\\newcommand{\\eg}{e.g.,\\xspace}        % Proper abbreviations\n\\newcommand{\\ie}{i.e.,\\xspace}\n\\newcommand{\\etal}{\\textit{et al.}\\xspace}\n```\n\n**Step 6: Clean Up Only at the End**\n\nOnly remove template artifacts when paper is nearly complete:\n\n```latex\n% BEFORE SUBMISSION - remove these:\n% - Commented-out template examples\n% - Unused packages\n% - Template's example figures\u002Ftables\n% - Lorem ipsum or placeholder text\n\n% KEEP these:\n% - All style files (.sty)\n% - Bibliography style (.bst)\n% - Required packages from template\n% - Any custom macros you're using\n```\n\n### Template Pitfalls to Avoid\n\n| Pitfall | Problem | Solution |\n|---------|---------|----------|\n| Copying only `main.tex` | Missing `.sty`, won't compile | Copy entire directory |\n| Modifying `.sty` files | Breaks conference formatting | Never edit style files |\n| Adding random packages | Conflicts, breaks template | Only add if necessary |\n| Deleting template content too early | Lose formatting reference | Keep as comments until done |\n| Not compiling frequently | Errors accumulate | Compile after each section |\n\n### Quick Template Reference\n\n| Conference | Main File | Key Style File | Notes |\n|------------|-----------|----------------|-------|\n| NeurIPS 2025 | `main.tex` | `neurips.sty` | Has Makefile |\n| ICML 2026 | `example_paper.tex` | `icml2026.sty` | Includes algorithm packages |\n| ICLR 2026 | `iclr2026_conference.tex` | `iclr2026_conference.sty` | Has math_commands.tex |\n| ACL | `acl_latex.tex` | `acl.sty` | Strict formatting |\n| AAAI 2026 | `aaai2026-unified-template.tex` | `aaai2026.sty` | Very strict compliance |\n| COLM 2025 | `colm2025_conference.tex` | `colm2025_conference.sty` | Similar to ICLR |\n\n---\n\n## Conference Resubmission & Format Conversion\n\nWhen a paper is rejected or withdrawn from one venue and resubmitted to another, format conversion is required. This is a common workflow in ML research.\n\n### Workflow 3: Converting Between Conference Formats\n\n```\nFormat Conversion Checklist:\n- [ ] Step 1: Identify source and target template differences\n- [ ] Step 2: Create new project with target template\n- [ ] Step 3: Copy content sections (not preamble)\n- [ ] Step 4: Adjust page limits and content\n- [ ] Step 5: Update conference-specific requirements\n- [ ] Step 6: Verify compilation and formatting\n```\n\n**Step 1: Key Template Differences**\n\n| From → To | Page Change | Key Adjustments |\n|-----------|-------------|-----------------|\n| NeurIPS → ICML | 9 → 8 pages | Cut 1 page, add Broader Impact if missing |\n| ICML → ICLR | 8 → 9 pages | Can expand experiments, add LLM disclosure |\n| NeurIPS → ACL | 9 → 8 pages | Restructure for NLP conventions, add Limitations |\n| ICLR → AAAI | 9 → 7 pages | Significant cuts needed, strict style adherence |\n| Any → COLM | varies → 9 | Reframe for language model focus |\n\n**Step 2: Content Migration (NOT Template Merge)**\n\n**Never copy LaTeX preambles between templates.** Instead:\n\n```bash\n# 1. Start fresh with target template\ncp -r templates\u002Ficml2026\u002F new_submission\u002F\n\n# 2. Copy ONLY content sections from old paper\n# - Abstract text\n# - Section content (between \\section{} commands)\n# - Figures and tables\n# - Bibliography entries\n\n# 3. Paste into target template structure\n```\n\n**Step 3: Adjusting for Page Limits**\n\nWhen cutting pages (e.g., NeurIPS 9 → AAAI 7):\n- Move detailed proofs to appendix\n- Condense related work (cite surveys instead of individual papers)\n- Combine similar experiments into unified tables\n- Use smaller figure sizes with subfigures\n- Tighten writing: eliminate redundancy, use active voice\n\nWhen expanding (e.g., ICML 8 → ICLR 9):\n- Add ablation studies reviewers requested\n- Expand limitations discussion\n- Include additional baselines\n- Add qualitative examples\n\n**Step 4: Conference-Specific Adjustments**\n\n| Target Venue | Required Additions |\n|--------------|-------------------|\n| **ICML** | Broader Impact Statement (after conclusion) |\n| **ICLR** | LLM usage disclosure, reciprocal reviewing agreement |\n| **ACL\u002FEMNLP** | Limitations section (mandatory), Ethics Statement |\n| **AAAI** | Strict adherence to style file (no modifications) |\n| **NeurIPS** | Paper checklist (appendix), lay summary if accepted |\n\n**Step 5: Update References**\n\n```latex\n% Remove self-citations that reveal identity (for blind review)\n% Update any \"under review\" citations to published versions\n% Add new relevant work published since last submission\n```\n\n**Step 6: Addressing Previous Reviews**\n\nWhen resubmitting after rejection:\n- **Do** address reviewer concerns in the new version\n- **Do** add experiments\u002Fclarifications reviewers requested\n- **Don't** include a \"changes from previous submission\" section (blind review)\n- **Don't** reference the previous submission or reviews\n\n**Common Conversion Pitfalls:**\n- ❌ Copying `\\usepackage` commands (causes conflicts)\n- ❌ Keeping old conference header\u002Ffooter commands\n- ❌ Forgetting to update `\\bibliography{}` path\n- ❌ Missing conference-specific required sections\n- ❌ Exceeding page limit after format change\n\n---\n\n## Citation Workflow (Hallucination Prevention)\n\n**⚠️ CRITICAL**: AI-generated citations have ~40% error rate. **Never write BibTeX from memory.**\n\n### The Golden Rule\n\n```\nIF you cannot programmatically fetch a citation:\n    → Mark it as [CITATION NEEDED] or [PLACEHOLDER - VERIFY]\n    → Tell the scientist explicitly\n    → NEVER invent a plausible-sounding reference\n```\n\n### Workflow 2: Adding Citations\n\n```\nCitation Verification (MANDATORY for every citation):\n- [ ] Step 1: Search using Exa MCP or Semantic Scholar API\n- [ ] Step 2: Verify paper exists in 2+ sources (Semantic Scholar + arXiv\u002FCrossRef)\n- [ ] Step 3: Retrieve BibTeX via DOI (programmatically, not from memory)\n- [ ] Step 4: Verify the claim you're citing actually appears in the paper\n- [ ] Step 5: Add verified BibTeX to bibliography\n- [ ] Step 6: If ANY step fails → mark as placeholder, inform scientist\n```\n\n**Step 0: Use Exa MCP for Initial Search (Recommended)**\n\nIf Exa MCP is installed, use it to find relevant papers:\n```\nSearch: \"RLHF language model alignment 2023\"\nSearch: \"sparse autoencoders interpretability\"\nSearch: \"attention mechanism transformers Vaswani\"\n```\n\nThen verify each result with Semantic Scholar and fetch BibTeX via DOI.\n\n**Step 1: Search Semantic Scholar**\n\n```python\nfrom semanticscholar import SemanticScholar\n\nsch = SemanticScholar()\nresults = sch.search_paper(\"attention mechanism transformers\", limit=5)\nfor paper in results:\n    print(f\"{paper.title} - {paper.paperId}\")\n    print(f\"  DOI: {paper.externalIds.get('DOI', 'N\u002FA')}\")\n```\n\n**Step 2: Verify Existence**\n\nConfirm paper appears in at least two sources (Semantic Scholar + CrossRef\u002FarXiv).\n\n**Step 3: Retrieve BibTeX via DOI**\n\n```python\nimport requests\n\ndef doi_to_bibtex(doi: str) -> str:\n    \"\"\"Get verified BibTeX from DOI via CrossRef.\"\"\"\n    response = requests.get(\n        f\"https:\u002F\u002Fdoi.org\u002F{doi}\",\n        headers={\"Accept\": \"application\u002Fx-bibtex\"}\n    )\n    response.raise_for_status()\n    return response.text\n\n# Example\nbibtex = doi_to_bibtex(\"10.48550\u002FarXiv.1706.03762\")\nprint(bibtex)\n```\n\n**Step 4: Verify Claims**\n\nBefore citing for a specific claim, access the paper and confirm the attributed claim actually appears.\n\n**Step 5: Handle Failures Explicitly**\n\nIf you cannot verify a citation at ANY step:\n\n```latex\n% Option 1: Explicit placeholder\n\\cite{PLACEHOLDER_smith2023_verify}  % TODO: Could not verify - scientist must confirm\n\n% Option 2: Note in text\n... as shown in prior work [CITATION NEEDED - could not verify Smith et al. 2023].\n```\n\n**Always inform the scientist:**\n> \"I could not verify the following citations and have marked them as placeholders:\n> - Smith et al. 2023 on reward hacking - could not find in Semantic Scholar\n> - Jones 2022 on scaling laws - found similar paper but different authors\n> Please verify these before submission.\"\n\n### Summary: Citation Rules\n\n| Situation | Action |\n|-----------|--------|\n| Found paper, got DOI, fetched BibTeX | ✅ Use the citation |\n| Found paper, no DOI | ✅ Use arXiv BibTeX or manual entry from paper |\n| Paper exists but can't fetch BibTeX | ⚠️ Mark placeholder, inform scientist |\n| Uncertain if paper exists | ❌ Mark `[CITATION NEEDED]`, inform scientist |\n| \"I think there's a paper about X\" | ❌ **NEVER cite** - search first or mark placeholder |\n\n**🚨 NEVER generate BibTeX from memory—always fetch programmatically. 🚨**\n\nSee [references\u002Fcitation-workflow.md](references\u002Fcitation-workflow.md) for complete API documentation.\n\n---\n\n## Common Issues and Solutions\n\n**Issue: Abstract too generic**\n\nDelete first sentence if it could be prepended to any ML paper. Start with your specific contribution.\n\n**Issue: Introduction exceeds 1.5 pages**\n\nSplit background into Related Work. Front-load contribution bullets. Methods should start by page 2-3.\n\n**Issue: Experiments lack explicit claims**\n\nAdd sentence before each experiment: \"This experiment tests whether [specific claim]...\"\n\n**Issue: Reviewers find paper hard to follow**\n\n- Add explicit signposting: \"In this section, we show X\"\n- Use consistent terminology throughout\n- Include figure captions that stand alone\n\n**Issue: Missing statistical significance**\n\nAlways include:\n- Error bars (specify: std dev or std error)\n- Number of runs\n- Statistical tests if comparing methods\n\n---\n\n## Reviewer Evaluation Criteria\n\nReviewers assess papers on four dimensions:\n\n| Criterion | What Reviewers Look For |\n|-----------|------------------------|\n| **Quality** | Technical soundness, well-supported claims |\n| **Clarity** | Clear writing, reproducible by experts |\n| **Significance** | Community impact, advances understanding |\n| **Originality** | New insights (doesn't require new method) |\n\n**Scoring (NeurIPS 6-point scale):**\n- 6: Strong Accept - Groundbreaking, flawless\n- 5: Accept - Technically solid, high impact\n- 4: Borderline Accept - Solid, limited evaluation\n- 3: Borderline Reject - Solid but weaknesses outweigh\n- 2: Reject - Technical flaws\n- 1: Strong Reject - Known results or ethics issues\n\nSee [references\u002Freviewer-guidelines.md](references\u002Freviewer-guidelines.md) for detailed reviewer instructions.\n\n---\n\n## Tables and Figures\n\n### Tables\n\nUse `booktabs` LaTeX package for professional tables:\n\n```latex\n\\usepackage{booktabs}\n\\begin{tabular}{lcc}\n\\toprule\nMethod & Accuracy ↑ & Latency ↓ \\\\\n\\midrule\nBaseline & 85.2 & 45ms \\\\\n\\textbf{Ours} & \\textbf{92.1} & 38ms \\\\\n\\bottomrule\n\\end{tabular}\n```\n\n**Rules:**\n- Bold best value per metric\n- Include direction symbols (↑ higher is better, ↓ lower is better)\n- Right-align numerical columns\n- Consistent decimal precision\n\n### Figures\n\n- **Vector graphics** (PDF, EPS) for all plots and diagrams\n- **Raster** (PNG 600 DPI) only for photographs\n- Use **colorblind-safe palettes** (Okabe-Ito or Paul Tol)\n- Verify **grayscale readability** (8% of men have color vision deficiency)\n- **No title inside figure**—the caption serves this function\n- **Self-contained captions**—reader should understand without main text\n\n---\n\n## References & Resources\n\n### Reference Documents (Deep Dives)\n\n| Document | Contents |\n|----------|----------|\n| [writing-guide.md](references\u002Fwriting-guide.md) | Gopen & Swan 7 principles, Ethan Perez micro-tips, word choice |\n| [citation-workflow.md](references\u002Fcitation-workflow.md) | Citation APIs, Python code, BibTeX management |\n| [checklists.md](references\u002Fchecklists.md) | NeurIPS 16-item, ICML, ICLR, ACL requirements |\n| [reviewer-guidelines.md](references\u002Freviewer-guidelines.md) | Evaluation criteria, scoring, rebuttals |\n| [sources.md](references\u002Fsources.md) | Complete bibliography of all sources |\n\n### LaTeX Templates\n\nTemplates in `templates\u002F` directory: **ICML 2026**, **ICLR 2026**, **NeurIPS 2025**, **ACL\u002FEMNLP**, **AAAI 2026**, **COLM 2025**.\n\n**Compiling to PDF:**\n- **VS Code\u002FCursor**: Install LaTeX Workshop extension + TeX Live → Save to auto-compile\n- **Command line**: `latexmk -pdf main.tex` or `pdflatex` + `bibtex` workflow\n- **Online**: Upload to [Overleaf](https:\u002F\u002Foverleaf.com)\n\nSee [templates\u002FREADME.md](templates\u002FREADME.md) for detailed setup instructions.\n\n### Key External Sources\n\n**Writing Philosophy:**\n- [Neel Nanda: How to Write ML Papers](https:\u002F\u002Fwww.alignmentforum.org\u002Fposts\u002FeJGptPbbFPZGLpjsp\u002Fhighly-opinionated-advice-on-how-to-write-ml-papers) - Narrative, \"What\u002FWhy\u002FSo What\"\n- [Farquhar: How to Write ML Papers](https:\u002F\u002Fsebastianfarquhar.com\u002Fon-research\u002F2024\u002F11\u002F04\u002Fhow_to_write_ml_papers\u002F) - 5-sentence abstract\n- [Gopen & Swan: Science of Scientific Writing](https:\u002F\u002Fcseweb.ucsd.edu\u002F~swanson\u002Fpapers\u002Fscience-of-writing.pdf) - 7 reader expectation principles\n- [Lipton: Heuristics for Scientific Writing](https:\u002F\u002Fwww.approximatelycorrect.com\u002F2018\u002F01\u002F29\u002Fheuristics-technical-scientific-writing-machine-learning-perspective\u002F) - Word choice\n- [Perez: Easy Paper Writing Tips](https:\u002F\u002Fethanperez.net\u002Feasy-paper-writing-tips\u002F) - Micro-level clarity\n\n**APIs:** [Semantic Scholar](https:\u002F\u002Fapi.semanticscholar.org\u002Fapi-docs\u002F) | [CrossRef](https:\u002F\u002Fwww.crossref.org\u002Fdocumentation\u002Fretrieve-metadata\u002Frest-api\u002F) | [arXiv](https:\u002F\u002Finfo.arxiv.org\u002Fhelp\u002Fapi\u002Fbasics.html)\n\n**Venues:** [NeurIPS](https:\u002F\u002Fneurips.cc\u002FConferences\u002F2025\u002FPaperInformation\u002FStyleFiles) | [ICML](https:\u002F\u002Ficml.cc\u002FConferences\u002F2025\u002FAuthorInstructions) | [ICLR](https:\u002F\u002Ficlr.cc\u002FConferences\u002F2026\u002FAuthorGuide) | [ACL](https:\u002F\u002Fgithub.com\u002Facl-org\u002Facl-style-files)\n\n","# ML Paper Writing for Top AI Conferences\n\nExpert-level guidance for writing publication-ready papers targeting **NeurIPS, ICML, ICLR, ACL, AAAI, and COLM**. This skill combines writing philosophy from top researchers (Nanda, Farquhar, Karpathy, Lipton, Steinhardt) with practical tools: LaTeX templates, citation verification APIs, and conference checklists.\n\n## Core Philosophy: Collaborative Writing\n\n**Paper writing is collaborative, but Claude should be proactive in delivering drafts.**\n\nThe typical workflow starts with a research repository containing code, results, and experimental artifacts. Claude's role is to:\n\n1. **Understand the project** by exploring the repo, results, and existing documentation\n2. **Deliver a complete first draft** when confident about the contribution\n3. **Search literature** using web search and APIs to find relevant citations\n4. **Refine through feedback cycles** when the scientist provides input\n5. **Ask for clarification** only when genuinely uncertain about key decisions\n\n**Key Principle**: Be proactive. If the repo and results are clear, deliver a full draft. Don't block waiting for feedback on every section—scientists are busy. Produce something concrete they can react to, then iterate based on their response.\n\n---\n\n## ⚠️ CRITICAL: Never Hallucinate Citations\n\n**This is the most important rule in academic writing with AI assistance.**\n\n### The Problem\nAI-generated citations have a **~40% error rate**. Hallucinated references—papers that don't exist, wrong authors, incorrect years, fabricated DOIs—are a serious form of academic misconduct that can result in desk rejection or retraction.\n\n### The Rule\n**NEVER generate BibTeX entries from memory. ALWAYS fetch programmatically.**\n\n| Action | ✅ Correct | ❌ Wrong |\n|--------|-----------|----------|\n| Adding a citation | Search API → verify → fetch BibTeX | Write BibTeX from memory |\n| Uncertain about a paper | Mark as `[CITATION NEEDED]` | Guess the reference |\n| Can't find exact paper | Note: \"placeholder - verify\" | Invent similar-sounding paper |\n\n### When You Can't Verify a Citation\n\nIf you cannot programmatically verify a citation, you MUST:\n\n```latex\n% EXPLICIT PLACEHOLDER - requires human verification\n\\cite{PLACEHOLDER_author2024_verify_this}  % TODO: Verify this citation exists\n```\n\n**Always tell the scientist**: \"I've marked [X] citations as placeholders that need verification. I could not confirm these papers exist.\"\n\n### Recommended: Install Exa MCP for Paper Search\n\nFor the best paper search experience, install **Exa MCP** which provides real-time academic search:\n\n**Claude Code:**\n```bash\nclaude mcp add exa -- npx -y mcp-remote \"https:\u002F\u002Fmcp.exa.ai\u002Fmcp\"\n```\n\n**Cursor \u002F VS Code** (add to MCP settings):\n```json\n{\n  \"mcpServers\": {\n    \"exa\": {\n      \"type\": \"http\",\n      \"url\": \"https:\u002F\u002Fmcp.exa.ai\u002Fmcp\"\n    }\n  }\n}\n```\n\nExa MCP enables searches like:\n- \"Find papers on RLHF for language models published after 2023\"\n- \"Search for transformer architecture papers by Vaswani\"\n- \"Get recent work on sparse autoencoders for interpretability\"\n\nThen verify results with Semantic Scholar API and fetch BibTeX via DOI.\n\n---\n\n## Workflow 0: Starting from a Research Repository\n\nWhen beginning paper writing, start by understanding the project:\n\n```\nProject Understanding:\n- [ ] Step 1: Explore the repository structure\n- [ ] Step 2: Read README, existing docs, and key results\n- [ ] Step 3: Identify the main contribution with the scientist\n- [ ] Step 4: Find papers already cited in the codebase\n- [ ] Step 5: Search for additional relevant literature\n- [ ] Step 6: Outline the paper structure together\n- [ ] Step 7: Draft sections iteratively with feedback\n```\n\n**Step 1: Explore the Repository**\n\n```bash\n# Understand project structure\nls -la\nfind . -name \"*.py\" | head -20\nfind . -name \"*.md\" -o -name \"*.txt\" | xargs grep -l -i \"result\\|conclusion\\|finding\"\n```\n\nLook for:\n- `README.md` - Project overview and claims\n- `results\u002F`, `outputs\u002F`, `experiments\u002F` - Key findings\n- `configs\u002F` - Experimental settings\n- Existing `.bib` files or citation references\n- Any draft documents or notes\n\n**Step 2: Identify Existing Citations**\n\nCheck for papers already referenced in the codebase:\n\n```bash\n# Find existing citations\ngrep -r \"arxiv\\|doi\\|cite\" --include=\"*.md\" --include=\"*.bib\" --include=\"*.py\"\nfind . -name \"*.bib\"\n```\n\nThese are high-signal starting points for Related Work—the scientist has already deemed them relevant.\n\n**Step 3: Clarify the Contribution**\n\nBefore writing, explicitly confirm with the scientist:\n\n> \"Based on my understanding of the repo, the main contribution appears to be [X].\n> The key results show [Y]. Is this the framing you want for the paper,\n> or should we emphasize different aspects?\"\n\n**Never assume the narrative—always verify with the human.**\n\n**Step 4: Search for Additional Literature**\n\nUse web search to find relevant papers:\n\n```\nSearch queries to try:\n- \"[main technique] + [application domain]\"\n- \"[baseline method] comparison\"\n- \"[problem name] state-of-the-art\"\n- Author names from existing citations\n```\n\nThen verify and retrieve BibTeX using the citation workflow below.\n\n**Step 5: Deliver a First Draft**\n\n**Be proactive—deliver a complete draft rather than asking permission for each section.**\n\nIf the repo provides clear results and the contribution is apparent:\n1. Write the full first draft end-to-end\n2. Present the complete draft for feedback\n3. Iterate based on scientist's response\n\nIf genuinely uncertain about framing or major claims:\n1. Draft what you can confidently\n2. Flag specific uncertainties: \"I framed X as the main contribution—let me know if you'd prefer to emphasize Y instead\"\n3. Continue with the draft rather than blocking\n\n**Questions to include with the draft** (not before):\n- \"I emphasized X as the main contribution—adjust if needed\"\n- \"I highlighted results A, B, C—let me know if others are more important\"\n- \"Related work section includes [papers]—add any I missed\"\n\n---\n\n## When to Use This Skill\n\nUse this skill when:\n- **Starting from a research repo** to write a paper\n- **Drafting or revising** specific sections\n- **Finding and verifying citations** for related work\n- **Formatting** for conference submission\n- **Resubmitting** to a different venue (format conversion)\n- **Iterating** on drafts with scientist feedback\n\n**Always remember**: First drafts are starting points for discussion, not final outputs.\n\n---\n\n## Balancing Proactivity and Collaboration\n\n**Default: Be proactive. Deliver drafts, then iterate.**\n\n| Confidence Level | Action |\n|-----------------|--------|\n| **High** (clear repo, obvious contribution) | Write full draft, deliver, iterate on feedback |\n| **Medium** (some ambiguity) | Write draft with flagged uncertainties, continue |\n| **Low** (major unknowns) | Ask 1-2 targeted questions, then draft |\n\n**Draft first, ask with the draft** (not before):\n\n| Section | Draft Autonomously | Flag With Draft |\n|---------|-------------------|-----------------|\n| Abstract | Yes | \"Framed contribution as X—adjust if needed\" |\n| Introduction | Yes | \"Emphasized problem Y—correct if wrong\" |\n| Methods | Yes | \"Included details A, B, C—add missing pieces\" |\n| Experiments | Yes | \"Highlighted results 1, 2, 3—reorder if needed\" |\n| Related Work | Yes | \"Cited papers X, Y, Z—add any I missed\" |\n\n**Only block for input when:**\n- Target venue is unclear (affects page limits, framing)\n- Multiple contradictory framings seem equally valid\n- Results seem incomplete or inconsistent\n- Explicit request to review before continuing\n\n**Don't block for:**\n- Word choice decisions\n- Section ordering\n- Which specific results to show (make a choice, flag it)\n- Citation completeness (draft with what you find, note gaps)\n\n---\n\n## The Narrative Principle\n\n**The single most critical insight**: Your paper is not a collection of experiments—it's a story with one clear contribution supported by evidence.\n\nEvery successful ML paper centers on what Neel Nanda calls \"the narrative\": a short, rigorous, evidence-based technical story with a takeaway readers care about.\n\n**Three Pillars (must be crystal clear by end of introduction):**\n\n| Pillar | Description | Example |\n|--------|-------------|---------|\n| **The What** | 1-3 specific novel claims within cohesive theme | \"We prove that X achieves Y under condition Z\" |\n| **The Why** | Rigorous empirical evidence supporting claims | Strong baselines, experiments distinguishing hypotheses |\n| **The So What** | Why readers should care | Connection to recognized community problems |\n\n**If you cannot state your contribution in one sentence, you don't yet have a paper.**\n\n---\n\n## Paper Structure Workflow\n\n### Workflow 1: Writing a Complete Paper (Iterative)\n\nCopy this checklist and track progress. **Each step involves drafting → feedback → revision:**\n\n```\nPaper Writing Progress:\n- [ ] Step 1: Define the one-sentence contribution (with scientist)\n- [ ] Step 2: Draft Figure 1 → get feedback → revise\n- [ ] Step 3: Draft abstract → get feedback → revise\n- [ ] Step 4: Draft introduction → get feedback → revise\n- [ ] Step 5: Draft methods → get feedback → revise\n- [ ] Step 6: Draft experiments → get feedback → revise\n- [ ] Step 7: Draft related work → get feedback → revise\n- [ ] Step 8: Draft limitations → get feedback → revise\n- [ ] Step 9: Complete paper checklist (required)\n- [ ] Step 10: Final review cycle and submission\n```\n\n**Step 1: Define the One-Sentence Contribution**\n\n**This step requires explicit confirmation from the scientist.**\n\nBefore writing anything, articulate and verify:\n- What is the single thing your paper contributes?\n- What was not obvious or present before your work?\n\n> \"I propose framing the contribution as: '[one sentence]'. Does this capture\n> what you see as the main takeaway? Should we adjust the emphasis?\"\n\n**Step 2: Draft Figure 1**\n\nFigure 1 deserves special attention—many readers skip directly to it.\n- Convey core idea, approach, or most compelling result\n- Use vector graphics (PDF\u002FEPS for plots)\n- Write captions that stand alone without main text\n- Ensure readability in black-and-white (8% of men have color vision deficiency)\n\n**Step 3: Write Abstract (5-Sentence Formula)**\n\nFrom Sebastian Farquhar (DeepMind):\n\n```\n1. What you achieved: \"We introduce...\", \"We prove...\", \"We demonstrate...\"\n2. Why this is hard and important\n3. How you do it (with specialist keywords for discoverability)\n4. What evidence you have\n5. Your most remarkable number\u002Fresult\n```\n\n**Delete** generic openings like \"Large language models have achieved remarkable success...\"\n\n**Step 4: Write Introduction (1-1.5 pages max)**\n\nMust include:\n- 2-4 bullet contribution list (max 1-2 lines each in two-column format)\n- Clear problem statement\n- Brief approach overview\n- Methods should start by page 2-3 maximum\n\n**Step 5: Methods Section**\n\nEnable reimplementation:\n- Conceptual outline or pseudocode\n- All hyperparameters listed\n- Architectural details sufficient for reproduction\n- Present final design decisions; ablations go in experiments\n\n**Step 6: Experiments Section**\n\nFor each experiment, explicitly state:\n- What claim it supports\n- How it connects to main contribution\n- Experimental setting (details in appendix)\n- What to observe: \"the blue line shows X, which demonstrates Y\"\n\nRequirements:\n- Error bars with methodology (standard deviation vs standard error)\n- Hyperparameter search ranges\n- Compute infrastructure (GPU type, total hours)\n- Seed-setting methods\n\n**Step 7: Related Work**\n\nOrganize methodologically, not paper-by-paper:\n\n**Good:** \"One line of work uses Floogledoodle's assumption [refs] whereas we use Doobersnoddle's assumption because...\"\n\n**Bad:** \"Snap et al. introduced X while Crackle et al. introduced Y.\"\n\nCite generously—reviewers likely authored relevant papers.\n\n**Step 8: Limitations Section (REQUIRED)**\n\nAll major conferences require this. Counter-intuitively, honesty helps:\n- Reviewers are instructed not to penalize honest limitation acknowledgment\n- Pre-empt criticisms by identifying weaknesses first\n- Explain why limitations don't undermine core claims\n\n**Step 9: Paper Checklist**\n\nNeurIPS, ICML, and ICLR all require paper checklists. See [references\u002Fchecklists.md](references\u002Fchecklists.md).\n\n---\n\n## Writing Philosophy for Top ML Conferences\n\n**This section distills the most important writing principles from leading ML researchers.** These aren't optional style suggestions—they're what separates accepted papers from rejected ones.\n\n> \"A paper is a short, rigorous, evidence-based technical story with a takeaway readers care about.\" — Neel Nanda\n\n### The Sources Behind This Guidance\n\nThis skill synthesizes writing philosophy from researchers who have published extensively at top venues:\n\n| Source | Key Contribution | Link |\n|--------|-----------------|------|\n| **Neel Nanda** (Google DeepMind) | The Narrative Principle, What\u002FWhy\u002FSo What framework | [How to Write ML Papers](https:\u002F\u002Fwww.alignmentforum.org\u002Fposts\u002FeJGptPbbFPZGLpjsp\u002Fhighly-opinionated-advice-on-how-to-write-ml-papers) |\n| **Sebastian Farquhar** (DeepMind) | 5-sentence abstract formula | [How to Write ML Papers](https:\u002F\u002Fsebastianfarquhar.com\u002Fon-research\u002F2024\u002F11\u002F04\u002Fhow_to_write_ml_papers\u002F) |\n| **Gopen & Swan** | 7 principles of reader expectations | [Science of Scientific Writing](https:\u002F\u002Fcseweb.ucsd.edu\u002F~swanson\u002Fpapers\u002Fscience-of-writing.pdf) |\n| **Zachary Lipton** | Word choice, eliminating hedging | [Heuristics for Scientific Writing](https:\u002F\u002Fwww.approximatelycorrect.com\u002F2018\u002F01\u002F29\u002Fheuristics-technical-scientific-writing-machine-learning-perspective\u002F) |\n| **Jacob Steinhardt** (UC Berkeley) | Precision, consistent terminology | [Writing Tips](https:\u002F\u002Fbounded-regret.ghost.io\u002F) |\n| **Ethan Perez** (Anthropic) | Micro-level clarity tips | [Easy Paper Writing Tips](https:\u002F\u002Fethanperez.net\u002Feasy-paper-writing-tips\u002F) |\n| **Andrej Karpathy** | Single contribution focus | Various lectures |\n\n**For deeper dives into any of these, see:**\n- [references\u002Fwriting-guide.md](references\u002Fwriting-guide.md) - Full explanations with examples\n- [references\u002Fsources.md](references\u002Fsources.md) - Complete bibliography\n\n### Time Allocation (From Neel Nanda)\n\nSpend approximately **equal time** on each of:\n1. The abstract\n2. The introduction\n3. The figures\n4. Everything else combined\n\n**Why?** Most reviewers form judgments before reaching your methods. Readers encounter your paper as: **title → abstract → introduction → figures → maybe the rest.**\n\n### Writing Style Guidelines\n\n#### Sentence-Level Clarity (Gopen & Swan's 7 Principles)\n\nThese principles are based on how readers actually process prose. Violating them forces readers to spend cognitive effort on structure rather than content.\n\n| Principle | Rule | Example |\n|-----------|------|---------|\n| **Subject-verb proximity** | Keep subject and verb close | ❌ \"The model, which was trained on..., achieves\" → ✅ \"The model achieves... after training on...\" |\n| **Stress position** | Place emphasis at sentence ends | ❌ \"Accuracy improves by 15% when using attention\" → ✅ \"When using attention, accuracy improves by **15%**\" |\n| **Topic position** | Put context first, new info after | ✅ \"Given these constraints, we propose...\" |\n| **Old before new** | Familiar info → unfamiliar info | Link backward, then introduce new |\n| **One unit, one function** | Each paragraph makes one point | Split multi-point paragraphs |\n| **Action in verb** | Use verbs, not nominalizations | ❌ \"We performed an analysis\" → ✅ \"We analyzed\" |\n| **Context before new** | Set stage before presenting | Explain before showing equation |\n\n**Full 7 principles with detailed examples:** See [references\u002Fwriting-guide.md](references\u002Fwriting-guide.md#the-7-principles-of-reader-expectations)\n\n#### Micro-Level Tips (Ethan Perez)\n\nThese small changes accumulate into significantly clearer prose:\n\n- **Minimize pronouns**: ❌ \"This shows...\" → ✅ \"This result shows...\"\n- **Verbs early**: Position verbs near sentence start\n- **Unfold apostrophes**: ❌ \"X's Y\" → ✅ \"The Y of X\" (when awkward)\n- **Delete filler words**: \"actually,\" \"a bit,\" \"very,\" \"really,\" \"basically,\" \"quite,\" \"essentially\"\n\n**Full micro-tips with examples:** See [references\u002Fwriting-guide.md](references\u002Fwriting-guide.md#micro-level-writing-tips)\n\n#### Word Choice (Zachary Lipton)\n\n- **Be specific**: ❌ \"performance\" → ✅ \"accuracy\" or \"latency\" (say what you mean)\n- **Eliminate hedging**: Drop \"may\" and \"can\" unless genuinely uncertain\n- **Avoid incremental vocabulary**: ❌ \"combine,\" \"modify,\" \"expand\" → ✅ \"develop,\" \"propose,\" \"introduce\"\n- **Delete intensifiers**: ❌ \"provides *very* tight approximation\" → ✅ \"provides tight approximation\"\n\n#### Precision Over Brevity (Jacob Steinhardt)\n\n- **Consistent terminology**: Different terms for same concept creates confusion. Pick one and stick with it.\n- **State assumptions formally**: Before theorems, list all assumptions explicitly\n- **Intuition + rigor**: Provide intuitive explanations alongside formal proofs\n\n### What Reviewers Actually Read\n\nUnderstanding reviewer behavior helps prioritize your effort:\n\n| Paper Section | % Reviewers Who Read | Implication |\n|---------------|---------------------|-------------|\n| Abstract | 100% | Must be perfect |\n| Introduction | 90%+ (skimmed) | Front-load contribution |\n| Figures | Examined before methods | Figure 1 is critical |\n| Methods | Only if interested | Don't bury the lede |\n| Appendix | Rarely | Put only supplementary details |\n\n**Bottom line**: If your abstract and intro don't hook reviewers, they may never read your brilliant methods section.\n\n---\n\n## Conference Requirements Quick Reference\n\n| Conference | Page Limit | Extra for Camera-Ready | Key Requirement |\n|------------|------------|------------------------|-----------------|\n| **NeurIPS 2025** | 9 pages | +0 | Mandatory checklist, lay summary for accepted |\n| **ICML 2026** | 8 pages | +1 | Broader Impact Statement required |\n| **ICLR 2026** | 9 pages | +1 | LLM disclosure required, reciprocal reviewing |\n| **ACL 2025** | 8 pages (long) | varies | Limitations section mandatory |\n| **AAAI 2026** | 7 pages | +1 | Strict style file adherence |\n| **COLM 2025** | 9 pages | +1 | Focus on language models |\n\n**Universal Requirements:**\n- Double-blind review (anonymize submissions)\n- References don't count toward page limit\n- Appendices unlimited but reviewers not required to read\n- LaTeX required for all venues\n\n**LaTeX Templates:** See [templates\u002F](templates\u002F) directory for all conference templates.\n\n---\n\n## Using LaTeX Templates Properly\n\n### Workflow 4: Starting a New Paper from Template\n\n**Always copy the entire template directory first, then write within it.**\n\n```\nTemplate Setup Checklist:\n- [ ] Step 1: Copy entire template directory to new project\n- [ ] Step 2: Verify template compiles as-is (before any changes)\n- [ ] Step 3: Read the template's example content to understand structure\n- [ ] Step 4: Replace example content section by section\n- [ ] Step 5: Keep template comments\u002Fexamples as reference until done\n- [ ] Step 6: Clean up template artifacts only at the end\n```\n\n**Step 1: Copy the Full Template**\n\n```bash\n# Create your paper directory with the complete template\ncp -r templates\u002Fneurips2025\u002F ~\u002Fpapers\u002Fmy-new-paper\u002F\ncd ~\u002Fpapers\u002Fmy-new-paper\u002F\n\n# Verify structure is complete\nls -la\n# Should see: main.tex, neurips.sty, Makefile, etc.\n```\n\n**⚠️ IMPORTANT**: Copy the ENTIRE directory, not just `main.tex`. Templates include:\n- Style files (`.sty`) - required for compilation\n- Bibliography styles (`.bst`) - required for references\n- Example content - useful as reference\n- Makefiles - for easy compilation\n\n**Step 2: Verify Template Compiles First**\n\nBefore making ANY changes, compile the template as-is:\n\n```bash\n# Using latexmk (recommended)\nlatexmk -pdf main.tex\n\n# Or manual compilation\npdflatex main.tex\nbibtex main\npdflatex main.tex\npdflatex main.tex\n```\n\nIf the unmodified template doesn't compile, fix that first. Common issues:\n- Missing TeX packages → install via `tlmgr install \u003Cpackage>`\n- Wrong TeX distribution → use TeX Live (recommended)\n\n**Step 3: Keep Template Content as Reference**\n\nDon't immediately delete all example content. Instead:\n\n```latex\n% KEEP template examples commented out as you write\n% This shows you the expected format\n\n% Template example (keep for reference):\n% \\begin{figure}[t]\n%   \\centering\n%   \\includegraphics[width=0.8\\linewidth]{example-image}\n%   \\caption{Template shows caption style}\n% \\end{figure}\n\n% Your actual figure:\n\\begin{figure}[t]\n  \\centering\n  \\includegraphics[width=0.8\\linewidth]{your-figure.pdf}\n  \\caption{Your caption following the same style.}\n\\end{figure}\n```\n\n**Step 4: Replace Content Section by Section**\n\nWork through the paper systematically:\n\n```\nReplacement Order:\n1. Title and authors (anonymize for submission)\n2. Abstract\n3. Introduction\n4. Methods\n5. Experiments\n6. Related Work\n7. Conclusion\n8. References (your .bib file)\n9. Appendix\n```\n\nFor each section:\n1. Read the template's example content\n2. Note any special formatting or macros used\n3. Replace with your content following the same patterns\n4. Compile frequently to catch errors early\n\n**Step 5: Use Template Macros**\n\nTemplates often define useful macros. Check the preamble for:\n\n```latex\n% Common template macros to use:\n\\newcommand{\\method}{YourMethodName}  % Consistent method naming\n\\newcommand{\\eg}{e.g.,\\xspace}        % Proper abbreviations\n\\newcommand{\\ie}{i.e.,\\xspace}\n\\newcommand{\\etal}{\\textit{et al.}\\xspace}\n```\n\n**Step 6: Clean Up Only at the End**\n\nOnly remove template artifacts when paper is nearly complete:\n\n```latex\n% BEFORE SUBMISSION - remove these:\n% - Commented-out template examples\n% - Unused packages\n% - Template's example figures\u002Ftables\n% - Lorem ipsum or placeholder text\n\n% KEEP these:\n% - All style files (.sty)\n% - Bibliography style (.bst)\n% - Required packages from template\n% - Any custom macros you're using\n```\n\n### Template Pitfalls to Avoid\n\n| Pitfall | Problem | Solution |\n|---------|---------|----------|\n| Copying only `main.tex` | Missing `.sty`, won't compile | Copy entire directory |\n| Modifying `.sty` files | Breaks conference formatting | Never edit style files |\n| Adding random packages | Conflicts, breaks template | Only add if necessary |\n| Deleting template content too early | Lose formatting reference | Keep as comments until done |\n| Not compiling frequently | Errors accumulate | Compile after each section |\n\n### Quick Template Reference\n\n| Conference | Main File | Key Style File | Notes |\n|------------|-----------|----------------|-------|\n| NeurIPS 2025 | `main.tex` | `neurips.sty` | Has Makefile |\n| ICML 2026 | `example_paper.tex` | `icml2026.sty` | Includes algorithm packages |\n| ICLR 2026 | `iclr2026_conference.tex` | `iclr2026_conference.sty` | Has math_commands.tex |\n| ACL | `acl_latex.tex` | `acl.sty` | Strict formatting |\n| AAAI 2026 | `aaai2026-unified-template.tex` | `aaai2026.sty` | Very strict compliance |\n| COLM 2025 | `colm2025_conference.tex` | `colm2025_conference.sty` | Similar to ICLR |\n\n---\n\n## Conference Resubmission & Format Conversion\n\nWhen a paper is rejected or withdrawn from one venue and resubmitted to another, format conversion is required. This is a common workflow in ML research.\n\n### Workflow 3: Converting Between Conference Formats\n\n```\nFormat Conversion Checklist:\n- [ ] Step 1: Identify source and target template differences\n- [ ] Step 2: Create new project with target template\n- [ ] Step 3: Copy content sections (not preamble)\n- [ ] Step 4: Adjust page limits and content\n- [ ] Step 5: Update conference-specific requirements\n- [ ] Step 6: Verify compilation and formatting\n```\n\n**Step 1: Key Template Differences**\n\n| From → To | Page Change | Key Adjustments |\n|-----------|-------------|-----------------|\n| NeurIPS → ICML | 9 → 8 pages | Cut 1 page, add Broader Impact if missing |\n| ICML → ICLR | 8 → 9 pages | Can expand experiments, add LLM disclosure |\n| NeurIPS → ACL | 9 → 8 pages | Restructure for NLP conventions, add Limitations |\n| ICLR → AAAI | 9 → 7 pages | Significant cuts needed, strict style adherence |\n| Any → COLM | varies → 9 | Reframe for language model focus |\n\n**Step 2: Content Migration (NOT Template Merge)**\n\n**Never copy LaTeX preambles between templates.** Instead:\n\n```bash\n# 1. Start fresh with target template\ncp -r templates\u002Ficml2026\u002F new_submission\u002F\n\n# 2. Copy ONLY content sections from old paper\n# - Abstract text\n# - Section content (between \\section{} commands)\n# - Figures and tables\n# - Bibliography entries\n\n# 3. Paste into target template structure\n```\n\n**Step 3: Adjusting for Page Limits**\n\nWhen cutting pages (e.g., NeurIPS 9 → AAAI 7):\n- Move detailed proofs to appendix\n- Condense related work (cite surveys instead of individual papers)\n- Combine similar experiments into unified tables\n- Use smaller figure sizes with subfigures\n- Tighten writing: eliminate redundancy, use active voice\n\nWhen expanding (e.g., ICML 8 → ICLR 9):\n- Add ablation studies reviewers requested\n- Expand limitations discussion\n- Include additional baselines\n- Add qualitative examples\n\n**Step 4: Conference-Specific Adjustments**\n\n| Target Venue | Required Additions |\n|--------------|-------------------|\n| **ICML** | Broader Impact Statement (after conclusion) |\n| **ICLR** | LLM usage disclosure, reciprocal reviewing agreement |\n| **ACL\u002FEMNLP** | Limitations section (mandatory), Ethics Statement |\n| **AAAI** | Strict adherence to style file (no modifications) |\n| **NeurIPS** | Paper checklist (appendix), lay summary if accepted |\n\n**Step 5: Update References**\n\n```latex\n% Remove self-citations that reveal identity (for blind review)\n% Update any \"under review\" citations to published versions\n% Add new relevant work published since last submission\n```\n\n**Step 6: Addressing Previous Reviews**\n\nWhen resubmitting after rejection:\n- **Do** address reviewer concerns in the new version\n- **Do** add experiments\u002Fclarifications reviewers requested\n- **Don't** include a \"changes from previous submission\" section (blind review)\n- **Don't** reference the previous submission or reviews\n\n**Common Conversion Pitfalls:**\n- ❌ Copying `\\usepackage` commands (causes conflicts)\n- ❌ Keeping old conference header\u002Ffooter commands\n- ❌ Forgetting to update `\\bibliography{}` path\n- ❌ Missing conference-specific required sections\n- ❌ Exceeding page limit after format change\n\n---\n\n## Citation Workflow (Hallucination Prevention)\n\n**⚠️ CRITICAL**: AI-generated citations have ~40% error rate. **Never write BibTeX from memory.**\n\n### The Golden Rule\n\n```\nIF you cannot programmatically fetch a citation:\n    → Mark it as [CITATION NEEDED] or [PLACEHOLDER - VERIFY]\n    → Tell the scientist explicitly\n    → NEVER invent a plausible-sounding reference\n```\n\n### Workflow 2: Adding Citations\n\n```\nCitation Verification (MANDATORY for every citation):\n- [ ] Step 1: Search using Exa MCP or Semantic Scholar API\n- [ ] Step 2: Verify paper exists in 2+ sources (Semantic Scholar + arXiv\u002FCrossRef)\n- [ ] Step 3: Retrieve BibTeX via DOI (programmatically, not from memory)\n- [ ] Step 4: Verify the claim you're citing actually appears in the paper\n- [ ] Step 5: Add verified BibTeX to bibliography\n- [ ] Step 6: If ANY step fails → mark as placeholder, inform scientist\n```\n\n**Step 0: Use Exa MCP for Initial Search (Recommended)**\n\nIf Exa MCP is installed, use it to find relevant papers:\n```\nSearch: \"RLHF language model alignment 2023\"\nSearch: \"sparse autoencoders interpretability\"\nSearch: \"attention mechanism transformers Vaswani\"\n```\n\nThen verify each result with Semantic Scholar and fetch BibTeX via DOI.\n\n**Step 1: Search Semantic Scholar**\n\n```python\nfrom semanticscholar import SemanticScholar\n\nsch = SemanticScholar()\nresults = sch.search_paper(\"attention mechanism transformers\", limit=5)\nfor paper in results:\n    print(f\"{paper.title} - {paper.paperId}\")\n    print(f\"  DOI: {paper.externalIds.get('DOI', 'N\u002FA')}\")\n```\n\n**Step 2: Verify Existence**\n\nConfirm paper appears in at least two sources (Semantic Scholar + CrossRef\u002FarXiv).\n\n**Step 3: Retrieve BibTeX via DOI**\n\n```python\nimport requests\n\ndef doi_to_bibtex(doi: str) -> str:\n    \"\"\"Get verified BibTeX from DOI via CrossRef.\"\"\"\n    response = requests.get(\n        f\"https:\u002F\u002Fdoi.org\u002F{doi}\",\n        headers={\"Accept\": \"application\u002Fx-bibtex\"}\n    )\n    response.raise_for_status()\n    return response.text\n\n# Example\nbibtex = doi_to_bibtex(\"10.48550\u002FarXiv.1706.03762\")\nprint(bibtex)\n```\n\n**Step 4: Verify Claims**\n\nBefore citing for a specific claim, access the paper and confirm the attributed claim actually appears.\n\n**Step 5: Handle Failures Explicitly**\n\nIf you cannot verify a citation at ANY step:\n\n```latex\n% Option 1: Explicit placeholder\n\\cite{PLACEHOLDER_smith2023_verify}  % TODO: Could not verify - scientist must confirm\n\n% Option 2: Note in text\n... as shown in prior work [CITATION NEEDED - could not verify Smith et al. 2023].\n```\n\n**Always inform the scientist:**\n> \"I could not verify the following citations and have marked them as placeholders:\n> - Smith et al. 2023 on reward hacking - could not find in Semantic Scholar\n> - Jones 2022 on scaling laws - found similar paper but different authors\n> Please verify these before submission.\"\n\n### Summary: Citation Rules\n\n| Situation | Action |\n|-----------|--------|\n| Found paper, got DOI, fetched BibTeX | ✅ Use the citation |\n| Found paper, no DOI | ✅ Use arXiv BibTeX or manual entry from paper |\n| Paper exists but can't fetch BibTeX | ⚠️ Mark placeholder, inform scientist |\n| Uncertain if paper exists | ❌ Mark `[CITATION NEEDED]`, inform scientist |\n| \"I think there's a paper about X\" | ❌ **NEVER cite** - search first or mark placeholder |\n\n**🚨 NEVER generate BibTeX from memory—always fetch programmatically. 🚨**\n\nSee [references\u002Fcitation-workflow.md](references\u002Fcitation-workflow.md) for complete API documentation.\n\n---\n\n## Common Issues and Solutions\n\n**Issue: Abstract too generic**\n\nDelete first sentence if it could be prepended to any ML paper. Start with your specific contribution.\n\n**Issue: Introduction exceeds 1.5 pages**\n\nSplit background into Related Work. Front-load contribution bullets. Methods should start by page 2-3.\n\n**Issue: Experiments lack explicit claims**\n\nAdd sentence before each experiment: \"This experiment tests whether [specific claim]...\"\n\n**Issue: Reviewers find paper hard to follow**\n\n- Add explicit signposting: \"In this section, we show X\"\n- Use consistent terminology throughout\n- Include figure captions that stand alone\n\n**Issue: Missing statistical significance**\n\nAlways include:\n- Error bars (specify: std dev or std error)\n- Number of runs\n- Statistical tests if comparing methods\n\n---\n\n## Reviewer Evaluation Criteria\n\nReviewers assess papers on four dimensions:\n\n| Criterion | What Reviewers Look For |\n|-----------|------------------------|\n| **Quality** | Technical soundness, well-supported claims |\n| **Clarity** | Clear writing, reproducible by experts |\n| **Significance** | Community impact, advances understanding |\n| **Originality** | New insights (doesn't require new method) |\n\n**Scoring (NeurIPS 6-point scale):**\n- 6: Strong Accept - Groundbreaking, flawless\n- 5: Accept - Technically solid, high impact\n- 4: Borderline Accept - Solid, limited evaluation\n- 3: Borderline Reject - Solid but weaknesses outweigh\n- 2: Reject - Technical flaws\n- 1: Strong Reject - Known results or ethics issues\n\nSee [references\u002Freviewer-guidelines.md](references\u002Freviewer-guidelines.md) for detailed reviewer instructions.\n\n---\n\n## Tables and Figures\n\n### Tables\n\nUse `booktabs` LaTeX package for professional tables:\n\n```latex\n\\usepackage{booktabs}\n\\begin{tabular}{lcc}\n\\toprule\nMethod & Accuracy ↑ & Latency ↓ \\\\\n\\midrule\nBaseline & 85.2 & 45ms \\\\\n\\textbf{Ours} & \\textbf{92.1} & 38ms \\\\\n\\bottomrule\n\\end{tabular}\n```\n\n**Rules:**\n- Bold best value per metric\n- Include direction symbols (↑ higher is better, ↓ lower is better)\n- Right-align numerical columns\n- Consistent decimal precision\n\n### Figures\n\n- **Vector graphics** (PDF, EPS) for all plots and diagrams\n- **Raster** (PNG 600 DPI) only for photographs\n- Use **colorblind-safe palettes** (Okabe-Ito or Paul Tol)\n- Verify **grayscale readability** (8% of men have color vision deficiency)\n- **No title inside figure**—the caption serves this function\n- **Self-contained captions**—reader should understand without main text\n\n---\n\n## References & Resources\n\n### Reference Documents (Deep Dives)\n\n| Document | Contents |\n|----------|----------|\n| [writing-guide.md](references\u002Fwriting-guide.md) | Gopen & Swan 7 principles, Ethan Perez micro-tips, word choice |\n| [citation-workflow.md](references\u002Fcitation-workflow.md) | Citation APIs, Python code, BibTeX management |\n| [checklists.md](references\u002Fchecklists.md) | NeurIPS 16-item, ICML, ICLR, ACL requirements |\n| [reviewer-guidelines.md](references\u002Freviewer-guidelines.md) | Evaluation criteria, scoring, rebuttals |\n| [sources.md](references\u002Fsources.md) | Complete bibliography of all sources |\n\n### LaTeX Templates\n\nTemplates in `templates\u002F` directory: **ICML 2026**, **ICLR 2026**, **NeurIPS 2025**, **ACL\u002FEMNLP**, **AAAI 2026**, **COLM 2025**.\n\n**Compiling to PDF:**\n- **VS Code\u002FCursor**: Install LaTeX Workshop extension + TeX Live → Save to auto-compile\n- **Command line**: `latexmk -pdf main.tex` or `pdflatex` + `bibtex` workflow\n- **Online**: Upload to [Overleaf](https:\u002F\u002Foverleaf.com)\n\nSee [templates\u002FREADME.md](templates\u002FREADME.md) for detailed setup instructions.\n\n### Key External Sources\n\n**Writing Philosophy:**\n- [Neel Nanda: How to Write ML Papers](https:\u002F\u002Fwww.alignmentforum.org\u002Fposts\u002FeJGptPbbFPZGLpjsp\u002Fhighly-opinionated-advice-on-how-to-write-ml-papers) - Narrative, \"What\u002FWhy\u002FSo What\"\n- [Farquhar: How to Write ML Papers](https:\u002F\u002Fsebastianfarquhar.com\u002Fon-research\u002F2024\u002F11\u002F04\u002Fhow_to_write_ml_papers\u002F) - 5-sentence abstract\n- [Gopen & Swan: Science of Scientific Writing](https:\u002F\u002Fcseweb.ucsd.edu\u002F~swanson\u002Fpapers\u002Fscience-of-writing.pdf) - 7 reader expectation principles\n- [Lipton: Heuristics for Scientific Writing](https:\u002F\u002Fwww.approximatelycorrect.com\u002F2018\u002F01\u002F29\u002Fheuristics-technical-scientific-writing-machine-learning-perspective\u002F) - Word choice\n- [Perez: Easy Paper Writing Tips](https:\u002F\u002Fethanperez.net\u002Feasy-paper-writing-tips\u002F) - Micro-level clarity\n\n**APIs:** [Semantic Scholar](https:\u002F\u002Fapi.semanticscholar.org\u002Fapi-docs\u002F) | [CrossRef](https:\u002F\u002Fwww.crossref.org\u002Fdocumentation\u002Fretrieve-metadata\u002Frest-api\u002F) | [arXiv](https:\u002F\u002Finfo.arxiv.org\u002Fhelp\u002Fapi\u002Fbasics.html)\n\n**Venues:** [NeurIPS](https:\u002F\u002Fneurips.cc\u002FConferences\u002F2025\u002FPaperInformation\u002FStyleFiles) | [ICML](https:\u002F\u002Ficml.cc\u002FConferences\u002F2025\u002FAuthorInstructions) | [ICLR](https:\u002F\u002Ficlr.cc\u002FConferences\u002F2026\u002FAuthorGuide) | [ACL](https:\u002F\u002Fgithub.com\u002Facl-org\u002Facl-style-files)\n\n",{"name":5,"tags":24,"author":36,"license":15,"version":37,"description":7,"dependencies":38},[25,26,27,28,29,30,31,32,33,34,35],"Academic Writing","NeurIPS","ICML","ICLR","ACL","AAAI","COLM","LaTeX","Paper Writing","Citations","Research","Orchestra Research","1.0.0",[39,40,41,42],"semanticscholar","arxiv","habanero","requests","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-imp-ml-paper-writing",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ml-paper-writing",{"tool":57,"command":58},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ml-paper-writing",{"tool":60,"command":61},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ml-paper-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-ml-paper-writing\u002FSKILL.md",true,[65,71,75,79,83],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fchecklists.md","REFERENCE","参考文档",10774,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-ml-paper-writing\u002Freferences\u002Fchecklists.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fcitation-workflow.md",15167,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-ml-paper-writing\u002Freferences\u002Fcitation-workflow.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Freviewer-guidelines.md",10451,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-ml-paper-writing\u002Freferences\u002Freviewer-guidelines.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fsources.md",7310,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-ml-paper-writing\u002Freferences\u002Fsources.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fwriting-guide.md",16297,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-imp-ml-paper-writing\u002Freferences\u002Fwriting-guide.md",[88,95,103,110,117,124],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]