Skill UI

This guide outlines the rigorous standards for writing top-tier distributed systems conference papers. It details the mandatory narrative arc—moving from an operational pain point to a named design principle—and emphasizes that every claim must be supported by precise, measured evidence (e.g., percentiles and specific workloads) rather than relying on superlatives or vague adjectives. It also provides guidance on structuring the argument, budgeting page space, and designing figures as core evidence.

A comprehensive guide for authors aiming to submit top-tier technical papers (like those for OOPSLA). It teaches how to transform descriptive drafts into highly verifiable, structured academic arguments. Focus areas include developing running examples, articulating falsifiable claims, optimizing article pacing, and anticipating reviewer challenges to maximize the chances of acceptance.

A comprehensive guide for rigorously positioning an Operations Research (OR) manuscript against prior art. It teaches authors to move beyond vague 'gap' statements by constructing a precise, technical delta against 3-5 closest papers. Focus areas include weakening assumptions, improving bounds, enhancing algorithmic complexity, and defining new operational regimes, often presented in a structured comparison table to satisfy technical reviewers.

This guide provides a comprehensive framework for authors responding to major journal revisions. It teaches how to structure a technical, point-by-point rebuttal, systematically closing proof gaps, strengthening assumptions, incorporating missing baselines, and preparing the entire codebase and data for professional reproducibility review.

A comprehensive guide to the Operations Research (OR) academic publishing review process. This guide explains the departmental editorial routing, the soft double-anonymous review model, and how to interpret complex decision letters (Reject, Major/Minor Revision, Accept). It details the roles of Area and Associate Editors, and provides actionable strategies for authors to strengthen their technical contributions and respond effectively to reviewer feedback.

A comprehensive guide detailing the specific narrative arc and strict formatting rules for writing technical papers for top-tier system conferences like OSDI. It teaches authors how to structure an argument—from identifying operational pain points to proposing a novel mechanism and presenting measurable results—while adhering to strict constraints such as the 12-page limit and avoiding appendices. This skill focuses on improving scholarly communication and technical clarity.

This comprehensive guide outlines the specific structural, stylistic, and scientific standards required for submitting papers to Pervasive Computing (PerCom) venues. It helps researchers elevate technically sound work by ensuring the narrative strongly emphasizes the real-world, human-centered contribution of the pervasive system, focusing on cross-subject evidence, rigorous limitation discussion, and adherence to strict academic page limits.

This tool guides the process of positioning a comprehensive review essay within a highly technical and debated academic field. It helps users define the precise scope (corpus boundaries), map the major scholarly camps and core disagreements, and strategically locate their own intervention point, ensuring the review reads as authoritative and current.

Provides comprehensive guidelines for authors responding to reviewer objections after a major technical conference submission (e.g., PLDI). It details how to triage structural critiques—including factual errors, soundness doubts, and evaluation gaps—and emphasizes maintaining academic rigor, adhering strictly to the original scope, and avoiding promises of unproven new contributions.

This guide details how to structure and write the 'Related Work' section for highly competitive academic venues like PLDI. It emphasizes moving beyond simple citation listings by forcing the author to identify and articulate the specific technical 'delta' (improvement) their paper provides over every prior technique, while also covering inter-conference comparisons and proper bibliography formatting.

A comprehensive guide for authors submitting technical papers to top compiler and systems conferences (like PLDI). It teaches how to structure an argument as a rigorous engineering case, focusing on stating the 'hard case' first, describing mechanisms rather than using adjectives, and ensuring every claim is directly backed by evidence throughout the paper.

A comprehensive guide for crafting the PNAS-style scientific abstract. It details the required structure (single paragraph, ~250 words), the five-move narrative flow (Context, Gap, Approach, Results, Implication), and the critical distinction between the technical Abstract (What/How/Found) and the Significance Statement (Why it matters). Learn how to write accessible, quantified, and self-contained science summaries.