recsys-related-work
Use when positioning an ACM RecSys submission against recommender-systems literature and its neighbors (SIGIR, KDD, WSDM, TheWebConf, UAI), including the reproducibility-critique line, arXiv and prior versions, concurrent work, ACM Digital Library archival status, and the citation coverage RecSys reviewers expect across recommendation subfields.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-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.
# RecSys Related Work Use this to audit novelty and eligibility. Reopen the current Call for Contributions for dual-submission, anonymity, and prior-publication rules before advising authors. ## Positioning checks - Separate the **recommendation** contribution from generic ML improvement: a new ranking objective, user/item modeling idea, evaluation protocol, off-policy estimator, or empirical insi
What does the recsys-related-work skill do?
Use when positioning an ACM RecSys submission against recommender-systems literature and its neighbors (SIGIR, KDD, WSDM, TheWebConf, UAI), including the reproducibility-critique line, arXiv and prior versions, concurrent work, ACM Digital Library archival status, and the citation coverage RecSys reviewers expect across recommendation subfields.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill recsys-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.