pldi-supplementary
Use when deciding what accompanies a PLDI submission beyond the 20 text pages — full proofs, extended benchmark data, anonymized code — and how to keep every extra byte double-blind, optional for reviewers, and consistent with the main PDF under summary-rejection formatting rules.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-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.
# PLDI Supplementary Material PLDI's cap is on *text pages excluding bibliography* in the main submission (20 for the 2026 cycle); everything else — complete proofs, full benchmark tables, anonymized implementations — is supporting material whose exact submission mechanics (appendix inside the PDF vs separate upload, size limits, reviewer obligations) are reset per cycle and were **not fully visible for 2026 (待核实)**. Decide placement by role first, then check the live CFP for the mechanics. ## Placement by role | Material | Where it belongs | Why | |---|---|---| | Proof sketches of main theorems | Main text | Reviewers judge soundness from the body | | Full proofs, case analyses | Appendix/supplement | Depth on demand; body states theorem + sketch | | Headline benchmark results | Main text | The claim lives or dies here | | Per-benchmark raw tables, extra configurations | Supplement | Evidence of thoroughness, not the argument | | Anonymized source code | Anonymous link or upload | Early credibility; becomes the AE artifact later | | Semantics figures too large for the text block | Rethink first | If reviewers need it to follow §4, it is not supplementary | The governing rule: **th
- Placement by role
- Anonymity extends to every byte
- Consistency contract with the main PDF
- Timing
- Output format
Sweep an anonymized code drop before upload rm -rf pkg/.git pkg/.github grep -rniE 'copyright|@[a-z0-9.-]+\.(edu|org|com)|university|author' pkg/ | head find pkg/ \( -name '*.DS_Store' -o -name '*.orig' -o -path '*__pycache__*' \) -delete tar tzf pkg.tgz | grep -Ei '/home/|/Users/' && echo "LEAK: user paths in archive"
What does the pldi-supplementary skill do?
Use when deciding what accompanies a PLDI submission beyond the 20 text pages — full proofs, extended benchmark data, anonymized code — and how to keep every extra byte double-blind, optional for reviewers, and consistent with the main PDF under summary-rejection formatting rules.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-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.