mlsys-supplementary
Use when deciding what goes into an MLSys appendix versus the 10-page body, exploiting the venue's unlimited separately-uploaded appendix that reviewers are not required to read, organizing configs, traces, extended results, and anonymized code pointers, and keeping supplementary material blinded for the research track.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-supplementary --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 Supplementary Use this when splitting a Conference on Machine Learning and Systems submission between body and appendix. The 2026-cycle mechanics (verified 2026-07-08): appendices are **unlimited in length**, uploaded as a **separate file** from the main paper, due at the same time — and reviewers are **explicitly not required to read them**. That last clause is the design constraint everything below follows from. ## The governing rule The 10-page body must win the paper's acceptance alone. The appendix exists to survive audits — a skeptical reviewer checking one specific configuration — and to serve future readers and artifact evaluators. Anything that must be *believed* for acceptance goes in the body; anything that must be *checkable* can go behind it. ## Placement decision table | Material | Body or appendix? | Reasoning | |---|---|---| | Headline comparison + strongest ablation | Body, always | Reviewers judge only what they must read | | Full hyperparameter/configuration matrices | Appendix, cross-referenced | Audit material, not narrative | | Baseline tuning protocol and budgets | Body (one paragraph) + appendix (full grid) | Fairness is decision-critical; the grid i
- The governing rule
- Placement decision table
- Structuring the appendix file
- Anonymity in supplementary material (research track)
- Worked split: an inference-compiler submission
- Common failure modes
- Interaction with later stages
- Cycle-volatility warning
- Output format
What does the mlsys-supplementary skill do?
Use when deciding what goes into an MLSys appendix versus the 10-page body, exploiting the venue's unlimited separately-uploaded appendix that reviewers are not required to read, organizing configs, traces, extended results, and anonymized code pointers, and keeping supplementary material blinded for the research track.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-supplementary --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.