Individual skill

ipsn-author-response

Use when drafting an IPSN-lineage rebuttal, covering the double-blind response to sensor-systems reviewers on ground truth, baseline fairness, deployment realism, energy accounting, and simulation-vs-real-hardware doubts, without leaking identity and without promising experiments not yet run.

IPSN-Skills/skills/ipsn-author-response/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,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.

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 Author Response

Use this after IPSN-lineage reviews are released. IPSN is conference-style: a short, decision-focused
**rebuttal** (verify the window and format on the current successor call), not a journal-style
revise-and-resubmit letter. The rebuttal must stay **double-blind** — no author names, institutions,
lab-named testbeds, or identity-revealing dataset/firmware links — and it must answer on the axes a
sensor-systems reviewer actually raised.

## Triage

- Answer what affects the decision: **evidence realism** (simulation vs real hardware), **soundness**
  of the method/platform, **baseline fairness**, **ground-truth validity**, **deployment honesty**,
  and **energy/latency accounting**.
- Use evidence that already exists or a number you can compute from data you already have — never a
Back to top