socc-supplementary
Use when deciding what belongs in an ACM SoCC paper body versus its released artifact and appendices, covering the acmart 12-page (full) or 6-page (short) budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, dual-anonymous supplementary material, and how to split a cloud-systems measurement paper between body and package.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.
# SoCC Supplementary Use this when assembling SoCC supplementary material. The governing rule is simple and strict: **the paper must be judgeable from the reviewed pages alone.** The released artifact and any appendix support the paper; they do not hold the argument. Reviewers read the artifact at their discretion, so anything the decision depends on — the headline throughput, tail, and cost results — lives in the body. ## What goes where | Content | Body (within page budget) | Artifact / appendix | |---|---|---| | The cloud problem and the contribution | Yes | — | | Core mechanism or measurement design | Yes | Full config grids, extra parameters | | Headline throughput / **tail** / **cost** results | Yes | Full result tables, secondary regimes | | The key baseline comparison | The result + baseline named and tuned | The full sweep and raw logs | | Testbed / trace description | Summary + key parameters | The complete node list, full trace spec | | Raw logs, workload generators, replay scripts | — | Yes | | Reproduction instructions | A pointer | The README and run scripts | If a reviewer would need to open the artifact to know whether to accept — for instance to find the p99 or the
- What goes where
- The page-budget discipline
- Dual-anonymous supplementary rules
- Appendix architecture (when the template allows in-paper appendices)
- Vignette: splitting a cloud-systems measurement paper
- Output format
What does the socc-supplementary skill do?
Use when deciding what belongs in an ACM SoCC paper body versus its released artifact and appendices, covering the acmart 12-page (full) or 6-page (short) budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, dual-anonymous supplementary material, and how to split a cloud-systems measurement paper between body and package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.