Menu

Individual skill

sensys-reproducibility

0upvotes

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.

SenSys-Skills/skills/sensys-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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 |
Back to top