mobicom-reproducibility
Use when making a MobiCom result reproducible on a different testbed — recording radio, hardware, channel, and mobility provenance as the runs happen, characterizing the variance that over-the-air measurement introduces, and deciding early which traces, firmware, and deployment data can legally and safely ship for artifact evaluation.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.
# MobiCom Reproducibility Reproducibility at MobiCom is harder than at a compute-only venue because the experiment includes a **physical radio channel that no one else has**. The goal is not bit-identical reruns; it is enough provenance that a reader with a *different* testbed can tell whether a mismatch is their setup or your claim. Provenance is captured while the runs happen — it cannot be reconstructed after the testbed is torn down. ## The provenance ledger Keep a machine-readable record per experiment, written as the run executes: ```text Per-run provenance record: radio: SDR/NIC model, firmware/driver version, carrier freq, bandwidth, TX power rf_frontend: antenna type, gain, cabling, amplifiers topology: node count, positions/distances, LOS/NLOS, host specs channel: RSSI/CSI traces, measured interference, coherence-time estimate mobility: walker paths, speeds, schedule (or "stationary") energy: instrument, sampling rate, measured boundary software: code commit hash, config diffs from defaults, analysis-script hash outputs: raw-capture location, per-figure derivation script ``` This ledger is simultaneously the evaluation record (`mobicom-experiments`), the artifact-evaluati
- The provenance ledger
- Characterize the variance, do not hide it
- What can legally and safely ship
- A hardware-optional reproduction path
- Audit checklist
- Output format
What does the mobicom-reproducibility skill do?
Use when making a MobiCom result reproducible on a different testbed — recording radio, hardware, channel, and mobility provenance as the runs happen, characterizing the variance that over-the-air measurement introduces, and deciding early which traces, firmware, and deployment data can legally and safely ship for artifact evaluation.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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 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.