ipsn-topic-selection
Use when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and whether it should go to the IPSN lineage (now the merged SenSys at CPS-IoT Week), a CPS-IoT Week neighbor (RTAS/ICCPS/HSCC), MobiSys/MobiCom, INFOCOM, or a signal-processing journal.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-topic-selection --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 Topic Selection Decide two things before drafting: **which track** and **which venue**. IPSN — the ACM/IEEE International Conference on Information Processing in Sensor Networks — split its research papers into the **Information Processing (IP) track** and the **Sensor Platforms, Tools and Design Methods (SPOTS) track**, and it lived inside **CPS-IoT Week**. As of 2026-07-09 IPSN no longer runs standalone — it merged into **SenSys (Embedded AI and Sensing Systems)** — but the IP-vs-SPOTS instinct still decides how your paper is read and where its evidence bar sits, so keep it. ## First decision: IP track or SPOTS track This is the choice with no sibling analogue. Get it wrong and your platform paper is judged by theory reviewers, or your estimator is judged by hardware reviewers. | Signal in your project | Track | Why | |---|---|---| | The core is an algorithm, estimator, inference, or learning method for sensed data | **IP** | Information processing is the contribution; energy/error/bits are the currency | | Localization, tracking, sensor fusion, compressive sensing, on-device/TinyML inference | **IP** | These are IP-track staples; the platform is a vehicle, not the point |
- First decision: IP track or SPOTS track
- Second decision: is this the IPSN lineage at all?
- The merger reality (do not skip)
- The model-swap and platform-swap tests
- Evidence maturity, without the ladder cliché
- Cheap reconnaissance before committing
- Decision procedure
What does the ipsn-topic-selection skill do?
Use when deciding whether a sensing/embedded project is an IPSN Information-Processing (IP) contribution or a Sensor Platforms, Tools and Design Methods (SPOTS) contribution, and whether it should go to the IPSN lineage (now the merged SenSys at CPS-IoT Week), a CPS-IoT Week neighbor (RTAS/ICCPS/HSCC), MobiSys/MobiCom, INFOCOM, or a signal-processing journal.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-topic-selection --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.