Individual skill
sensys-related-work
Use when positioning a SenSys paper against the sensing, embedded, IoT, and on-device-AI literature — sweeping the right venue lanes after the SenSys/IPSN/IoTDI merger, proving each citation's venue via dblp/ACM DL against the MobiCom/NSDI/IPSN traps, distinguishing your mechanism from the nearest prior system, and self-citing blind-safely.
SenSys-Skills/skills/sensys-related-work/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- 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.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# SenSys Related Work
A SenSys related-work section has one job: show that you know the **closest prior systems** and
can name, precisely, what your mechanism does that theirs does not. Vague "prior work is limited"
draws blood at a systems venue where reviewers built that prior work. The 2026 merger widened the
lanes you must sweep — IPSN and IoTDI literature is now sibling canon, not a separate world.
## Sweep the right lanes
After the merger, a thorough sweep covers more ground than a pre-2026 SenSys paper did:
| Lane | Where it lives | What to look for |
|---|---|---|
| Low-power networked sensing | SenSys, **IPSN** (pre-2026) | The primitive/service your mechanism competes with |