sensys-supplementary
Use when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument, moving full protocols, extra plots, and derivations to the appendix, blinding anonymous artifact links, and keeping the Response to Reviewers out of the body.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-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.
# SenSys Supplementary Material SenSys gives you an unusual amount of room *outside* the page cap: **references and appendices are unlimited**. That freedom is a trap if it becomes a dumping ground. The discipline is to keep the ≤ 12-page (full) or ≤ 6-page (short) body carrying the **argument**, and to place everything a reviewer might *want* but does not *need to judge the claim* in the appendix — reachable, but not in the way of the story. ## The placement decision For each piece of content, ask: *must a reviewer read this to believe the headline claim?* | Content | Body (in the cap) | Appendix (unlimited) | HotCRP field | |---|---|---|---| | The mechanism and its constraint model | Yes | — | — | | The headline energy/latency/accuracy results | Yes | — | — | | Full measurement protocol (instrument settings, calibration steps) | Summary only | Full detail | — | | Extra ablations and secondary plots | The load-bearing ones | The rest | — | | Derivations / proofs of a bound | Statement + intuition | Full proof | — | | Complete hardware BOM and wiring | — | Yes | — | | Deployment logs, per-node uptime tables | Summary | Full tables | — | | Title, abstract, topics, conflicts | — | —
- The placement decision
- The body earns its space
- Blind the artifact links
- Keep the resubmission packet out of the body
- Structure the appendix so it is navigable
- Output format
What does the sensys-supplementary skill do?
Use when deciding what goes in a SenSys paper's body versus its unlimited references and appendices versus HotCRP fields — keeping the double-column body carrying the argument, moving full protocols, extra plots, and derivations to the appendix, blinding anonymous artifact links, and keeping the Response to Reviewers out of the body.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-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.