wsdm-workflow
Use when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference, backward milestone planning, the September short-paper fallback, alternate entrances (demos, WSDM Cup, doctoral consortium), and coordination with sibling-venue deadlines.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-workflow --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.
# WSDM Workflow Plan a WSDM campaign around the venue's defining rhythm: one deadline a year, in August, for a conference the following February - with no rebuttal stage between them. Missing August costs twelve months, and nothing after August can improve the outcome. Every date below is a 2026-cycle anchor (abstract 2025-08-07, paper 2025-08-14, notification 2025-10-23, conference 2026-02-22 to 26, Boise); the 2027 edition (20th, Hong Kong, February 15-19, 2027) had not published verified deadlines at this pack's check date - confirm them at wsdm-conference.org/2027 before committing the plan. ## The annual clock ```text T-26w fit decision (wsdm-topic-selection) + evidence plan T-20w datasets locked, split manifests written, baselines running T-12w main results stable; ablation matrix complete T-8w full draft; adversarial read #1 -> objection inventory T-4w artifact repo review-ready; ethics section drafted T-1w abstract registered (bidding-quality title+abstract) Aug T=0 paper deadline, AoE <- everything ends here Oct ~T+10w notification <- no interaction in between Nov+ camera-ready + ACM production (dates from acceptance email) Feb single-track conference (talk/poster, registr
- The annual clock
- The September pressure valve
- Alternate entrances to the same room
- Coordinating with the sibling calendar
- Contingencies
- Team operating rules
- Output format
What does the wsdm-workflow skill do?
Use when planning the calendar for a WSDM submission - the single annual cycle from August abstract and paper deadlines through October notification to the February conference, backward milestone planning, the September short-paper fallback, alternate entrances (demos, WSDM Cup, doctoral consortium), and coordination with sibling-venue deadlines.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wsdm-workflow --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.