Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP…
Install Mobisys Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/MobiSys-Skills/skills/mobisys-review-process .claude/skills/mobisys-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mobisys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-review-process into .claude/skills/mobisys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/MobiSys-Skills/skills/mobisys-review-process .agents/skills/mobisys-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mobisys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-review-process into .agents/skills/mobisys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/MobiSys-Skills/skills/mobisys-review-process .cursor/skills/mobisys-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mobisys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-review-process into .cursor/skills/mobisys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path MobiSys-Skills/skills/mobisys-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/MobiSys-Skills/skills/mobisys-review-process .gemini/skills/mobisys-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mobisys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-review-process into .gemini/skills/mobisys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/MobiSys-Skills/skills/mobisys-review-process .github/skills/mobisys-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mobisys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-review-process into .github/skills/mobisys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/MobiSys-Skills/skills/mobisys-review-process .opencode/skills/mobisys-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mobisys-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-review-process into .opencode/skills/mobisys-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mobisys-review-process- GitHub stars
- 1.2k
- Token cost
- ~958 tokens
- SKILL.md length
- 421 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP…
- Planning around MobiSys peer review — the two-round process with an early-reject cut after round 1
- SKILL.md covers Process model, Who reviews here, Scoring leverage table and Stage-by-stage realism, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The round-2 rebuttal window
What it does
Mobisys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP mechanics, the systems-and-services reviewer pool, and decision criteria for on-device claims, so response strategy fits how MobiSys decides.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Peer review. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning around MobiSys peer review — the two-round process with an early-reject cut after round 1
- The round-2 rebuttal window
- Double-blind HotCRP mechanics
- The systems-and-services reviewer pool
Example prompts
- “/mobisys-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mobisys Review Process loads about 958 tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 421 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 421 words, ~958 tokens.
Download SKILL.mdSave it as
.claude/skills/mobisys-review-process/SKILL.md (or your agent's skills folder).- name
- mobisys-review-process
- description
- Use when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP mechanics, the systems-and-services reviewer pool, and decision criteria for on-device claims, so response strategy fits how MobiSys decides.
MobiSys Review Process
Use this to reason about review-stage strategy. Reopen the current CFP, the HotCRP site, and the organizing-committee page before making process claims — the mechanics are cycle-specific.
Process model
- MobiSys uses HotCRP for submission and review, with a paper-registration step preceding the paper upload and double-blind review (author identities hidden since 2017).
- Review runs in two rounds. Papers that do not advance past round 1 receive an early rejection with reviews, so authors can re-plan before the process ends. Round-2 survivors reach reviews and a rebuttal window.
- The rebuttal is scope-limited: correct factual errors and answer specific reviewer
questions; new results are admissible only when directly responsive, or may be promised for
camera-ready (
mobisys-author-response). - Unlike MobiCom and NSDI, the rendered 2026 CFP describes accept/reject through the rebuttal, not a separate one-shot revision channel; treat any revision path as 待核实 per cycle.
- Accepted papers are published in the ACM Digital Library, so camera-ready compliance and artifact badges matter as much as the initial accept.
Who reviews here
- The pool is systems-and-services researchers: people who build and measure mobile runtimes, on-device ML, sensing services, and platforms, and who read an energy or latency claim as something to be re-derived, not admired.
- Because MobiSys is specialized, topical matches are close; a hand-wavy device claim or an undefined energy boundary gets caught rather than skimmed past.
- Borderline mobile-systems papers usually fall on one of three edges: an evaluation on a single device or single run, an energy/thermal claim without a described instrument, or a contribution that is really a better model dressed as a system.
Show full SKILL.md (158 more words)Show less
Scoring leverage table
| Review dimension | What raises it | What sinks it |
|---|---|---|
| Contribution | A system mechanism forced by the device constraint | A model or algorithm with an incidental phone demo |
| On-device evidence | Distributions on real hardware across devices/states | Single-device, single-run, simulation-only numbers |
| Energy/latency rigor | Named instrument, boundary, and sustained-load behavior | "Efficient" with no measured joules or throttle trace |
| Clarity | An explicit operating point (device, workload, budget) | Latency numbers with no device or workload context |
Stage-by-stage realism
- Round 1: triage by what a systems reviewer would weigh — is the device evidence real and is the contribution a system? A thin evaluation is the classic early reject.
- Rebuttal: windows are short and scope is narrow; a precise reply that fixes a factual error and answers the one decision-critical question beats an exhaustive one.
- Decision: one unresolved evidence objection (single-device, undefined energy boundary) outweighs several resolved clarity complaints.
- After accept: artifact evaluation and camera-ready are their own gates
(
mobisys-artifact-evaluation,mobisys-camera-ready).
Output format
[Current stage] submitted / round-1 / round-2 reviews / rebuttal / decision / camera-ready
[Decision actors] <reviewers / AC / chairs>
[Likely leverage] <contribution / on-device evidence / energy-latency rigor / clarity>
[Forbidden moves] <identity leak / out-of-scope new results in rebuttal>
[Next response move] <one action>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in MobiSys-Skills/skills/mobisys-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mobisys Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mobisys Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~958 | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Scholar Evaluationspacering-net/codeg | 3.9k | 11 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
Similar skills
Scholar Evaluation
spacering-net/codeg
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Academic Paper Reviewer
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Mobisys Review Process
What does Mobisys Review Process do?
A skill your agent uses when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP…. Mobisys Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when explaining or planning around MobiSys peer review — the two-round process with an early-reject cut after round 1, the round-2 rebuttal window, double-blind HotCRP mechanics, the systems-and-services reviewer pool, and decision criteria for on-device claims, so response strategy fits how MobiSys decides.
When should I use Mobisys Review Process?
Mobisys Review Process fits situations like: planning around MobiSys peer review — the two-round process with an early-reject cut after round 1; the round-2 rebuttal window; double-blind HotCRP mechanics; the systems-and-services reviewer pool.
How do I install Mobisys Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a claude-code`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobisys-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Mobisys Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a codex`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobisys-review-process in your project. Codex loads it when a task matches its description.
Can I use Mobisys Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobisys-review-process, .gemini/skills/mobisys-review-process, .github/skills/mobisys-review-process and .opencode/skills/mobisys-review-process in your project.
What does Mobisys Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Mobisys Review Process is instructions for the agent only.
Does Mobisys Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mobisys Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mobisys Review Process use?
Mobisys Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mobisys Review Process use?
About 958 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mobisys Review Process?
Skills that share tags, products or a category with Mobisys Review Process: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mobisys Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.