ppopp-supplementary
Use when deciding what belongs in a PPoPP paper's 10 reviewed pages versus the artifact or appendix, splitting content by decision-criticality so proofs, full core sweeps, and correctness arguments that determine acceptance stay legible in the body, while bulk data and extended runs move out.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-supplementary --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 Supplementary Decide what lives in the **10 reviewed pages** (text and figures, two-column `acmart`) and what moves to the artifact or an appendix. The governing rule at PPoPP is **decision-criticality**: anything a reviewer must read to be convinced the result is **correct under concurrency** and **scales** stays in the body. References are unlimited and free; body space is the scarce resource. ## The decision-criticality test For each candidate piece of content, ask: *would a reviewer's accept/reject change if they could not see this?* ```text [Decides acceptance] the correctness argument's core, the headline scaling curve, the baseline comparison, the key design insight -> BODY (inside 10 pages) [Supports/confirms] full linearizability proof details, every core-count data point, additional workloads, sensitivity sweeps, extra GPUs -> ARTIFACT / APPENDIX [Bulk / mechanical] raw logs, per-run tables, generator internals, build scripts -> ARTIFACT ``` The failure mode PPoPP punishes is burying a load-bearing argument — the linearization points, the one plot that shows saturation — outside the reviewed pages, so the reviewer cannot judge the claim and defaults to skepticism.
- The decision-criticality test
- What must stay in the body
- What can move out
- Where "out" is at PPoPP
- Keeping the body legible under the page cap
- Output format
What does the ppopp-supplementary skill do?
Use when deciding what belongs in a PPoPP paper's 10 reviewed pages versus the artifact or appendix, splitting content by decision-criticality so proofs, full core sweeps, and correctness arguments that determine acceptance stay legible in the body, while bulk data and extended runs move out.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-supplementary --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.