writing-systems-papers

Generate venue-aware paragraph structures for 10–12 page systems papers.

2|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill writing-systems-papers-raja21068
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-systems-papers
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/writing-systems-papers
Command: npx skills add https://github.com/raja21068/AutoResearch --skill writing-systems-papers-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a strong systems conference paper often fails at the “paragraph level” because authors lack venue-specific page budgeting, reusable paragraph roles, and consistent writing patterns.

Core Features & Use Cases

  • Venue-ready page allocation for 10–12 page systems papers (OSDI/SOSP/ASPLOS/NSDI/EuroSys) so every section fits the camera-ready constraints.
  • Paragraph-level blueprints for the abstract, introduction, background, design, implementation, evaluation, related work, and conclusion with explicit role templates.
  • Writing patterns that drive stronger structure such as Gap Analysis, Observation-Driven design, Contribution Lists, and the “X is better for Y in Z” thesis formula.
  • Use case: You need to convert a rough systems idea into a submission-ready outline where each paragraph has a job, evidence expectations, and a measurable evaluation plan.

Quick Start

Use this skill when you want fine-grained systems-paper structure guidance for an OSDI, SOSP, ASPLOS, NSDI, or EuroSys submission.

Frequently Asked Questions about writing-systems-papers

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 fit strict page budgets?

To structure a systems paper for OSDI or SOSP, you need venue-aware page allocation that assigns paragraph-level blueprints to each section, ensuring every part fits the 10–12 page camera-ready constraints.

What is the best way to write an evaluation section for an ASPLOS submission?

Writing an evaluation section for an ASPLOS submission requires paragraph-level blueprints with explicit role templates that define evidence expectations and a measurable evaluation plan.

How do I write a systems paper introduction that clearly states my contribution?

A systems paper introduction needs a Contribution List pattern and the thesis formula to enforce gap, observation, contribution, and thesis consistency across your paragraphs.

Can I generate a submission-ready outline from a rough systems idea?

Yes, you can convert a rough systems idea into a submission-ready outline where each paragraph has a specific job, evidence expectations, and a measurable evaluation plan.

Does this approach work for EuroSys and NSDI paper formats?

Yes, this venue-ready page allocation and paragraph-level blueprinting applies to drafting structures for EuroSys, NSDI, OSDI, SOSP, and ASPLOS systems papers.

Why do systems conference papers often fail at the paragraph level?

Systems conference papers fail at the paragraph level because authors lack venue-specific page budgeting, reusable paragraph roles, and consistent writing patterns to drive strong structure.