webconf-topic-selection
Use when deciding whether a project belongs at the Web Conference (WWW) at all, which of the ten research tracks should review it, whether the short-paper or Web4Good lane fits better, and when the work should instead route to WSDM, SIGIR, CIKM, KDD, ICWSM, WebSci, or an ML flagship.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-topic-selection --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.
# Web Conference Topic Selection Two decisions, in order: **is the work web-native**, and **which track's reviewer pool should judge it**. Both are made by the authors, both are effectively irreversible at the deadline, and the second is as consequential as the first because the venue reviews inside tracks. ## Decision 1: the web-nativeness test Ask: *if the Web's specific structure disappeared, would this contribution still make sense?* Web-native work depends on at least one of: open hypertext and link structure; platform mechanics and incentives; live, adversarial, user-generated content; web-scale heterogeneity; or the socio-technical coupling of users and algorithms. A generic model that merely *evaluates* on a web dataset fails the test — the dataset is swappable, so an ML venue's pool serves it better. ```text Web-native? -> route Contribution needs link/platform/user -> Web Conference candidate; go to structure to exist Decision 2 Contribution is a general method; web -> NeurIPS/ICML/ICLR or KDD, cite data is one evaluation among many web results as evidence Contribution is about people/society, -> ICWSM or WebSci if measurement/ computation is instrumental interdisciplinar
- Decision 1: the web-nativeness test
- Decision 2: track fit (2026 lineup)
- Lane selection inside the venue
- The two chronic misroutes
- Boundary cases of the current era
- Commitment checklist
- Output format
What does the webconf-topic-selection skill do?
Use when deciding whether a project belongs at the Web Conference (WWW) at all, which of the ten research tracks should review it, whether the short-paper or Web4Good lane fits better, and when the work should instead route to WSDM, SIGIR, CIKM, KDD, ICWSM, WebSci, or an ML flagship.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-topic-selection --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.