mlsys-submission
Use when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that still permit arXiv posting, research-versus-industrial track requirements, dual-submission exceptions, style-kit compliance, and desk-reject triage before the deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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.
# MLSys Submission Use this to run a pre-deadline audit of a Conference on Machine Learning and Systems submission. Facts below are anchored to the 2026 cycle (verified 2026-07-08); reopen the current Call for Research Papers and the Industrial Track call on mlsys.org before acting, because MLSys restructures its calls between cycles — the Industrial Track itself only appeared in 2026. ## Track decision comes first Everything downstream differs by track, so settle this before formatting anything. | Question | Research track | Industrial track (new in 2026) | |---|---|---| | Novelty required? | Yes — previously unpublished research | No — but design methodology and detailed benchmarks of a built, large-scale system are expected | | Anonymization | Full: authors, affiliations, self-references, acknowledgements | Author names hidden, but company names, product names, and URLs may remain | | Typical author | Academic or industrial researcher with a new mechanism | Team reporting a production ML system's design and measured behavior | | Cross-track submission | Forbidden to submit the same paper to both tracks | Same | If the paper's strongest asset is deployment scale and operational i
- Track decision comes first
- Format audit (2026-cycle anchors)
- Anonymity model — stricter and looser than you expect
- Dual-submission rules
- Desk-reject and triage table
- Final-week sequence for a systems paper
- OpenReview field audit
- Cycle-volatility warnings
- Output format
Pre-upload leak sweep on the built PDF and source tree pdfinfo paper.pdf | grep -iE 'author|producer' # metadata identity pdftotext paper.pdf - | grep -inE 'acknowledg|grant|@|github.com/[a-z0-9-]+' | head grep -rinE 'copyright|institute|univers' *.tex | grep -v style | head
What does the mlsys-submission skill do?
Use when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that still permit arXiv posting, research-versus-industrial track requirements, dual-submission exceptions, style-kit compliance, and desk-reject triage before the deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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.