ipsn-submission
Use when auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the double-blind sweep for hardware/deployment papers, dataset/artifact links, and desk-reject triage — routed to the current successor (SenSys) call because IPSN no longer runs standalone.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-submission --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 Submission Run this audit before uploading. IPSN research papers were **double-blind**, on the **ACM Primary Article Template**, **≤12 pages** inclusive of everything, submitted through **HotCRP** — and split into the **IP** and **SPOTS** tracks. IPSN merged into **SenSys (Embedded AI and Sensing Systems)** from 2025-2026, so reopen the current SenSys call first: the numbers below are the IPSN 2024 (23rd, Hong Kong) snapshot read on 2026-07-09 (see `resources/official-source-map.md`) and the successor may differ (SenSys 2026 posted full 12 / short 6 pages). ## Pick the track before the PDF - **IP track** (Information Processing): algorithms, estimation, signal processing, inference, learning, localization. Reviewed by method reviewers who check soundness, baselines, and whether the information-processing claim holds. - **SPOTS track** (Sensor Platforms, Tools and Design Methods): hardware, embedded software, tools, measurement, deployments. Reviewed for reusability, measured design trade-offs, and real-system evidence. A mis-tracked paper draws the wrong reviewers and loses on the wrong axis. Confirm whether the successor keeps this split or uses a single track with categori
- Pick the track before the PDF
- Format and page budget
- Double-blind sweep (hardware papers leak in unusual places)
- Dataset and artifact at submission
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any anonymized artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|doi\.org|acknowledg|grant|university|@[a-z0-9.]+\.edu' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/|firmware.*owner' | head
What does the ipsn-submission skill do?
Use when auditing an IPSN-lineage submission for HotCRP readiness, covering the IP-vs-SPOTS track choice, the ACM Primary Article Template and ≤12-page inclusive budget, the double-blind sweep for hardware/deployment papers, dataset/artifact links, and desk-reject triage — routed to the current successor (SenSys) call because IPSN no longer runs standalone.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-submission --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.