PODS Skills

A 12-skill depth pack for ACM PODS (the SIGMOD/SIGACT Symposium on Principles of Database Systems), the database-THEORY symposium co-located with SIGMOD: routing theory work between PODS and its systems siblings, the multi-cycle-per-year submission calendar, lightweight double-anonymous EasyChair review with a revision/shepherd round, the acmsmall 15-page-plus-unlimited-references-and-appendix bud

by @brycewang-stanford 9 skills

Install

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

Or inside Claude Code

In the Plugins tab, add this marketplace:

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

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

Skills in this plugin

▌
Pods Submission · brycewang-stanford
Use when auditing an ACM PODS research submission for EasyChair readiness, covering the chosen cycle's abstract-then-paper deadlines, the acmsmall[review,anonymous] format and 15-page budget, the at-submission proof appendix, lightweight double-anonymity, the declared conflicts of interest, PACMMOD-track publication, and desk-risk triage before the AoE cutoff.

1k repo stars
▌
Pods Experiments · brycewang-stanford
Use when designing or auditing the analytical "evidence" of an ACM PODS paper — worst-case and average-case analyses, matching upper and lower bounds, dichotomy completeness, correct complexity assumptions, and the occasional empirical validation when a theory paper claims practicality — matching the rigor to the shape of each theoretical claim.

1k repo stars
▌
Pods Camera Ready · brycewang-stanford
Use when preparing an accepted ACM PODS paper for its PACMMOD-track camera-ready, covering de-anonymization, the final acmsmall format and PACMMOD journal metadata (DOI, ORCID, CCS concepts), integrating shepherd-required revision items without overclaiming, posting and DOI-linking the arXiv full version, and confirming registration and presentation.

1k repo stars
▌
Pods Supplementary · brycewang-stanford
Use when deciding what belongs in an ACM PODS paper body versus its at-submission appendix, covering the acmsmall 15-page budget, the rule that PODS forbids online/external appendices so all proofs ship with the submission, the body/appendix split for a theory paper, and double-anonymous supplementary hygiene.

1k repo stars
▌
Pods Writing Style · brycewang-stanford
Use when revising an ACM PODS paper for a precise model and result on the first page, exact theorem statements with matching bounds, complete and self-contained proofs (body plus at-submission appendix), honest assumptions and open cases, double-anonymous wording, and disciplined use of the acmsmall 15-page budget.

1k repo stars
▌
Pods Review Process · brycewang-stanford
Use when reasoning about how an ACM PODS submission is evaluated, covering lightweight double-anonymous review, the multi-cycle-per-year calendar, the two reviewing rounds within a cycle, the 48-hour rebuttal, the accept/reject/revision decision with a shepherded revision, PACMMOD-track publication, and how PODS differs from SIGMOD's rounds and ICDT's process.

1k repo stars
▌
Pods Author Response · brycewang-stanford
Use when drafting ACM PODS author responses, covering the short ~48-hour double-anonymous rebuttal that corrects misreadings of proofs and definitions, and — distinctively — the shepherded revision cover letter that maps every required item to a concrete change in the resubmitted paper and survives the shepherd's second read.

1k repo stars
▌
Pods Reproducibility · brycewang-stanford
Use when strengthening the verifiability of an ACM PODS paper — a complete claim-to-proof map, self-contained proofs in the at-submission appendix (no external appendices), correctly stated assumptions, honest scope and open cases, the full-version-on-arXiv norm, and consistency between what the paper claims and what the proofs actually establish.

1k repo stars
▌
Pods Topic Selection · brycewang-stanford
Use when deciding whether a data-management project belongs at ACM PODS (the database-theory symposium) or should be routed to SIGMOD/VLDB/ICDE (systems), ICDT (its sister theory venue), LICS/ICALP/STOC (pure theory), or a journal (TODS/LMCS/JACM), by contribution shape, the result-swap test, and the PODS-vs-ICDT community fit.

1k repo stars