Individual skill

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.

MLSys-Skills/skills/mlsys-supplementary/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top