[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MB82BQDZ7HQ5WRJEKB4W5C":3,"skill-same:01M6MB82BQDZ7HQ5WRJEKB4W5C":155},{"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":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":71,"repositoryHtmlUrl":72,"repositoryHomepageUrl":73,"ownerHtmlUrl":74,"ownerBlogUrl":75,"ownerDescription":76,"updatedAt":77,"install":78,"resources":91},"01M6MB82BQDZ7HQ5WRJEKB4W5C","systems-paper-writing",null,"Provides paragraph-level structural blueprints for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Covers page budgets per section, writing patterns (gap analysis, observation-driven, contribution list, thesis formula), evaluation structure, venue checklists, reviewer guidelines, deadlines, and LaTeX templates for OSDI, NSDI, ASPLOS, and SOSP. Use when planning the section and page layout of a systems paper. Use when drafting an introduction, motivation, design, or evaluation section. Use when checking a draft against venue page limits and a pre-submission checklist. Use when anticipating how systems reviewers will assess a paper. Use when looking up conference formats or deadlines. For NeurIPS\u002FICML\u002FICLR papers or citation verification, use ml-paper-writing instead.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"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,55,56,57],"writing","Systems Paper Writing","paper","systems","Paper Writing","OSDI","drafting","limits","section","design","for","formats","SOSP","ASPLOS","NSDI","gap analysis","guidelines","Evaluation","citation verification","structure","use","list","how","2026-11-10 10:12:30",false,"---\nname: systems-paper-writing\ndescription: Provides paragraph-level structural blueprints for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Covers page budgets per section, writing patterns (gap analysis, observation-driven, contribution list, thesis formula), evaluation structure, venue checklists, reviewer guidelines, deadlines, and LaTeX templates for OSDI, NSDI, ASPLOS, and SOSP. Use when planning the section and page layout of a systems paper. Use when drafting an introduction, motivation, design, or evaluation section. Use when checking a draft against venue page limits and a pre-submission checklist. Use when anticipating how systems reviewers will assess a paper. Use when looking up conference formats or deadlines. For NeurIPS\u002FICML\u002FICLR papers or citation verification, use ml-paper-writing instead.\nlicense: MIT\nmetadata:\n  version: 1.1.0\n  category: research-writing\n  maintainer: Kalaris Labs\n  tags: 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,"license":15,"metadata":63,"description":7},{"tags":64,"version":65,"category":66,"maintainer":67},"Systems Paper Writing, OSDI, SOSP, ASPLOS, NSDI, EuroSys, Structural Blueprint, Academic Writing, LaTeX","1.1.0","research-writing","Kalaris Labs","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":90},[80,83,86],{"tool":81,"command":82},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill systems-paper-writing",{"tool":84,"command":85},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill systems-paper-writing",{"tool":87,"command":88},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill systems-paper-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002FSKILL.md",true,[92,98,102,106,110,114,120,124,128,132,136,140,144,147,151],{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fchecklist.md","REFERENCE","参考文档",11896,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Freferences\u002Fchecklist.md",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Freviewer-guidelines.md",4585,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Freferences\u002Freviewer-guidelines.md",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fsection-blueprints.md",16452,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Freferences\u002Fsection-blueprints.md",{"path":107,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fsystems-conferences.md",10256,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Freferences\u002Fsystems-conferences.md",{"path":111,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fwriting-patterns.md",9447,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Freferences\u002Fwriting-patterns.md",{"path":115,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":118,"sourceHtmlUrl":119},"templates\u002Fasplos2027\u002Fmain.tex","OTHER","其他",15845,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fasplos2027\u002Fmain.tex",{"path":121,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":122,"sourceHtmlUrl":123},"templates\u002Fasplos2027\u002Freferences.bib",5172,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fasplos2027\u002Freferences.bib",{"path":125,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":126,"sourceHtmlUrl":127},"templates\u002Fnsdi2027\u002Fmain.tex",15006,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Fmain.tex",{"path":129,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":130,"sourceHtmlUrl":131},"templates\u002Fnsdi2027\u002Freferences.bib",5848,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Freferences.bib",{"path":133,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":134,"sourceHtmlUrl":135},"templates\u002Fnsdi2027\u002Fusenix-2020-09.sty",2294,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fnsdi2027\u002Fusenix-2020-09.sty",{"path":137,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":138,"sourceHtmlUrl":139},"templates\u002Fosdi2026\u002Fmain.tex",14716,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Fmain.tex",{"path":141,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":142,"sourceHtmlUrl":143},"templates\u002Fosdi2026\u002Freferences.bib",5785,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Freferences.bib",{"path":145,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":134,"sourceHtmlUrl":146},"templates\u002Fosdi2026\u002Fusenix-2020-09.sty","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fosdi2026\u002Fusenix-2020-09.sty",{"path":148,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":149,"sourceHtmlUrl":150},"templates\u002Fsosp2026\u002Fmain.tex",17451,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fsosp2026\u002Fmain.tex",{"path":152,"resourceType":116,"resourceTypeDesc":117,"sizeBytes":153,"sourceHtmlUrl":154},"templates\u002Fsosp2026\u002Freferences.bib",5395,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fsystems-paper-writing\u002Ftemplates\u002Fsosp2026\u002Freferences.bib",[156,165,173,181,189,197],{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":164},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":172,"publishedAt":164},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":164},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":185,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":164},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":193,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":164},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":201,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":164},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]