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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-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.
# 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. - Use the 12-page body for the system's spine; move long protocols, extra device sweeps, and extended ablations to the appendix without making the main paper unintelligible. - Avoid overclaiming wins when the distribution is unreported or the gain is inside run-to-run spread. - Maintain double-blind style in self-citations, prior-system references, acknowledgements, funding, screenshots, and artifact descriptions. ## System-presentation discipline - State the **operating point**: the device, the workload, and the budge
- Revision rules
- System-presentation discipline
- Sentence-level rewrites
- Vignette: compressing into twelve double-column pages
- Output format
What does the mobisys-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-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.