podc-related-work
Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, and keeping self-citation safe under lightweight double-blind review.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-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.
# PODC Related Work Position against results, not topics. In distributed-computing theory a "related" paper is one that proves a **bound in a comparable model**, and your delta must be stated in the currency the field uses: **model + problem + cost measure + bound**. A related-work section that lists topics ("several works study consensus") without the bounds and models tells a PODC reviewer nothing. ## The literature lanes - **PODC and DISC** — the two distributed-theory flagships; most of your closest prior bounds live here. They share the Dijkstra Prize and Dissertation Award and much of a reviewer pool, so their results are the ones your reviewers know best. - **SPAA** — parallel algorithms/architectures; relevant for shared-memory and concurrency results, less so for message-passing/fault-tolerance. - **STOC / FOCS / SODA** — where a distributed result's *sequential* core or a key combinatorial lemma may have appeared; cite when your technique descends from sequential theory. - **Journals — JACM and *Distributed Computing*** — the archival, definitive versions of many results (FLP, partial synchrony, linearizability). Cite the **journal version** for the canonical statement, a
- The literature lanes
- Write the delta in the field's currency
- Distinguish your model from neighbors
- Positioning your contribution
- Self-citation under lightweight double-blind
- Common failures
- Output format
What does the podc-related-work skill do?
Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes (PODC/DISC/SPAA and the JACM / Distributed Computing journals), writing a model-and-bound-precise delta over prior results, distinguishing your model from neighboring ones, and keeping self-citation safe under lightweight double-blind review.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-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.