systems-paper-writing

Generate reviewer-aligned section and paragraph blueprints for systems conference papers.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/box755/simlens-research --skill systems-paper-writing-box755
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systems-paper-writing
Source: https://github.com/box755/simlens-research/tree/main/skill-packs/AI-Research-SKILLs/20-ml-paper-writing/systems-paper-writing
Command: npx skills add https://github.com/box755/simlens-research --skill systems-paper-writing-box755

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of turning your systems research into a submission-ready paper with venue-appropriate structure, section-level intent, and paragraph-level blueprints for major sections of OSDI/OSDI-like and other top systems venues.

Core Features & Use Cases

  • Paragraph-level structural blueprints for 10–12 page systems papers: page allocation and what each paragraph must accomplish in order (e.g., Introduction problem→gap→thesis→contributions; Design architecture→modules→trade-offs).
  • Venue-specific checklists and reviewer-focused guidance: submission/camera-ready page budget reminders plus self-check items aligned with how systems reviewers evaluate clarity, novelty, design, and evaluation rigor.
  • Evaluation and integrity guardrails: an explicit evaluation section plan (setup, end-to-end, ablations, scalability) and strict rules for citation/data integrity (e.g., mark [CITATION NEEDED] rather than fabricating).

Use this when you are writing a systems conference paper for venues like OSDI, SOSP, ASPLOS, NSDI, and EuroSys and you want a concrete, reviewer-aligned outline rather than generic academic writing advice.

Quick Start

Use the systems-paper-writing Skill to draft an OSDI (or SOSP/ASPLOS/NSDI/EuroSys) paper by mapping each section (S1–S7) to the provided paragraph templates and page budget.

Frequently Asked Questions about systems-paper-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a systems paper for OSDI or SOSP to meet page budgets?

To structure a systems paper for OSDI or SOSP, map sections to paragraph-level blueprints that allocate a 10-12 page budget, ensuring the introduction covers the problem, gap, thesis, and contributions sequentially.

What should be included in the evaluation section of an ASPLOS or EuroSys paper?

An evaluation section for an ASPLOS or EuroSys paper must include setup, end-to-end tests, ablations, and scalability checks to satisfy reviewer expectations for rigorous systems research validation.

Can I use LaTeX templates for writing NSDI conference papers with paragraph-level guidance?

Yes, you can use LaTeX templates alongside paragraph-level structural blueprints to draft NSDI conference papers, mapping each section to specific paragraph intents and strict page-budget constraints.

How to avoid fabricating references when drafting systems conference papers?

To avoid fabricating references when drafting systems conference papers, enforce strict citation discipline by explicitly marking missing sources with [CITATION NEEDED] rather than generating false bibliographic entries.

Does writing a top-tier systems paper require venue-specific checklists for reviewer alignment?

Writing a top-tier systems paper requires venue-specific checklists to validate submission criteria, page budgets, and reviewer-focused guidance on clarity, novelty, design, and evaluation rigor.

What is the best way to outline design trade-offs in a systems paper?

The best way to outline design trade-offs in a systems paper is to structure the design section sequentially from overall architecture to specific modules, explicitly detailing the engineering trade-offs involved.