pods-related-work
Use when positioning an ACM PODS submission against the database-theory literature across PODS, ICDT, LICS, and the journals (TODS, LMCS, JACM, VLDBJ), writing delta-first contrast that compares results rather than cataloging citations, keeping self-citations double-anonymous, and handling concurrent, arXiv-preprint, and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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.
# PODS Related Work Use this to audit novelty and eligibility. PODS reviewers are close to the database-theory literature and expect to see exactly where your **result** sits relative to the nearest prior **result** — a comparison of theorems, not a list of papers. Reopen the current PODS call for the resubmission, anonymity, and prior-publication rules before advising authors. ## Positioning checks - **Separate the mathematical novelty from the effort.** What is new: a bound that was open, a dichotomy that completes a partial classification, a semantics nobody had defined, a lower bound matching a known upper bound? Name the theorem-level delta. - **Cover the theory lanes.** PODS reviewers expect the database-theory venues *and* the relevant logic/complexity literature, not only the papers nearest your technique (see the table). A bibliography missing the obvious prior classification reads as unaware. - **Write delta-first at the level of results.** Each closely related paper gets one sentence naming what it *proved* and one naming how your result differs — a stronger bound, a broader class, a matching lower bound, a removed assumption. Compare theorems, do not summarize abstracts
- Positioning checks
- Database-theory literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the pods-related-work skill do?
Use when positioning an ACM PODS submission against the database-theory literature across PODS, ICDT, LICS, and the journals (TODS, LMCS, JACM, VLDBJ), writing delta-first contrast that compares results rather than cataloging citations, keeping self-citations double-anonymous, and handling concurrent, arXiv-preprint, and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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.