PPoPP Skills

A 12-skill depth pack for PPoPP (ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming): venue routing against PLDI/CGO/POPL/SC/ASPLOS, the two-column acmart sigplan 10-page format, double-blind HotCRP submission with an author-response rebuttal, concurrency-correctness and parallel-performance evidence (scalability, NUMA, GPU, lock-free/wait-free structures, memory models), the

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/ppopp-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 12 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-ppopp-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 12
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Ppopp Workflow · brycewang-stanford
Use when planning a PPoPP submission campaign end to end, sequencing the summer paper deadline, the author-response rebuttal window, notification, the post-acceptance CGO-shared artifact-evaluation round, the camera-ready, and the presentation inside the co-located HPCA/CGO/PPoPP/CC week.

1k repo stars
▌
Ppopp Submission · brycewang-stanford
Use when auditing a PPoPP research-paper submission for HotCRP readiness, covering the two-column acmart sigplan template, the 10-page text+figures budget with unlimited references, the 100-400 word abstract, double-blind anonymity for parallel-systems work, conflict declaration against the PC and External Review Committee, and desk-reject triage before the AoE cutoff.

1k repo stars
▌
Ppopp Experiments · brycewang-stanford
Use when designing or auditing a PPoPP paper's evaluation, covering the twin bar of concurrency correctness and measured scalability — speedup curves, strong vs weak scaling, core/thread sweeps, NUMA and GPU effects, contention microbenchmarks plus real workloads, variance and measurement hygiene, and honest strong baselines.

1k repo stars
▌
Ppopp Camera Ready · brycewang-stanford
Use when preparing a PPoPP camera-ready, covering systematic de-anonymization, ACM rights/eRights and CCS concepts metadata, restoring the named hardware and acknowledgements, permanentizing the artifact DOI and any earned badges, and passing ACM production checks for the two-column acmart sigplan proceedings.

1k repo stars
▌
Ppopp Related Work · brycewang-stanford
Use when writing or auditing a PPoPP paper's related-work and positioning, covering the parallel-programming literature lanes (concurrent data structures, runtimes/schedulers, GPU/accelerators, memory models, parallel algorithms), delta-first comparison against the nearest competitor, double-blind self-citation, and separating PPoPP work from CGO/PLDI/POPL/SC neighbors.

1k repo stars
▌
Ppopp Supplementary · brycewang-stanford
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.

1k repo stars
▌
Ppopp Writing Style · brycewang-stanford
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.

1k repo stars
▌
Ppopp Review Process · brycewang-stanford
Use when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer matching, the author-response rebuttal, the accept/reject decision with automatic poster consideration, and how PPoPP's process differs from PLDI's and CGO's.

1k repo stars
▌
Ppopp Author Response · brycewang-stanford
Use when writing a PPoPP author-response rebuttal, covering the short fixed word-capped window, answering the recurring "does it scale?" and "what about baseline X?" questions with pre-run numbers, correcting factual misreadings of a concurrency argument, staying double-blind, and prioritizing the points that can actually move a decision.

1k repo stars
▌
Ppopp Reproducibility · brycewang-stanford
Use when making a PPoPP paper's parallel-performance results reproducible, covering the hardware and topology description reviewers re-run, thread pinning and NUMA control, seeds and warm-up, compiler/driver/flag provenance, and building an environment that reproduces the paper's scaling trend on different machines.

1k repo stars
▌
Ppopp Topic Selection · brycewang-stanford
Use when deciding whether a parallel/concurrent-computing project belongs at PPoPP or should be routed to PLDI, CGO, POPL, ASPLOS, HPCA, SC, SPAA, or OOPSLA, and when distinguishing PPoPP's "the parallelism is the point" scope from a compiler contribution (CGO/PLDI), a concurrency logic (POPL), or a microarchitecture result (ASPLOS/HPCA).

1k repo stars
▌
Ppopp Artifact Evaluation · brycewang-stanford
Use when packaging a PPoPP artifact for the post-acceptance, CGO-shared artifact-evaluation track, covering PPoPP's specific badge policy (Functional or Reusable plus Results Reproduced, no "Results Replicated"; Available granted by the publisher from a deposit link), reproducible parallel measurements on evaluators' hardware, and the separate AE deadline.

1k repo stars