[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QNJXDHJ83GAQEB2NV97S35":3,"skill-same:01M6QNJXDHJ83GAQEB2NV97S35":152},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":14,"repositoryHtmlUrl":69,"repositoryHomepageUrl":70,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6QNJXDHJ83GAQEB2NV97S35","systems-paper-writing",null,"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.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"systems","Systems Paper Writing","paper","writing","Paper Writing","LaTeX","templates","guide","use","structural","Academic Writing","guidelines","OSDI","NSDI","ASPLOS","SOSP","papers","targeting","for","research","2026-11-10 10:12:30",false,"---\nname: systems-paper-writing\ndescription: 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.\nversion: 1.1.0\nauthor: Orchestra Research\nlicense: MIT\ntags: [Systems Paper Writing, OSDI, SOSP, ASPLOS, NSDI, EuroSys, Structural Blueprint, Academic Writing, LaTeX]\ncategory: \"ai-research\"\n---\n\n# Systems Paper Writing: Paragraph-Level Structural Blueprint\n\nFine-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.\n\n## When to Use This Skill\n\n| Scenario | Use This Skill | Use ml-paper-writing Instead |\n|----------|---------------|------------------------------|\n| Structuring a 12-page OSDI\u002FSOSP paper | ✅ | |\n| Page budget and paragraph planning | ✅ | |\n| Systems-specific evaluation structure | ✅ | |\n| General ML paper writing philosophy | | ✅ |\n| Citation verification workflow | | ✅ |\n| LaTeX templates and formatting | | ✅ |\n| NeurIPS\u002FICML\u002FICLR paper structure | | ✅ |\n\n**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.\n\n---\n\n## Authoritative Sources\n\nThis blueprint synthesizes guidance from established systems researchers:\n\n1. **Levin & Redell** — \"How (and How Not) to Write a Good Systems Paper\" (SOSP'83 PC Chairs, USENIX\u002FACM SIGOPS)\n2. **Irene Zhang** (MSR\u002FUW) — \"Hints on how to write an SOSP paper\" (SOSP\u002FOSDI PC)\n3. **Gernot Heiser** (UNSW, seL4) — Style Guide + Paper Writing Talk\n4. **Timothy Roscoe** (ETH Zürich) — \"Writing reviews for systems conferences\"\n5. **Mike Dahlin** (UT Austin\u002FGoogle) — \"Giving a Conference Talk\"\n6. **Yi Ding** — \"How to write good systems papers?\"\n7. **hzwer & DingXiaoH** — WritingAIPaper (GitHub 1.3k+ stars)\n\nFull citations and URLs: see [references\u002Fsection-blueprints.md](references\u002Fsection-blueprints.md).\n\n---\n\n## 12-Page Systems Paper Blueprint\n\n### Overview: Page Allocation\n\n| Section | Pages | Purpose |\n|---------|-------|---------|\n| Abstract | ~0.25 | 150–250 words, 5-sentence structure |\n| S1 Introduction | 1.5–2 | Problem → Gap → Insight → Contributions |\n| S2 Background & Motivation | 1–1.5 | Terms + Production observations |\n| S3 Design | 3–4 | Architecture + Module details + Alternatives |\n| S4 Implementation | 0.5–1 | Prototype details, LOC, key engineering |\n| S5 Evaluation | 3–4 | Setup + End-to-end + Microbenchmarks + Scalability |\n| S6 Related Work | 1 | Grouped by methodology, explicit comparison |\n| S7 Conclusion | 0.5 | 3-sentence summary |\n| **Total** | **~12** | Submission: 12 pages strict (USENIX) \u002F 11 pages (ACM ASPLOS). Camera-ready: up to 14 pages (USENIX) \u002F 13 pages (ACM). Ranges above span submission through camera-ready. Target 12 pages for initial submission. References unlimited. |\n\n### Abstract (150–250 words, 5 sentences)\n\n```text\nSentence 1: Problem context and importance\nSentence 2: Gap in existing approaches\nSentence 3: Key insight or thesis (\"X is better for Y in environment Z\")\nSentence 4: Summary of approach and key results\nSentence 5: Broader impact or availability\n```\n\n**Source**: Levin & Redell — \"Can you state the new idea concisely? Use them in the abstract.\" Irene Zhang — \"The abstract is harder to write because you cannot use terms or concepts you introduced in the paper.\"\n\n### S1 Introduction (1.5–2 pages)\n\n**Paragraph structure**:\n\n1. **Problem statement** (~0.5 page) — Establish the domain and why it matters. Use concrete numbers (cluster sizes, workload statistics, latency requirements).\n2. **Gap analysis** (~0.5 page) — Enumerate specific gaps G1–Gn in existing systems. Each gap is one sentence with evidence.\n3. **Key insight** (1 paragraph) — The thesis statement: \"X is better for applications Y running in environment Z.\" (Irene Zhang formula)\n4. **Contributions** (~0.5 page) — Numbered list of 3–5 concrete contributions. Each contribution is testable and maps to a section.\n\n**Writing pattern**: hzwer Move 1 (Establish territory) → Move 2 (Find niche) → Move 3 (Occupy niche).\n\n**Source**: Irene Zhang — \"clearly state your target environment (Z) and application (Y)\" + \"clearly state why previous systems do not meet the needs\"; Levin & Redell — \"What exactly is the problem being solved?\"\n\n### S2 Background & Motivation (1–1.5 pages)\n\n**Paragraph structure**:\n\n1. **Technical background** (~0.5 page) — Define terms and systems the reader needs. Follow Gernot Heiser's \"define-before-use\" principle.\n2. **Production observations** (~0.5–1 page) — Present Observation 1, 2, 3 from real data or measurements. Each observation leads to a design insight.\n\n**Source**: Irene Zhang — \"clearly motivate Y and Z. Why is application Y important?\"; Gernot Heiser — \"define-before-use.\"\n\n### S3 Design (3–4 pages)\n\n**Paragraph structure**:\n\n1. **System architecture overview** (~0.5 page) — Architecture diagram first (Yi Ding: \"draw a picture first\"). One-paragraph walkthrough of major components and data flow.\n2. **Module-by-module design** (~2–2.5 pages) — Each subsection: what the module does, the design choice made, alternatives considered, and why this choice wins.\n3. **Design alternatives and trade-offs** (~0.5–1 page) — For each major decision, explicitly discuss what was not chosen and why.\n\n**Source**: Irene Zhang — \"Every design choice made in X should be discussed with alternatives and the reasons for the choice\"; Levin & Redell — \"What were the alternatives considered at various points, and why were the choices made?\"\n\n### S4 Implementation (0.5–1 page)\n\n1. **Prototype description** — Language, framework, LOC, integration with existing systems.\n2. **Key engineering decisions** — Non-obvious implementation choices worth documenting.\n\n**Source**: Levin & Redell — \"Does the paper describe something that has actually been implemented?\"; Irene Zhang — \"explain how you constructed a prototype to test your hypothesis.\"\n\n### S5 Evaluation (3–4 pages)\n\n**Paragraph structure**:\n\n1. **Experimental setup** (~0.5 page) — Hardware, baselines, workloads, metrics. Enough detail to reproduce.\n2. **End-to-end comparison** (~1–1.5 pages) — X vs baselines for application Y on environment Z. Main performance results.\n3. **Microbenchmarks \u002F Ablation** (~1–1.5 pages) — Isolate each design decision's contribution. Ablation experiments decompose the gains.\n4. **Scalability** (~0.5 page) — Show behavior as problem size, cluster size, or load increases.\n\n**Critical rule** (Irene Zhang): State every experimental conclusion **three times**:\n- Section opening: hypothesis (\"We expect X to outperform Y because...\")\n- Section closing: conclusion (\"Results show X outperforms Y by Z%\")\n- Figure caption: evidence (\"Figure N shows X achieves Z% better throughput than Y\")\n\n**Two experiment types**:\n- Type 1: X vs baselines for Y on Z (end-to-end comparison)\n- Type 2: Ablation — remove each design component to measure its individual impact\n\n### S6 Related Work (1 page)\n\n- Group by **methodology or approach**, not by individual papers.\n- For each group: what they do, what limitation remains, how your work differs.\n- Use a comparison table when comparing 4+ systems on specific dimensions.\n\n**Source**: Levin & Redell — \"Are comparisons with previous work clear and explicit?\"; Irene Zhang — use comparison tables.\n\n### S7 Conclusion (0.5 page)\n\nThree sentences (Irene Zhang formula):\n1. The hypothesis \u002F problem addressed\n2. The solution approach\n3. The key result\n\n---\n\n## Writing Patterns\n\nFour reusable patterns for structuring systems papers. See [references\u002Fwriting-patterns.md](references\u002Fwriting-patterns.md) for detailed examples.\n\n### Pattern 1: Gap Analysis (Lucid, ASPLOS'23)\nEnumerate gaps G1–Gn in Introduction → map to answers A1–An in Design. Creates a clear contract with the reader.\n\n### Pattern 2: Observation-Driven (GFS, arXiv 2025)\nPresent production observations (O1–O3) in Motivation → derive design insights → build system around insights. Effective when you have real workload data.\n\n### Pattern 3: Contribution List (Blox, EuroSys'24; Sia, SOSP'23)\nNumbered contributions in Introduction, each mapping to a section. Readers (and reviewers) can track claims through the paper.\n\n### Pattern 4: Thesis Formula (Irene Zhang)\nStructure the entire paper around: \"X is better for applications Y running in environment Z.\" Introduction states it, Design explains how, Evaluation proves it.\n\n---\n\n## Conference Differences\n\n> **Warning**: Venue rules change yearly. Always verify against the **current year's CFP** before submission.\n\n| Venue | Format | Submission Limit | Camera-Ready | References |\n|-------|--------|-----------------|--------------|------------|\n| OSDI | USENIX | 12 pages | 14 pages | Unlimited |\n| NSDI | USENIX | 12 pages | 14 pages | Unlimited |\n| SOSP | ACM SIGOPS | 12 pages (tech content) | — | Unlimited |\n| ASPLOS | ACM SIGPLAN | 11 pages | 13 pages | Unlimited |\n| EuroSys | ACM | 12 pages | — | Unlimited |\n\nBased on 2025\u002F2026 CFPs. Verify current limits before submission.\n\n---\n\n## Writing Philosophy\n\n### Manage Reader State (Gernot Heiser)\nTreat the reader's cognitive load like an OS managing process state. Never introduce a concept without context. Never reference something defined later without a forward pointer.\n\n### Six-Dimensional Quality (Levin & Redell)\nSelf-check against: **Original Ideas**, **Reality** (is it built?), **Lessons** (what did you learn?), **Choices** (alternatives discussed?), **Context** (related work fair?), **Presentation** (clear writing?).\n\n### Page-One Figure (hzwer)\nInclude a figure on the first page that captures the core idea. Reviewers form first impressions from the title, abstract, and page-one figure.\n\n---\n\n## Academic Integrity Requirements\n\n### Citation Discipline\n- **Never generate citations from memory.** Use ml-paper-writing's citation verification workflow (Semantic Scholar \u002F DBLP \u002F CrossRef APIs).\n- Mark unverified references as `[CITATION NEEDED]`.\n\n### Prohibition of Fabrication\n- Do NOT fabricate production observations, traces, deployment experiences, or experimental results.\n- Do NOT generate fake venue rules, paper metadata, or best-paper claims.\n- Do NOT copy paragraph-level text from reference papers. This blueprint provides **structural guidance**, not copy-paste templates.\n\n### LLM Disclosure\n- Some venues require disclosure of substantial LLM use in writing or ideation. Check each venue's AI policy in the current CFP.\n\n### Attribution\n- When structures are inspired by specific papers (e.g., Lucid's gap-analysis pattern), cite the inspiration.\n- Cross-repository references (e.g., ARIS paper-slides structure) are attributed, not copied.\n\n### Temporal Validity\n- Venue rules (page limits, format, AI policies) change annually. All venue information in this skill is based on 2025\u002F2026 CFPs. **Always verify against the current year's CFP.**\n\n---\n\n## Workflow: Structuring a New Systems Paper\n\n```text\nStep 1: Read this SKILL.md for page allocation overview\nStep 2: Read references\u002Fsection-blueprints.md for per-section paragraph templates\nStep 3: Choose a writing pattern from references\u002Fwriting-patterns.md\nStep 4: Draft section by section following the blueprint\nStep 5: Run the checklist from references\u002Fchecklist.md before submission\nStep 6: Use ml-paper-writing for citation verification and LaTeX formatting\n```\n\n### Quick Checklist\n\n- [ ] Thesis statement follows \"X is better for Y in Z\" formula\n- [ ] Introduction has numbered contributions (3–5)\n- [ ] Each contribution maps to a paper section\n- [ ] Design discusses alternatives for every major choice\n- [ ] Every eval conclusion stated 3 times (hypothesis, result, caption)\n- [ ] Related work grouped by methodology, not individual papers\n- [ ] Page budget within venue limits\n- [ ] All citations verified programmatically (no hallucinated references)\n\n---\n\n## Common Issues and Solutions\n\n| Issue | Solution |\n|-------|----------|\n| Paper feels like a \"feature list\" | Restructure around thesis formula: X better for Y in Z |\n| Evaluation lacks depth | Add ablation experiments isolating each design decision |\n| Reviewers say \"incremental\" | Strengthen gap analysis: make G1–Gn crisper with evidence |\n| Design section too long | Move implementation details to S4, keep S3 at design level |\n| Motivation feels weak | Add production observations with concrete numbers |\n| Related work reads like a bibliography | Group by approach, add explicit differentiation |\n\n---\n\n## References\n\n### Writing Guidance\n- [references\u002Fsection-blueprints.md](references\u002Fsection-blueprints.md) — Detailed per-section paragraph templates with authoritative source quotes and best-paper structural examples\n- [references\u002Fwriting-patterns.md](references\u002Fwriting-patterns.md) — Four writing patterns with concrete paper examples\n\n### Venue-Specific\n- [references\u002Fchecklist.md](references\u002Fchecklist.md) — 7-stage pre-submission checklist covering structure, writing quality, evaluation rigor, design quality, academic integrity, venue-specific requirements (OSDI\u002FNSDI\u002FASPLOS\u002FSOSP\u002FEuroSys), and final pass\n- [references\u002Fsystems-conferences.md](references\u002Fsystems-conferences.md) — Conference overview, deadlines, track descriptions, formatting requirements, submission rules, and format conversion guides\n- [references\u002Freviewer-guidelines.md](references\u002Freviewer-guidelines.md) — How systems conference reviewers evaluate papers, with venue-specific criteria and common concerns\n\n### LaTeX Templates\n- [templates\u002Fosdi2026\u002F](templates\u002Fosdi2026\u002F) — OSDI 2026 (USENIX format)\n- [templates\u002Fnsdi2027\u002F](templates\u002Fnsdi2027\u002F) — NSDI 2027 (USENIX format)\n- [templates\u002Fasplos2027\u002F](templates\u002Fasplos2027\u002F) — ASPLOS 2027 (ACM SIGPLAN format)\n- [templates\u002Fsosp2026\u002F](templates\u002Fsosp2026\u002F) — SOSP 2026 (ACM SIGPLAN format)\n","# Systems Paper Writing: Paragraph-Level Structural Blueprint\n\nFine-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.\n\n## When to Use This Skill\n\n| Scenario | Use This Skill | Use ml-paper-writing Instead |\n|----------|---------------|------------------------------|\n| Structuring a 12-page OSDI\u002FSOSP paper | ✅ | |\n| Page budget and paragraph planning | ✅ | |\n| Systems-specific evaluation structure | ✅ | |\n| General ML paper writing philosophy | | ✅ |\n| Citation verification workflow | | ✅ |\n| LaTeX templates and formatting | | ✅ |\n| NeurIPS\u002FICML\u002FICLR paper structure | | ✅ |\n\n**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.\n\n---\n\n## Authoritative Sources\n\nThis blueprint synthesizes guidance from established systems researchers:\n\n1. **Levin & Redell** — \"How (and How Not) to Write a Good Systems Paper\" (SOSP'83 PC Chairs, USENIX\u002FACM SIGOPS)\n2. **Irene Zhang** (MSR\u002FUW) — \"Hints on how to write an SOSP paper\" (SOSP\u002FOSDI PC)\n3. **Gernot Heiser** (UNSW, seL4) — Style Guide + Paper Writing Talk\n4. **Timothy Roscoe** (ETH Zürich) — \"Writing reviews for systems conferences\"\n5. **Mike Dahlin** (UT Austin\u002FGoogle) — \"Giving a Conference Talk\"\n6. **Yi Ding** — \"How to write good systems papers?\"\n7. **hzwer & DingXiaoH** — WritingAIPaper (GitHub 1.3k+ stars)\n\nFull citations and URLs: see [references\u002Fsection-blueprints.md](references\u002Fsection-blueprints.md).\n\n---\n\n## 12-Page Systems Paper Blueprint\n\n### Overview: Page Allocation\n\n| Section | Pages | Purpose |\n|---------|-------|---------|\n| Abstract | ~0.25 | 150–250 words, 5-sentence structure |\n| S1 Introduction | 1.5–2 | Problem → Gap → Insight → Contributions |\n| S2 Background & Motivation | 1–1.5 | Terms + Production observations |\n| S3 Design | 3–4 | Architecture + Module details + Alternatives |\n| S4 Implementation | 0.5–1 | Prototype details, LOC, key engineering |\n| S5 Evaluation | 3–4 | Setup + End-to-end + Microbenchmarks + Scalability |\n| S6 Related Work | 1 | Grouped by methodology, explicit comparison |\n| S7 Conclusion | 0.5 | 3-sentence summary |\n| **Total** | **~12** | Submission: 12 pages strict (USENIX) \u002F 11 pages (ACM ASPLOS). Camera-ready: up to 14 pages (USENIX) \u002F 13 pages (ACM). Ranges above span submission through camera-ready. Target 12 pages for initial submission. References unlimited. |\n\n### Abstract (150–250 words, 5 sentences)\n\n```text\nSentence 1: Problem context and importance\nSentence 2: Gap in existing approaches\nSentence 3: Key insight or thesis (\"X is better for Y in environment Z\")\nSentence 4: Summary of approach and key results\nSentence 5: Broader impact or availability\n```\n\n**Source**: Levin & Redell — \"Can you state the new idea concisely? Use them in the abstract.\" Irene Zhang — \"The abstract is harder to write because you cannot use terms or concepts you introduced in the paper.\"\n\n### S1 Introduction (1.5–2 pages)\n\n**Paragraph structure**:\n\n1. **Problem statement** (~0.5 page) — Establish the domain and why it matters. Use concrete numbers (cluster sizes, workload statistics, latency requirements).\n2. **Gap analysis** (~0.5 page) — Enumerate specific gaps G1–Gn in existing systems. Each gap is one sentence with evidence.\n3. **Key insight** (1 paragraph) — The thesis statement: \"X is better for applications Y running in environment Z.\" (Irene Zhang formula)\n4. **Contributions** (~0.5 page) — Numbered list of 3–5 concrete contributions. Each contribution is testable and maps to a section.\n\n**Writing pattern**: hzwer Move 1 (Establish territory) → Move 2 (Find niche) → Move 3 (Occupy niche).\n\n**Source**: Irene Zhang — \"clearly state your target environment (Z) and application (Y)\" + \"clearly state why previous systems do not meet the needs\"; Levin & Redell — \"What exactly is the problem being solved?\"\n\n### S2 Background & Motivation (1–1.5 pages)\n\n**Paragraph structure**:\n\n1. **Technical background** (~0.5 page) — Define terms and systems the reader needs. Follow Gernot Heiser's \"define-before-use\" principle.\n2. **Production observations** (~0.5–1 page) — Present Observation 1, 2, 3 from real data or measurements. Each observation leads to a design insight.\n\n**Source**: Irene Zhang — \"clearly motivate Y and Z. Why is application Y important?\"; Gernot Heiser — \"define-before-use.\"\n\n### S3 Design (3–4 pages)\n\n**Paragraph structure**:\n\n1. **System architecture overview** (~0.5 page) — Architecture diagram first (Yi Ding: \"draw a picture first\"). One-paragraph walkthrough of major components and data flow.\n2. **Module-by-module design** (~2–2.5 pages) — Each subsection: what the module does, the design choice made, alternatives considered, and why this choice wins.\n3. **Design alternatives and trade-offs** (~0.5–1 page) — For each major decision, explicitly discuss what was not chosen and why.\n\n**Source**: Irene Zhang — \"Every design choice made in X should be discussed with alternatives and the reasons for the choice\"; Levin & Redell — \"What were the alternatives considered at various points, and why were the choices made?\"\n\n### S4 Implementation (0.5–1 page)\n\n1. **Prototype description** — Language, framework, LOC, integration with existing systems.\n2. **Key engineering decisions** — Non-obvious implementation choices worth documenting.\n\n**Source**: Levin & Redell — \"Does the paper describe something that has actually been implemented?\"; Irene Zhang — \"explain how you constructed a prototype to test your hypothesis.\"\n\n### S5 Evaluation (3–4 pages)\n\n**Paragraph structure**:\n\n1. **Experimental setup** (~0.5 page) — Hardware, baselines, workloads, metrics. Enough detail to reproduce.\n2. **End-to-end comparison** (~1–1.5 pages) — X vs baselines for application Y on environment Z. Main performance results.\n3. **Microbenchmarks \u002F Ablation** (~1–1.5 pages) — Isolate each design decision's contribution. Ablation experiments decompose the gains.\n4. **Scalability** (~0.5 page) — Show behavior as problem size, cluster size, or load increases.\n\n**Critical rule** (Irene Zhang): State every experimental conclusion **three times**:\n- Section opening: hypothesis (\"We expect X to outperform Y because...\")\n- Section closing: conclusion (\"Results show X outperforms Y by Z%\")\n- Figure caption: evidence (\"Figure N shows X achieves Z% better throughput than Y\")\n\n**Two experiment types**:\n- Type 1: X vs baselines for Y on Z (end-to-end comparison)\n- Type 2: Ablation — remove each design component to measure its individual impact\n\n### S6 Related Work (1 page)\n\n- Group by **methodology or approach**, not by individual papers.\n- For each group: what they do, what limitation remains, how your work differs.\n- Use a comparison table when comparing 4+ systems on specific dimensions.\n\n**Source**: Levin & Redell — \"Are comparisons with previous work clear and explicit?\"; Irene Zhang — use comparison tables.\n\n### S7 Conclusion (0.5 page)\n\nThree sentences (Irene Zhang formula):\n1. The hypothesis \u002F problem addressed\n2. The solution approach\n3. The key result\n\n---\n\n## Writing Patterns\n\nFour reusable patterns for structuring systems papers. See [references\u002Fwriting-patterns.md](references\u002Fwriting-patterns.md) for detailed examples.\n\n### Pattern 1: Gap Analysis (Lucid, ASPLOS'23)\nEnumerate gaps G1–Gn in Introduction → map to answers A1–An in Design. Creates a clear contract with the reader.\n\n### Pattern 2: Observation-Driven (GFS, arXiv 2025)\nPresent production observations (O1–O3) in Motivation → derive design insights → build system around insights. Effective when you have real workload data.\n\n### Pattern 3: Contribution List (Blox, EuroSys'24; Sia, SOSP'23)\nNumbered contributions in Introduction, each mapping to a section. Readers (and reviewers) can track claims through the paper.\n\n### Pattern 4: Thesis Formula (Irene Zhang)\nStructure the entire paper around: \"X is better for applications Y running in environment Z.\" Introduction states it, Design explains how, Evaluation proves it.\n\n---\n\n## Conference Differences\n\n> **Warning**: Venue rules change yearly. Always verify against the **current year's CFP** before submission.\n\n| Venue | Format | Submission Limit | Camera-Ready | References |\n|-------|--------|-----------------|--------------|------------|\n| OSDI | USENIX | 12 pages | 14 pages | Unlimited |\n| NSDI | USENIX | 12 pages | 14 pages | Unlimited |\n| SOSP | ACM SIGOPS | 12 pages (tech content) | — | Unlimited |\n| ASPLOS | ACM SIGPLAN | 11 pages | 13 pages | Unlimited |\n| EuroSys | ACM | 12 pages | — | Unlimited |\n\nBased on 2025\u002F2026 CFPs. Verify current limits before submission.\n\n---\n\n## Writing Philosophy\n\n### Manage Reader State (Gernot Heiser)\nTreat the reader's cognitive load like an OS managing process state. Never introduce a concept without context. Never reference something defined later without a forward pointer.\n\n### Six-Dimensional Quality (Levin & Redell)\nSelf-check against: **Original Ideas**, **Reality** (is it built?), **Lessons** (what did you learn?), **Choices** (alternatives discussed?), **Context** (related work fair?), **Presentation** (clear writing?).\n\n### Page-One Figure (hzwer)\nInclude a figure on the first page that captures the core idea. Reviewers form first impressions from the title, abstract, and page-one figure.\n\n---\n\n## Academic Integrity Requirements\n\n### Citation Discipline\n- **Never generate citations from memory.** Use ml-paper-writing's citation verification workflow (Semantic Scholar \u002F DBLP \u002F CrossRef APIs).\n- Mark unverified references as `[CITATION NEEDED]`.\n\n### Prohibition of Fabrication\n- Do NOT fabricate production observations, traces, deployment experiences, or experimental results.\n- Do NOT generate fake venue rules, paper metadata, or best-paper claims.\n- Do NOT copy paragraph-level text from reference papers. This blueprint provides **structural guidance**, not copy-paste templates.\n\n### LLM Disclosure\n- Some venues require disclosure of substantial LLM use in writing or ideation. Check each venue's AI policy in the current CFP.\n\n### Attribution\n- When structures are inspired by specific papers (e.g., Lucid's gap-analysis pattern), cite the inspiration.\n- Cross-repository references (e.g., ARIS paper-slides structure) are attributed, not copied.\n\n### Temporal Validity\n- Venue rules (page limits, format, AI policies) change annually. All venue information in this skill is based on 2025\u002F2026 CFPs. **Always verify against the current year's CFP.**\n\n---\n\n## Workflow: Structuring a New Systems Paper\n\n```text\nStep 1: Read this SKILL.md for page allocation overview\nStep 2: Read references\u002Fsection-blueprints.md for per-section paragraph templates\nStep 3: Choose a writing pattern from references\u002Fwriting-patterns.md\nStep 4: Draft section by section following the blueprint\nStep 5: Run the checklist from references\u002Fchecklist.md before submission\nStep 6: Use ml-paper-writing for citation verification and LaTeX formatting\n```\n\n### Quick Checklist\n\n- [ ] Thesis statement follows \"X is better for Y in Z\" formula\n- [ ] Introduction has numbered contributions (3–5)\n- [ ] Each contribution maps to a paper section\n- [ ] Design discusses alternatives for every major choice\n- [ ] Every eval conclusion stated 3 times (hypothesis, result, caption)\n- [ ] Related work grouped by methodology, not individual papers\n- [ ] Page budget within venue limits\n- [ ] All citations verified programmatically (no hallucinated references)\n\n---\n\n## Common Issues and Solutions\n\n| Issue | Solution |\n|-------|----------|\n| Paper feels like a \"feature list\" | Restructure around thesis formula: X better for Y in Z |\n| Evaluation lacks depth | Add ablation experiments isolating each design decision |\n| Reviewers say \"incremental\" | Strengthen gap analysis: make G1–Gn crisper with evidence |\n| Design section too long | Move implementation details to S4, keep S3 at design level |\n| Motivation feels weak | Add production observations with concrete numbers |\n| Related work reads like a bibliography | Group by approach, add explicit differentiation |\n\n---\n\n## References\n\n### Writing Guidance\n- [references\u002Fsection-blueprints.md](references\u002Fsection-blueprints.md) — Detailed per-section paragraph templates with authoritative source quotes and best-paper structural examples\n- [references\u002Fwriting-patterns.md](references\u002Fwriting-patterns.md) — Four writing patterns with concrete paper examples\n\n### Venue-Specific\n- [references\u002Fchecklist.md](references\u002Fchecklist.md) — 7-stage pre-submission checklist covering structure, writing quality, evaluation rigor, design quality, academic integrity, venue-specific requirements (OSDI\u002FNSDI\u002FASPLOS\u002FSOSP\u002FEuroSys), and final pass\n- [references\u002Fsystems-conferences.md](references\u002Fsystems-conferences.md) — Conference overview, deadlines, track descriptions, formatting requirements, submission rules, and format conversion guides\n- [references\u002Freviewer-guidelines.md](references\u002Freviewer-guidelines.md) — How systems conference reviewers evaluate papers, with venue-specific criteria and common concerns\n\n### LaTeX Templates\n- [templates\u002Fosdi2026\u002F](templates\u002Fosdi2026\u002F) — OSDI 2026 (USENIX format)\n- [templates\u002Fnsdi2027\u002F](templates\u002Fnsdi2027\u002F) — NSDI 2027 (USENIX format)\n- [templates\u002Fasplos2027\u002F](templates\u002Fasplos2027\u002F) — ASPLOS 2027 (ACM SIGPLAN format)\n- [templates\u002Fsosp2026\u002F](templates\u002Fsosp2026\u002F) — SOSP 2026 (ACM SIGPLAN format)\n",{"name":5,"tags":60,"author":63,"license":15,"version":64,"category":65,"description":7},[36,47,50,49,48,61,62,45,40],"EuroSys","Structural Blueprint","Orchestra Research","1.1.0","ai-research","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Fqc-systems-paper-writing","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill systems-paper-writing",{"tool":81,"command":82},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill systems-paper-writing",{"tool":84,"command":85},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill systems-paper-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002FSKILL.md",true,[89,95,99,103,107,111,117,121,125,129,133,137,141,144,148],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fchecklist.md","REFERENCE","参考文档",11896,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Freferences\u002Fchecklist.md",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Freviewer-guidelines.md",4585,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Freferences\u002Freviewer-guidelines.md",{"path":100,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fsection-blueprints.md",16479,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Freferences\u002Fsection-blueprints.md",{"path":104,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fsystems-conferences.md",10256,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Freferences\u002Fsystems-conferences.md",{"path":108,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fwriting-patterns.md",9447,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Freferences\u002Fwriting-patterns.md",{"path":112,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":115,"sourceHtmlUrl":116},"templates\u002Fasplos2027\u002Fmain.tex","OTHER","其他",15845,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fasplos2027\u002Fmain.tex",{"path":118,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":119,"sourceHtmlUrl":120},"templates\u002Fasplos2027\u002Freferences.bib",5172,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fasplos2027\u002Freferences.bib",{"path":122,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":123,"sourceHtmlUrl":124},"templates\u002Fnsdi2027\u002Fmain.tex",15006,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Fmain.tex",{"path":126,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":127,"sourceHtmlUrl":128},"templates\u002Fnsdi2027\u002Freferences.bib",5848,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Freferences.bib",{"path":130,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":131,"sourceHtmlUrl":132},"templates\u002Fnsdi2027\u002Fusenix-2020-09.sty",2294,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Fusenix-2020-09.sty",{"path":134,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":135,"sourceHtmlUrl":136},"templates\u002Fosdi2026\u002Fmain.tex",14716,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Fmain.tex",{"path":138,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":139,"sourceHtmlUrl":140},"templates\u002Fosdi2026\u002Freferences.bib",5785,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Freferences.bib",{"path":142,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":131,"sourceHtmlUrl":143},"templates\u002Fosdi2026\u002Fusenix-2020-09.sty","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Fusenix-2020-09.sty",{"path":145,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":146,"sourceHtmlUrl":147},"templates\u002Fsosp2026\u002Fmain.tex",17451,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fsosp2026\u002Fmain.tex",{"path":149,"resourceType":113,"resourceTypeDesc":114,"sizeBytes":150,"sourceHtmlUrl":151},"templates\u002Fsosp2026\u002Freferences.bib",5395,"https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqc-systems-paper-writing\u002Ftemplates\u002Fsosp2026\u002Freferences.bib",[153,182,205,230,255,279],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":162,"publishedAt":55},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[159],{"categoryNo":160,"categoryName":161,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[163,164,165,166,167,168,169,170,171,172,173,174,175,176,177,178,53,179,180,181],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","browsing","request","youtube transcripts",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":55},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[189,190,191,54,167,192,193,194,195,196,197,198,199,200,43,201,202,203,204,53],"twitter","x twitter growth","growth","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","platform","grow","posting","competitive",{"skillNo":206,"name":207,"nameZh":6,"description":208,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":209,"categories":210,"keywords":212,"publishedAt":55},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[211],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[213,199,214,215,216,217,218,219,43,220,221,66,222,223,224,225,226,227,228,229],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":236,"publishedAt":55},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[237,238,239,240,241,242,243,244,245,43,246,174,247,248,249,250,251,252,253,254],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":256,"name":257,"nameZh":6,"description":258,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":259,"categories":260,"keywords":262,"publishedAt":55},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[261],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[263,264,265,266,267,215,242,268,269,270,271,272,199,273,173,274,275,276,277,278],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":280,"name":281,"nameZh":6,"description":282,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":283,"categories":284,"keywords":285,"publishedAt":55},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[286,287,288,289,290,291,292,293,294,271,295,296,297,298,299,300,175,301,302,254],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]