sensys-reproducibility
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-reproducibility --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 Reproducibility A SenSys result is reproducible when someone on **different hardware** can understand — and, from your traces, re-obtain — your numbers. The threat is not messy code; it is **provenance that evaporates when the deployment ends**. Energy measured without its method, accuracy scored against forgotten ground truth, and firmware whose toolchain is unrecorded cannot be reproduced at any price once the testbed is torn down. Capture it while the nodes are still powered. ## Capture it live, not later | Provenance | Capture while live | Why it cannot be reconstructed | |---|---|---| | **Energy method** | Instrument model, sampling rate, integration boundaries, sleep floor | A stored current number loses its method; "42 µA" of what phases? | | **Hardware** | MCU/SoC part + clock, sensor config, radio + TX power, board revision, battery/harvester spec | A later "same board" is rarely bit-identical | | **Firmware** | Sources + toolchain version + compiler flags, pinned | A rebuild on a new toolchain shifts timing and energy | | **Ground truth** | Reference protocol + the reference's own error | Labels without their protocol are unfalsifiable | | **Deployment** | Placem
- Capture it live, not later
- The reproducibility that matters is cross-hardware
- Decide early what can ship
- Reproducibility checklist
- Output format
What does the sensys-reproducibility skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sensys-reproducibility --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.