Individual skill

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.

IPSN-Skills/skills/ipsn-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
Yes
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,393
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

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