ppopp-writing-style
Use when drafting or tightening a PPoPP paper's prose and structure, covering the two-column acmart sigplan layout, the 10-page text+figures budget, stating the concurrency-correctness and scalability claim up front, presenting speedup curves and core sweeps, and the parallel-programming conventions PPoPP reviewers expect.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PPoPP Writing Style Write to the PPoPP bar: a parallel-programming contribution that is **correct under concurrency and measurably scalable**, presented in **two-column `acmart` `sigplan`** within **10 pages** of text and figures (references unlimited). The reader is a parallel-systems expert who will look for the speedup curve, the baseline, and the correctness argument before they finish the introduction. ## The first-page contract By the end of page 1 a PPoPP reviewer should know: 1. **The parallel-programming problem** — what breaks or stalls when you go parallel (contention, a sequential bottleneck, poor locality, divergence, a memory-model hazard). 2. **The contribution** — the structure, runtime, algorithm, or technique, in one sentence, framed so parallelism is clearly the point (not a compiler pass or a proof in disguise). 3. **The twin claim** — that it is correct under concurrency *and* how much it scales, with the headline number ("linear to 96 cores," "1.8× over the state-of-the-art lock-free map at 64 threads"). 4. **The evidence shape** — the hardware, the workloads, and the baseline you beat. A PPoPP introduction that describes a mechanism but never states a scali
- The first-page contract
- Two-column, 10-page discipline
- Structure that fits the venue
- Presenting parallel performance
- Language conventions
- Common PPoPP writing failures
- Output format
What does the ppopp-writing-style skill do?
Use when drafting or tightening a PPoPP paper's prose and structure, covering the two-column acmart sigplan layout, the 10-page text+figures budget, stating the concurrency-correctness and scalability claim up front, presenting speedup curves and core sweeps, and the parallel-programming conventions PPoPP reviewers expect.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.