ipsn-writing-style
Use when revising an IPSN-lineage paper for a real sensing problem on the first page, a load-bearing information-processing or platform contribution, ground-truth methodology, energy/latency/accuracy budgets, honest deployment reporting, double-blind wording, and disciplined use of the ≤12-page ACM two-column budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-writing-style --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 Writing Style Use this when revising the main paper. IPSN papers are read by sensor-systems and information-processing reviewers, so they need a **real sensing problem on the first page** and evidence measured on **real hardware against ground truth**. The failure this skill prevents is a technically fine paper that reads like an offline ML result, or a hardware report with no measured trade-off. ## Revision rules - **Lead with the sensing problem and its physical budget:** the phenomenon being sensed, why current sensing/processing is inadequate, the contribution (an estimator/inference method and/or a platform), the real-hardware evidence, and the energy/latency/accuracy budget that makes it deployable. - **Make the information processing load-bearing (IP track).** State the estimator, inference, or learning method precisely enough to re-implement, and tie it to a quantity that matters (error bound, joules, bits, latency) — not just "accuracy improved." - **Make the platform reusable and measured (SPOTS track).** Give the MCU/SoC, sensor, radio, and toolchain, and justify design choices with measured power, timing, and robustness — a datasheet is not a contribution. - **Pa
- Revision rules
- Sensor-systems paper skeleton
- Sentence-level rewrites
- Energy/latency/ground-truth discipline
- Vignette: compressing a deployment paper
- Output format
What does the ipsn-writing-style skill do?
Use when revising an IPSN-lineage paper for a real sensing problem on the first page, a load-bearing information-processing or platform contribution, ground-truth methodology, energy/latency/accuracy budgets, honest deployment reporting, double-blind wording, and disciplined use of the ≤12-page ACM two-column budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ipsn-writing-style --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.