ipsn-reproducibility
Use when strengthening IPSN-lineage reproducibility for a hardware/embedded/deployment artifact, covering firmware and board files, pinned toolchains, raw traces and calibration, honest degrees of reproducibility for a physical system, anonymized-but-runnable artifacts, and consistency between the paper and the package.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-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.
# IPSN Reproducibility Use this before submission and again before camera-ready. IPSN's artifact and Best Research Artifact culture makes reproducibility a scored dimension — but a sensor-systems artifact is harder than a software one: it involves firmware, hardware, physical ground truth, and measurements that depend on the bench. The goal is that a competent reader could rebuild as much of your evidence as the physical setup allows, and knows exactly which parts need your hardware. ## Evidence map - Map each claim and reported number to a **verifiable location** — a paper section, a figure generated from logged traces, a firmware build, or a script in the artifact. - For an **IP-track** method, give the algorithm, parameters, and the analysis scripts that turn raw traces into the paper's figures. - For a **SPOTS-track** platform, ship firmware sources, build instructions, a bill of materials or board files, and the pinned toolchain (compiler, SDK, RTOS versions). - For a **deployment**, ship the raw sensor traces, the ground-truth reference, and the calibration data — not only the derived metrics. - Keep the paper and artifact **consistent**: a number in the PDF that no script or
- Evidence map
- What a sensor-systems artifact contains
- Provenance pinning
- Degrees of reproducibility (state the one you achieved)
- Anonymized but runnable (double-blind)
- Consistency and camera-ready pass
- Vignette: a deployment plus estimator
- Output format
What does the ipsn-reproducibility skill do?
Use when strengthening IPSN-lineage reproducibility for a hardware/embedded/deployment artifact, covering firmware and board files, pinned toolchains, raw traces and calibration, honest degrees of reproducibility for a physical system, anonymized-but-runnable artifacts, and consistency between the paper and the package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-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.