podc-submission
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-submission --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 Submission Run this audit before uploading to the PODC HotCRP site (`podc26.hotcrp.com` for the 2026 cycle). PODC — the ACM Symposium on Principles of Distributed Computing — judges a **model, a theorem, and a proof**, so the submission is read as a mathematical argument, not as a system or a study. Every number below was read from the PODC 2026 call for papers on 2026-07-09 via search renderings (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## The two-step deadline PODC 2026 separates **abstract registration** from **full-paper submission**, and both are AoE: - **Abstract registration** locks in title, abstract, authors, and conflicts a few days early (PODC 2026: **11 February 2026**). Miss it and the system will not accept the PDF later. - **Full-paper submission** uploads the anonymized PDF (PODC 2026: **16 February 2026**, 23:59 AoE). Register with the *real* title and abstract, not a placeholder — the abstract drives reviewer bidding among a specialized PC, and a registered abstract that diverges from the final paper quietly worsens your match. ## Regular paper or Brief Announcement — decide before formattin
- The two-step deadline
- Regular paper or Brief Announcement — decide before formatting
- Format and page budget
- Lightweight double-blind sweep
- The proof is the deliverable
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # scrub identifying metadata pdftotext paper.pdf - | grep -nEi 'university|@[a-z0-9.]+\.edu|acknowledg|grant|thanks' | head pdftotext paper.pdf - | grep -nEi 'our (previous|prior|earlier) (work|paper)|we showed in \[' | head
What does the podc-submission skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill podc-submission --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.