webconf-submission
Use when auditing a Web Conference (WWW) research-tracks submission before the abstract or full-paper deadline, covering track choice among the ten research tracks, the single-PDF 8+references+appendix page arithmetic within 12 pages, EasyChair profile completeness, the author-list freeze, the 7-submission cap, and double-blind checks.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-submission --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 Submission The Web Conference splits its abstract and full-paper deadlines by exactly one week (2026: September 30 and October 7, 2025, AoE, explicitly strict). Several of the checks below can only be fixed inside that week, and one — the author list — locks shut at the *abstract* deadline. Treat every number here as a 2026-edition anchor and reopen the current research-tracks CFP first. ## The three gates, in order of irreversibility 1. **Author-list freeze.** At the abstract deadline the author list and its ordering become final: no additions, removals, or reordering afterward, only spelling and affiliation corrections. Settle authorship disputes *before* registering the abstract, not during the review cycle. This is stricter than most ML venues and catches teams every year. 2. **Track declaration.** A submission goes to exactly one of the ten research tracks; the track determines which chairs and reviewer pool see the paper. A graph learning paper sent to "Web mining and content analysis" instead of "Graph algorithms and modeling for the Web" gets reviewers who ask different questions. If the track is contested inside the team, run `webconf-topic-selection` firs
- The three gates, in order of irreversibility
- Page arithmetic (2026 rule)
- Format and anonymity
- EasyChair profile gate
- Failure-severity ledger
- Deadline-week runbook
- Vignette: the abstract-week authorship dispute
- Cross-lane edge cases
- Output format
What does the webconf-submission skill do?
Use when auditing a Web Conference (WWW) research-tracks submission before the abstract or full-paper deadline, covering track choice among the ten research tracks, the single-PDF 8+references+appendix page arithmetic within 12 pages, EasyChair profile completeness, the author-list freeze, the 7-submission cap, and double-blind checks.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-submission --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 984 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.