mlsys-workflow
Use when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response, notification, camera-ready, the March artifact-evaluation submission, and the May conference, with backward planning built around scarce GPU time and team ownership.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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.
# MLSys Workflow Use this as the project-management skill for a Conference on Machine Learning and Systems submission. MLSys runs one cycle per year, so a missed gate costs twelve months or a reroute to another venue. All dates below are the verified 2026-cycle timetable (access 2026-07-08) — treat them as *shape*, and replace every one with the current mlsys.org dates page before committing a plan. MLSys is a conference with rotating per-edition leadership (2026: General Chair Luis Ceze; Program Chairs Zhihao Jia and Aakanksha Chowdhery) and no APC — proceedings publish open on proceedings.mlsys.org, and the money side is registration, where accepted-paper authors get a two-week reserved-ticket window. ## The 2026-cycle shape | Gate | 2026 anchor | What it demands | |---|---|---| | CFP and track choice | Summer 2025 (CFP publicized ~August) | Research vs industrial routing decided | | Paper + appendix deadline | October 30, 2025 | Frozen evaluation, blinded PDF, separate appendix upload | | Reviews released | January 12, 2026 | All authors on deck immediately | | Author response due | January 16, 2026 | Four days — pre-planned, not improvised | | Notification | January 25-26, 2026
- The 2026-cycle shape
- Backward plan from the paper deadline
- Standing team rituals
- Failure modes by stage
- The reroute decision, prepared in advance
- Ownership map (minimum viable)
- Cycle-volatility warning
- Output format
What does the mlsys-workflow skill do?
Use when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response, notification, camera-ready, the March artifact-evaluation submission, and the May conference, with backward planning built around scarce GPU time and team ownership.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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 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.