ipsn-supplementary
Use when deciding what belongs in an IPSN-lineage paper body versus its artifact, appendix, and demo/poster track, covering the ≤12-page ACM two-column budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, dataset release, and how to split a sensor-systems paper between body and package.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-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.
# IPSN Supplementary Use this when assembling IPSN supplementary material. The governing rule is simple and strict: **the paper must be judgeable from the reviewed pages alone.** The artifact, appendix, and any dataset support the paper; they do not hold the argument. Reviewers open the artifact at their discretion, so anything the decision depends on lives in the ≤12-page body. ## What goes where | Content | Body (within page budget) | Artifact / appendix | |---|---|---| | The sensing claim and its answer | Yes | — | | Core method (IP) or platform design (SPOTS) | Yes | Full parameter grids, extra config, board files | | Headline energy/latency/accuracy numbers + how measured | Yes | Full measurement logs, per-run traces | | Deployment yield / sync / loss headline | Yes | Full per-node, per-day breakdowns | | Ground-truth methodology | Named + summarized | The reference data and calibration logs | | Raw traces, firmware, scripts | — | Yes | | Secondary plots, extra sites, sensitivity sweeps | A pointer | Yes | If a reviewer would need to open the artifact or a demo to know whether to accept, the paper is mis-partitioned — move that evidence into the body. ## The ≤12-page disciplin
- What goes where
- The ≤12-page discipline
- Double-blind supplementary rules
- Demo/poster and dataset paths
- Appendix architecture (when the template allows in-paper appendices)
- Vignette: splitting a deployment paper
- Output format
What does the ipsn-supplementary skill do?
Use when deciding what belongs in an IPSN-lineage paper body versus its artifact, appendix, and demo/poster track, covering the ≤12-page ACM two-column budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, dataset release, and how to split a sensor-systems paper between body and package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-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 909 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.