PODC Skills

A 12-skill depth pack for ACM PODC (Symposium on Principles of Distributed Computing), the SIGACT-SIGOPS distributed-computing-theory flagship: routing among PODC/DISC/SPAA/STOC/SODA, the lightweight double-blind HotCRP submission, the 10-page ACM proceedings budget with unbounded full version, proof-appendix and model/assumption rigor (in place of artifact evaluation), the Brief Announcements tra

by @brycewang-stanford 10 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/podc-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 10 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-podc-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: 10
authors: 1

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

Skills in this plugin

▌
Podc Submission · brycewang-stanford
Use when auditing an ACM PODC submission for HotCRP readiness, covering the two-step abstract-registration then full-paper deadline, the ACM Master template with the 10-page-merits budget and unbounded full version, lightweight double-blind anonymization, the regular-paper-vs-Brief-Announcement choice, and desk-risk triage before the AoE cutoff.

1k repo stars
▌
Podc Experiments · brycewang-stanford
Use when building the evidence for an ACM PODC paper — where "evidence" is a proof, not a benchmark. Covers matching upper and lower bounds, tightness arguments, model and assumption stress-tests, adversary-strength calibration, and the honest, clearly-optional role of any simulation in a distributed-computing-theory paper.

1k repo stars
▌
Podc Camera Ready · brycewang-stanford
Use when preparing an accepted ACM PODC paper for the proceedings — de-anonymizing after lightweight double-blind, compressing to the 10-page two-column ACM proceedings format without losing the proof map, completing ACM rights/eRights metadata and CCS concepts, and posting the synchronized full version with all proofs to arXiv.

1k repo stars
▌
Podc Related Work · brycewang-stanford
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.

1k repo stars
▌
Podc Supplementary · brycewang-stanford
Use when deciding what goes in the first 10 read-guaranteed pages of an ACM PODC submission versus the full version / appendix, and when choosing between a regular paper and a Brief Announcement — so that nothing which decides acceptance lives past page 10 and every deferred proof remains reachable.

1k repo stars
▌
Podc Writing Style · brycewang-stanford
Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result stated as a theorem up front, a proof architecture the reader can navigate, and the 10-page-merits discipline) so the merits case lands within the first 10 pages a PODC committee is guaranteed to read.

1k repo stars
▌
Podc Review Process · brycewang-stanford
Use when reasoning about how an ACM PODC submission is evaluated — covering lightweight double-blind review, a program committee that reads proofs, the accept/reject decision with no journal-style revision round, the Brief Announcements track's lighter bar, and how PODC's process differs from DISC, SPAA, and the sequential-theory venues STOC/FOCS/SODA.

1k repo stars
▌
Podc Author Response · brycewang-stanford
Use when writing an ACM PODC rebuttal/author response, if the cycle runs one — covering how to correct a proof misreading, supply a missing lemma or bound within the anonymity envelope, prioritize soundness questions over taste, and behave correctly given that PODC has no revision round to fall back on.

1k repo stars
▌
Podc Reproducibility · brycewang-stanford
Use when making an ACM PODC paper's result independently checkable — reproducibility for a proofs venue, not an artifact venue. Covers a self-contained proof appendix, an explicit and checkable model/assumption box, honest handling of any optional simulation, and keeping the full version (with proofs) in sync with the 10-page camera-ready.

1k repo stars
▌
Podc Topic Selection · brycewang-stanford
Use when deciding whether a distributed-computing result belongs at ACM PODC or should be routed to DISC, SPAA, OPODIS/SIROCCO/SSS, STOC/FOCS/SODA, a systems venue (ICDCS/DSN/OSDI/NSDI), a blockchain-theory venue (AFT/FC), or a journal (JACM / Distributed Computing) — and how to avoid the PODC-vs-PODS naming trap by reasoning about the distributed model and the cost measure.

1k repo stars