SenSys Skills

A 12-skill depth pack for ACM/IEEE SenSys submissions: sensing/embedded-AI topic fit, the two-deadline HotCRP review model, double-blind submission audit, author response and revision, camera-ready and ACM artifact badges, real-testbed reproducibility, energy and low-power evaluation, supplementary material, related work, writing style, and cycle workflow. Grounded in the SenSys 2026/2027 Calls fo

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/sensys-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 12 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-sensys-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 12
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Sensys Workflow · brycewang-stanford
Use when planning a SenSys campaign against the two-deadline calendar — deciding which deadline to target and which edition it feeds, backward-scheduling so energy campaigns and long-term deployments finish before freeze, budgeting time for the resubmission-with-revision path, and sequencing fit, building, writing, and submission.

1k repo stars
▌
Sensys Submission · brycewang-stanford
Use when running the final pre-upload audit of a SenSys submission — confirming the right per-edition HotCRP site and which of the two deadlines is open, the AoE cutoff in local time, the 12/6-page double-column cap, the double-blind sweep including hardware and deployment leaks, and the resubmission-with-revision contract at the second deadline.

1k repo stars
▌
Sensys Experiments · brycewang-stanford
Use when designing or auditing a SenSys evaluation — energy and low-power measurement with a named instrument, real-testbed and deployment realism, honest sensor ground truth, on-device latency and memory, and same-hardware baselines, so the evidence meets SenSys's built-and-measured bar rather than a simulation or offline-benchmark one.

1k repo stars
▌
Sensys Camera Ready · brycewang-stanford
Use when preparing an accepted SenSys camera-ready — de-anonymizing the double-column ACM final, completing ACM rights and metadata, restoring acknowledgments, landing the awarded ACM artifact badges onto the paper, releasing traces and firmware within their constraints, and planning the in-person talk and demo for the merged audience.

1k repo stars
▌
Sensys Related Work · brycewang-stanford
Use when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving each citation's venue via dblp/ACM DL against the MobiCom/NSDI/IPSN traps, distinguishing your mechanism from the nearest prior system, and self-citing blind-safely.

1k repo stars
▌
Sensys Supplementary · brycewang-stanford
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.

1k repo stars
▌
Sensys Writing Style · brycewang-stanford
Use when drafting or revising a SenSys paper's abstract, introduction, and system sections — building the sensing-pain to mechanism to measured-behavior arc inside the double-column limit, putting the buildable system on the first page, reporting energy and latency as numbers not adjectives, and pairing every claim with a measurement.

1k repo stars
▌
Sensys Review Process · brycewang-stanford
Use when interpreting SenSys's two-deadline, self-contained review model — what a first-deadline outcome means, that a reject may return at the second deadline only with a substantive revision and Response to Reviewers, how systems reviewers weigh energy and deployment evidence, and how to classify a notification before drafting a response.

1k repo stars
▌
Sensys Author Response · brycewang-stanford
Use when writing a SenSys Response to Reviewers for a resubmission — treating the reviews as a required-changes contract, mapping each blocking concern to a specific change and the new measurement that closes it, staging the energy and testbed experiments a systems revision demands, and keeping the response anonymous and in the CFP's form.

1k repo stars
▌
Sensys Reproducibility · brycewang-stanford
Use when making a SenSys result reproducible across a different testbed — capturing energy-measurement method, hardware and firmware provenance, sensor ground-truth protocol, and deployment conditions while the testbed is still live, and deciding early which traces and firmware can legally and safely ship.

1k repo stars
▌
Sensys Topic Selection · brycewang-stanford
Use when deciding whether a project belongs at SenSys after the 2026 merger absorbed IPSN and IoTDI — testing whether the contribution is a built, measured sensing/embedded/IoT/on-device-AI system rather than a pure algorithm, a mobile-networking mechanism, or an offline ML result, and routing misfits to MobiCom, MobiSys, or an ML/DSP venue.

1k repo stars
▌
Sensys Artifact Evaluation · brycewang-stanford
Use when packaging a SenSys artifact for the Artifact Evaluation Committee — choosing which of the three ACM badges (Available, Functional, Reproduced) to pursue, building a hardware-optional evaluation path for reviewers without your testbed, documenting energy and hardware provenance, and passing the smoke run that proves functionality.

1k repo stars