Individual skill
mobisys-experiments
Use when designing or auditing the evaluation of a MobiSys submission — building real-device testbeds, instrumenting energy and thermal behavior, measuring latency and frame-rate tails, bounding memory footprint, choosing tuned system baselines, and running deployments or user studies, so systems reviewers see where the system wins and breaks on the device.
MobiSys-Skills/skills/mobisys-experiments/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
- Yes
- 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,401
- 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
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,027 bytes
Read excerpt
# MobiSys Experiments
A MobiSys result becomes believable only when it is **measured on real hardware, driven to
steady state, and reported in latency, energy, memory, and thermal terms**. Simulation-only or
single-run numbers read as under-done. The evaluation axis here is the *device and platform* —
compute, energy, latency, memory, heat — not the radio or channel a wireless venue grades, and
not the traffic-and-topology an infrastructure venue grades. Build the evaluation as one
device-behavior claim per experiment.
## Turn each claim into one device experiment
The clean structure gives each subsection a claim about the running system, then the one
experiment that settles it. The opposite habit — run a benchmark suite and describe whatever
survives — is the unfocused evaluation MobiSys reviewers push back on. The claim-to-experiment