Agent skill · Documentation

systems-paper-writing

Comprehensive guide for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines. Use this skill for all systems conference paper writing.

Orchestra-Researchgithub.com/Orchestra-ResearchGitHub ↗
claude-codecodexMIT
Install
npx skills add Orchestra-Research/AI-Research-SKILLs --skill systems-paper-writing --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 16
SKILL.md size: 14 KB
Bundled scripts: none
Version: 1.1.0
Declared author: Orchestra Research
Path: 20-ml-paper-writing/systems-paper-writing/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 11,391
Language: TeX
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Systems Paper Writing: Paragraph-Level Structural Blueprint Fine-grained structural guidance for writing **10–12 page systems papers** targeting top systems venues: OSDI, SOSP, ASPLOS, NSDI, and EuroSys. This skill provides page allocation per section, paragraph-level blueprints, and writing patterns distilled from authoritative guides and best-paper analysis. ## When to Use This Skill | Scenario | Use This Skill | Use ml-paper-writing Instead | |----------|---------------|------------------------------| | Structuring a 12-page OSDI/SOSP paper | ✅ | | | Page budget and paragraph planning | ✅ | | | Systems-specific evaluation structure | ✅ | | | General ML paper writing philosophy | | ✅ | | Citation verification workflow | | ✅ | | LaTeX templates and formatting | | ✅ | | NeurIPS/ICML/ICLR paper structure | | ✅ | **Boundary**: ml-paper-writing provides general writing philosophy, multi-venue templates, and citation verification. This skill focuses exclusively on **paragraph-level structural blueprints** for systems conferences. --- ## Authoritative Sources This blueprint synthesizes guidance from established systems researchers: 1. **Levin & Redell** — "How (and How Not) to Write a

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Authoritative Sources
  3. 12-Page Systems Paper Blueprint
  4. Overview: Page Allocation
  5. Abstract (150–250 words, 5 sentences)
  6. S1 Introduction (1.5–2 pages)
  7. S2 Background & Motivation (1–1.5 pages)
  8. S3 Design (3–4 pages)
  9. S4 Implementation (0.5–1 page)
  10. S5 Evaluation (3–4 pages)
  11. S6 Related Work (1 page)
  12. S7 Conclusion (0.5 page)
  13. Writing Patterns
  14. Pattern 1: Gap Analysis (Lucid, ASPLOS'23)
Ships with 15 files
  • references/checklist.md
  • references/reviewer-guidelines.md
  • references/section-blueprints.md
  • references/systems-conferences.md
  • references/writing-patterns.md
  • templates/asplos2027/main.tex
  • templates/asplos2027/references.bib
  • templates/nsdi2027/main.tex
  • templates/nsdi2027/references.bib
  • templates/nsdi2027/usenix-2020-09.sty
  • templates/osdi2026/main.tex
  • templates/osdi2026/references.bib
  • templates/osdi2026/usenix-2020-09.sty
  • templates/sosp2026/main.tex
  • templates/sosp2026/references.bib
More from AI-Research-SKILLs
All skills →
About this skill
What does the systems-paper-writing skill do?

Comprehensive guide for writing systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides paragraph-level structural blueprints, writing patterns, venue-specific checklists, reviewer guidelines, LaTeX templates, and conference deadlines. Use this skill for all systems conference paper writing.

How do I install it?

Run `npx skills add Orchestra-Research/AI-Research-SKILLs --skill systems-paper-writing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Orchestra-Research/AI-Research-SKILLs, a repository with 11,391 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going