mobisys-author-response
Use when drafting a MobiSys rebuttal after round-2 reviews — working within the scope limit (correct factual errors, answer specific reviewer questions), adding only directly-responsive new results, promising camera-ready work honestly, staying double-blind, and giving the area chair a clean rationale for a mobile-systems accept decision.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-author-response --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 Author Response Use this after MobiSys round-2 reviews are released. Reopen the current rebuttal instructions and length limit before drafting, because scope and mechanics are cycle-specific. The MobiSys rebuttal is **narrow by design**: it is not a revision and not a place to reargue the paper. ## Scope discipline - The rebuttal is for **correcting factual errors** in the reviews and **answering specific questions** reviewers posed. Stay inside that scope. - New experiments are admissible **only if they directly address reviewer feedback**; alternatively, you may **promise** results expected by the camera-ready deadline — but only ones you can actually deliver. - Keep the reply **double-blind**: no institution, authorship, private repository, or identity-revealing device/account detail. - Use existing submitted evidence first: figures, appendix tables, device provenance, and the artifact — point to them precisely rather than restating them. ## Triage - Answer concerns that affect the **decision**: is the system real, is the on-device evidence sufficient, is the energy/latency claim defensible, is the contribution a system. - Correct factual misreadings first (a reviewer
- Scope discipline
- Triage
- Drafting pattern
- Systems-reviewer pushback patterns
- Response micro-example
- Output format
What does the mobisys-author-response skill do?
Use when drafting a MobiSys rebuttal after round-2 reviews — working within the scope limit (correct factual errors, answer specific reviewer questions), adding only directly-responsive new results, promising camera-ready work honestly, staying double-blind, and giving the area chair a clean rationale for a mobile-systems accept decision.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-author-response --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 984 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.