[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KQCDFWJTPACYTG2FRG252E":3,"skill-same:01M6KQCDFWJTPACYTG2FRG252E":147},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":13,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":69,"install":70,"resources":83},"01M6KQCDFWJTPACYTG2FRG252E","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.","endman100\u002Fskill-router-nexus","endman100","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31997019?v=4","01M6KPDX17BYDWW4RRB0TNGGMX","01M6KPDX64Y2QBEWVFG5W5PWPF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002FSKILL.md",[17,22,25,28],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"Paper Writing","writing","Systems Paper Writing","systems","paper","Structural Blueprint","EuroSys","for","orchestra","targeting","papers","SOSP","ASPLOS","NSDI","OSDI","structural","patterns","Blueprint","guide","reviewer","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]\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":59,"author":62,"license":14,"version":63,"description":7},[36,48,45,46,47,40,39,60,61],"Academic Writing","LaTeX","Orchestra Research","1.1.0","main","f19b254e8975d0bfddb394686706106930d7964d","AI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus","https:\u002F\u002Fgithub.com\u002Fendman100","2026-11-11 18:19:10",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add endman100\u002Fskill-router-nexus --skill systems-paper-writing",{"tool":76,"command":77},"bunx","bunx skills add endman100\u002Fskill-router-nexus --skill systems-paper-writing",{"tool":79,"command":80},"pnpm","pnpm dlx skills add endman100\u002Fskill-router-nexus --skill systems-paper-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002FSKILL.md",true,[84,90,94,98,102,106,112,116,120,124,128,132,136,139,143],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fchecklist.md","REFERENCE","参考文档",11896,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Freferences\u002Fchecklist.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Freviewer-guidelines.md",4585,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Freferences\u002Freviewer-guidelines.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fsection-blueprints.md",16479,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Freferences\u002Fsection-blueprints.md",{"path":99,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fsystems-conferences.md",10256,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Freferences\u002Fsystems-conferences.md",{"path":103,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fwriting-patterns.md",9447,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Freferences\u002Fwriting-patterns.md",{"path":107,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":110,"sourceHtmlUrl":111},"templates\u002Fasplos2027\u002Fmain.tex","OTHER","其他",15845,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fasplos2027\u002Fmain.tex",{"path":113,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":114,"sourceHtmlUrl":115},"templates\u002Fasplos2027\u002Freferences.bib",5172,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fasplos2027\u002Freferences.bib",{"path":117,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":118,"sourceHtmlUrl":119},"templates\u002Fnsdi2027\u002Fmain.tex",15006,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Fmain.tex",{"path":121,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":122,"sourceHtmlUrl":123},"templates\u002Fnsdi2027\u002Freferences.bib",5848,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Freferences.bib",{"path":125,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":126,"sourceHtmlUrl":127},"templates\u002Fnsdi2027\u002Fusenix-2020-09.sty",2294,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Fusenix-2020-09.sty",{"path":129,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":130,"sourceHtmlUrl":131},"templates\u002Fosdi2026\u002Fmain.tex",14716,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Fmain.tex",{"path":133,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":134,"sourceHtmlUrl":135},"templates\u002Fosdi2026\u002Freferences.bib",5785,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Freferences.bib",{"path":137,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":126,"sourceHtmlUrl":138},"templates\u002Fosdi2026\u002Fusenix-2020-09.sty","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Fusenix-2020-09.sty",{"path":140,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":141,"sourceHtmlUrl":142},"templates\u002Fsosp2026\u002Fmain.tex",17451,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fsosp2026\u002Fmain.tex",{"path":144,"resourceType":108,"resourceTypeDesc":109,"sizeBytes":145,"sourceHtmlUrl":146},"templates\u002Fsosp2026\u002Freferences.bib",5395,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FAI-Research\u002Fsystems-paper-writing\u002Fsystems-paper-writing\u002Ftemplates\u002Fsosp2026\u002Freferences.bib",[148,170,198,220,229,253],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":54},"01M6MPCT5BXVER8HQZTW3QE9AS","create-master","基于佛教经典文献，生成特定高僧大德的 AI 教学角色","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMetaphysics-and-Spirituality\u002FMaster-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMetaphysics-and-Spirituality\u002FMaster-skill\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000039","教师与教育",[159,160,161,162,163,164,165,166,167,168,169],"create master","master","create","生成","true","webfetch","edit","write","read","grep","Bash",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":180,"publishedAt":54},"01M6M43AKE95Y64E1JRXEF5QQ3","writing-dna-skill","从至少 20 篇完整文章中蒸馏可复用的写作 DNA，分析语言、文章结构、选题逻辑、素材策略、认知框架和视觉风格，并生成 Writing-DNA.md；按该 DNA 写作时会读取全部蒸馏产物和 5 篇相关原文。用于中英文作者、账号、品牌或出版物的风格分析与一致性写作。 Distill reusable Writing DNA from at least 20 complete articles for Chinese or English authors, publications, brands, and accounts; use for language, structure, topic logic, source strategy, cognitive-frame, and visual-style analysis.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fwriting-dna-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fwriting-dna-skill\u002FSKILL.md",[177,178,179],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},[181,182,35,183,184,185,186,187,188,189,190,191,192,162,193,194,195,41,196,197],"writing dna skill","DNA","strategy","english","logic","visual","structure","chinese","reusable","use","style","distill","analysis","frame","source","at","complete",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":202,"sourceHtmlUrl":203,"categories":204,"keywords":207,"publishedAt":54},"01M6M428TTCGQ4ME3KY99VN037","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fstop-slop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fstop-slop\u002FSKILL.md",[205,206],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},[208,209,210,211,212,213,214,50,215,190,216,217,218,41,219,35],"slop","stop slop","stop","drafting","when","drafts","https","prose","remove","editing","text","content",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":54},"01M6M41X0B7EBX42TK435DMGGR","shuorenhua","检查和清理中英文文本里的 AI 套路，适用于“去 AI 味”“说人话”“自然一点”“别像模板”“先标问题”这类改写和审稿需求；按场景控制力度，同时保留事实、术语、语域和责任主体。","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fshuorenhua\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fshuorenhua\u002FSKILL.md",[],[222,228],"文本",{"skillNo":230,"name":231,"nameZh":6,"description":232,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":233,"sourceHtmlUrl":234,"categories":235,"keywords":236,"publishedAt":54},"01M6M3ZD12WBEW5KXKDM4N6DFG","naming","Name products, SaaS, brands, open source projects, bots, and apps. Use when the user needs to name something, find a brand name, or pick a product name. Metaphor-driven process that produces memorable, meaningful names and avoids AI slop.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fnaming-main\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fnaming-main\u002FSKILL.md",[],[231,237,238,239,240,241,190,242,167,195,243,244,245,246,169,247,248,249,250,212,251,252,208],"repo","websearch","product name","apps","bots","view","brand","pick","gh","projects","open","saas","open source","product","describe","ai slop",{"skillNo":254,"name":255,"nameZh":6,"description":256,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":257,"sourceHtmlUrl":258,"categories":259,"keywords":261,"publishedAt":54},"01M6M3YVXAFAAWJ7F6JMPFREYE","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fhumanizer-zh\u002FSKILL.md",[260],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[262,263,264,167,166,165,35,162,228,265,208,210],"humanizer","zh","humanizer zh","翻译"]