percom-supplementary
Use when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a human-subjects sensing paper between body and dataset.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-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.
# PerCom Supplementary Use this when assembling PerCom supplementary material. The governing rule is simple and strict: **the paper must be judgeable from the reviewed pages alone.** The dataset and any appendix support the paper; they do not hold the argument. Reviewers read supplementary material at their discretion, so anything the decision depends on lives in the 9 pages — and PerCom's budget is **tight**, which makes the split unforgiving. ## What goes where | Content | Body (within 9-page budget) | Dataset / appendix | |---|---|---| | The pervasive-computing claim and headline result | Yes | — | | Core technique or study design | Yes | Full hyperparameter grids, extra config | | The **cross-subject (LOSO)** headline evaluation | Yes | Full per-subject / per-session tables | | Metrics behind a claim (F1, event-level) | The result + metric named | The computation notebook | | Subject and sensor description | Summary + selection criterion | The complete datasheet | | Raw signals, logs, labels, scripts | — | Yes | | Reproduction instructions | A pointer | The README and run scripts | If a reviewer would need to open the dataset to know whether to accept, the paper is mis-partitio
- What goes where
- The 9-page-budget discipline
- Double-blind supplementary rules
- Appendix architecture (when the template allows in-paper appendices)
- Vignette: splitting a mixed-modality sensing paper
- Output format
What does the percom-supplementary skill do?
Use when deciding what belongs in an IEEE PerCom paper body versus its dataset/artifact and any appendix, covering the tight IEEEtran 9+1 page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a human-subjects sensing paper between body and dataset.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-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.