ipsn-artifact-evaluation
Use when packaging an IPSN-lineage artifact for the ACM badges and the IPSN Best Research Artifact Award, covering hardware-plus-software artifacts (firmware, board files, datasets), what sensor-systems evaluators check first, DOI-issuing archives, evaluator-proof documentation for a physical system, and the separate post-acceptance timing.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-artifact-evaluation --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 Artifact Evaluation Use this for the artifact track. IPSN had a strong artifact culture — a **Best Research Artifact Award** alongside the Best Paper Award — and its artifacts are unusual because they mix **hardware, firmware, and data**, not just code. Two things to internalize: badges and the award are earned by evaluators actually using your package, and the review artifact (anonymized, for the paper's reviewers) is not the same deliverable as the public artifact (de-anonymized, DOI-archived). Because IPSN merged into SenSys, confirm the current badge set, the award's persistence, and the deadline on the successor call (待核实). ## Badges and the award (verify the current set) | Target | What it certifies | What earns it | |---|---|---| | Artifacts Available (ACM) | The artifact is permanently, publicly retrievable | Deposit in a DOI-issuing archive (Zenodo, IEEE DataPort, figshare, Software Heritage) | | Artifacts Evaluated - Functional | The artifact runs and does what the paper says | A clean-machine (or emulated) install, a demo, documented expected outputs | | Artifacts Evaluated - Reusable | Others can build on it | The Functional bar plus careful docs, structure, lice
- Badges and the award (verify the current set)
- What sensor-systems evaluators open first
- Packaging plan
- Anonymized review artifact vs. public artifact
- Worked vignette: packaging an on-device sensing artifact
- Calibration
- Output format
What does the ipsn-artifact-evaluation skill do?
Use when packaging an IPSN-lineage artifact for the ACM badges and the IPSN Best Research Artifact Award, covering hardware-plus-software artifacts (firmware, board files, datasets), what sensor-systems evaluators check first, DOI-issuing archives, evaluator-proof documentation for a physical system, and the separate post-acceptance timing.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-artifact-evaluation --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.