Individual skill
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.
MobiCom-Skills/skills/mobicom-reproducibility/SKILL.md
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.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- data Derived category
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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: