ml-paper-writing

Installation
Summary

Draft publication-ready ML/AI/Systems papers for top conferences with citation verification and LaTeX templates.

  • Supports 12 major venues (NeurIPS, ICML, ICLR, ACL, AAAI, COLM, OSDI, NSDI, ASPLOS, SOSP) with conference-specific templates, page limits, and submission requirements
  • Enforces programmatic citation verification via Semantic Scholar and CrossRef APIs to prevent hallucinated references; marks unverifiable citations as explicit placeholders
  • Provides writing philosophy from leading researchers (Nanda, Farquhar, Lipton, Steinhardt) covering narrative structure, the 7 principles of reader expectations, and sentence-level clarity
  • Includes format conversion workflows for resubmitting between venues and complete paper checklists (abstract, introduction, methods, experiments, related work, limitations) with iterative feedback loops
SKILL.md

ML Paper Writing for Top AI Conferences

Expert-level guidance for writing publication-ready papers targeting NeurIPS, ICML, ICLR, ACL, AAAI, 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.

For systems venues (OSDI, NSDI, ASPLOS, SOSP), use the systems-paper-writing skill, which provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, and LaTeX templates for systems conferences.

Core Philosophy: Collaborative Writing

Paper writing is collaborative, but Claude should be proactive in delivering drafts.

The typical workflow starts with a research repository containing code, results, and experimental artifacts. Claude's role is to:

  1. Understand the project by exploring the repo, results, and existing documentation
  2. Deliver a complete first draft when confident about the contribution
  3. Search literature using web search and APIs to find relevant citations
  4. Refine through feedback cycles when the scientist provides input
  5. Ask for clarification only when genuinely uncertain about key decisions

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.

Related skills

More from zechenzhangagi/ai-research-skills

Installs
716
GitHub Stars
8.3K
First Seen
Jan 23, 2026