Menu

Individual skill

sensys-topic-selection

0upvotes

Use when deciding whether a project belongs at SenSys after the 2026 merger absorbed IPSN and IoTDI — testing whether the contribution is a built, measured sensing/embedded/IoT/on-device-AI system rather than a pure algorithm, a mobile-networking mechanism, or an offline ML result, and routing misfits to MobiCom, MobiSys, or an ML/DSP venue.

SenSys-Skills/skills/sensys-topic-selection/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
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,411
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# SenSys Topic Selection

SenSys accepts a **system you built and measured under embedded constraints**. The 2026 merger
of SenSys, IPSN, and IoTDI widened the mandate — low-power networked sensing, embedded systems,
IoT, and on-device AI now share one venue — but it did not soften the systems bar: a strong
SenSys paper still has a **buildable mechanism** whose value is shown in **energy, latency,
memory, and deployment behavior on real hardware**, not in a proof or a leaderboard delta.

## The fit test

Ask these in order; a "no" is a routing signal, not a verdict on the work's quality.

1. **Is there a system?** Can you point to the artifact — firmware, a node, a protocol, a
   deployment — that embodies the contribution? A pure algorithm with no embedded realization
Back to top