ipsn-related-work
Use when positioning an IPSN-lineage submission against the sensor-networks and information-processing literature (IPSN, SenSys, MobiCom, MobiSys, INFOCOM, and signal-processing venues), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind, and handling concurrent, preprint, and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-related-work --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 Related Work Use this to audit novelty and eligibility. IPSN reviewers span two literatures — the sensor-systems world (IPSN/SenSys/MobiCom/MobiSys/INFOCOM) and the information-processing/signal-processing world — and they expect to see where your paper sits relative to the nearest prior work, stated as a **delta**, not a list. Because IPSN merged into SenSys, reopen the current successor call for dual-submission, anonymity, and prior-publication rules before advising. ## Positioning checks - **Separate the sensing/information-processing novelty from the engineering effort.** What is new: a new estimator, a new platform, a new measurement, a new deployment regime, or an on-device method nobody had made fit? - **Cover both lanes.** An IP-track paper still owes the systems lane (has a sensor system done this end-to-end?) and the theory lane (is there an estimation/SP result you must cite?). A SPOTS paper owes the platform and tools lineage. A bibliography missing the obvious sibling work reads as unaware. - **Write delta-first.** Each closely related paper gets one sentence naming what it did and one naming what you do differently — not a summary. Position, don't catalog. - **
- Positioning checks
- Sensing/IP literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the ipsn-related-work skill do?
Use when positioning an IPSN-lineage submission against the sensor-networks and information-processing literature (IPSN, SenSys, MobiCom, MobiSys, INFOCOM, and signal-processing venues), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind, and handling concurrent, preprint, and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-related-work --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.