popl-related-work
Use when positioning a POPL paper in the semantics, type-systems, and verification literature — stating per-line technical deltas against the nearest formal systems, covering the PACMPL family and LICS/CAV/CPP/TOPLAS neighbors, citing PACMPL-era papers in journal form, and dblp-verifying every classic before it is attributed to POPL.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-related-work --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.
# POPL Related Work At POPL the related-work section is part of the *proof of novelty*: reviewers are specialists who know the three closest systems, and the section must say — precisely — what your formalism can do that each of them cannot, or what assumption of theirs you discharge. Venue-form facts below were checked 2026-07-08. ## Delta sentences, not tours Weak: "Much work has studied gradual typing [1-9]." Strong: each nearest neighbor gets a sentence with a technical object in it — - "[X]'s soundness needs whole-program compilation; our Theorem 5 holds under separate compilation because the logical relation is defined on open terms." - "Our rules coincide with [Y] on the pure fragment (Prop. 2) and diverge exactly at effect handlers, which [Y] does not treat." If you cannot write the delta sentence, you have not finished reading the neighbor paper — or the delta does not exist, which is a `popl-topic-selection` conversation. ## The neighborhood map | Where the closest work lives | Typical relationship to your POPL paper | |---|---| | POPL / PACMPL Issue POPL | The direct predecessors; deltas must be theorem-level | | ICFP, OOPSLA, PLDI (same PACMPL journal) | Same idea famil
- Delta sentences, not tours
- The neighborhood map
- Cite the PACMPL era correctly
- Verify before attributing
- Output format
What does the popl-related-work skill do?
Use when positioning a POPL paper in the semantics, type-systems, and verification literature — stating per-line technical deltas against the nearest formal systems, covering the PACMPL family and LICS/CAV/CPP/TOPLAS neighbors, citing PACMPL-era papers in journal form, and dblp-verifying every classic before it is attributed to POPL.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill popl-related-work --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.