sigmod-related-work
Use when positioning a SIGMOD submission against the data-management literature, covering coverage across SIGMOD/PACMMOD, PVLDB, ICDE, TODS, and PODS lines, decades-deep systems history, concurrent papers in rolling venues, industrial-system citations, and PACMMOD's substantial-overlap exclusivity rule.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-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.
# SIGMOD Related Work Database research has unusually long memory and unusually fast turnover at the same time: reviewers expect a submission to know both the 1980s ancestor of its technique and the PVLDB paper from three months ago. Positioning at SIGMOD is therefore a two-clock problem, and the related-work section is where a PC of system builders first tests whether the authors know the field t
What does the sigmod-related-work skill do?
Use when positioning a SIGMOD submission against the data-management literature, covering coverage across SIGMOD/PACMMOD, PVLDB, ICDE, TODS, and PODS lines, decades-deep systems history, concurrent papers in rolling venues, industrial-system citations, and PACMMOD's substantial-overlap exclusivity rule.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-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.