Individual skill
mobisys-writing-style
Use when revising a MobiSys paper for a mobile-systems first page, the pain → system-design → on-device-evidence arc, 12-page double-column compression, double-blind wording, and claims disciplined by measured latency, energy, memory, and thermal budgets rather than superlatives, so the draft survives systems-and-services reviewers.
MobiSys-Skills/skills/mobisys-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- 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.
- 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
- writing 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 · 3,701 bytes
Read excerpt
# MobiSys Writing Style
Use this when revising the main paper. A MobiSys paper needs a compact statement of the
on-device problem, the system that solves it, and the measurements that prove it — in the
12-page double-column body.
## Revision rules
- Put the mobile-system contribution on the first page: the on-device pain, why current
systems fail *on the device*, the mechanism, and the measured payoff.
- Name the device budget explicitly. MobiSys reviewers are sensitive to hidden compute,
energy, latency, memory, and thermal assumptions.
- Pair every major claim with a measurement on real hardware, a design argument, or a
reproducibility detail — never a superlative.