Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
A skill your agent uses when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round…
MITAuto-check passed
Install Mobicom Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-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/MobiCom-Skills/skills/mobicom-review-process .claude/skills/mobicom-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 "mobicom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-review-process into .claude/skills/mobicom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-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/MobiCom-Skills/skills/mobicom-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 mobicom-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-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/MobiCom-Skills/skills/mobicom-review-process .agents/skills/mobicom-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 "mobicom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-review-process into .agents/skills/mobicom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-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 mobicom-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-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/MobiCom-Skills/skills/mobicom-review-process .cursor/skills/mobicom-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 "mobicom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-review-process into .cursor/skills/mobicom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-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 MobiCom-Skills/skills/mobicom-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 mobicom-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobicom-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/MobiCom-Skills/skills/mobicom-review-process .gemini/skills/mobicom-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 "mobicom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-review-process into .gemini/skills/mobicom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-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 mobicom-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 mobicom-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/MobiCom-Skills/skills/mobicom-review-process .github/skills/mobicom-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 "mobicom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-review-process into .github/skills/mobicom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-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 mobicom-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 mobicom-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/MobiCom-Skills/skills/mobicom-review-process .opencode/skills/mobicom-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 "mobicom-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiCom-Skills/skills/mobicom-review-process into .opencode/skills/mobicom-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobicom-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
mobicom-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 481 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round…
- Reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one
- SKILL.md covers The stages and the outcome space, The early reject is data, not…, The rebuttal window is short… and The one-shot revision is a…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The released reviews and rebuttal window after round two
What it does
Mobicom Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round two, the accept / one-shot revision / reject outcome space, reviewer continuity across a revision, and how the rolling-deadline structure shapes what to do next.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one
- The released reviews and rebuttal window after round two
- The accept / one-shot revision / reject outcome space
- Reviewer continuity across a revision
Example prompts
- “/mobicom-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
Mobicom Review Process loads about 1.1k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 481 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). 481 words, ~1,077 tokens.
Download SKILL.mdSave it as
.claude/skills/mobicom-review-process/SKILL.md (or your agent's skills folder).- name
- mobicom-review-process
- description
- Use when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round two, the accept / one-shot revision / reject outcome space, reviewer continuity across a revision, and how the rolling-deadline structure shapes what to do next.
MobiCom Review Process
Understanding MobiCom's review structure changes what you do at each stage. Unlike a single-verdict venue, MobiCom runs two rounds per deadline with an early-reject cut and a rebuttal, and then keeps a one-shot revision channel on top. Knowing which state you are in — and what each state affords — is the difference between a wasted rolling deadline and a converging paper.
The stages and the outcome space
Submission
-> Round 1 review
-> EARLY REJECT (reviews returned) [use them for the next round]
-> advance to Round 2
-> Round 2 review -> reviews RELEASED -> REBUTTAL window -> PC decision
-> ACCEPT
-> ONE-SHOT REVISION (required-changes list)
-> REJECT| State | What it means | What you do |
|---|---|---|
| Early reject | did not clear round 1; full reviews returned | mine reviews, decide next round (mobicom-workflow) |
| Advanced | reached round 2; reviews will come with a rebuttal window | prepare to respond fast (mobicom-author-response) |
| Accept | in the program | artifacts + camera-ready (mobicom-camera-ready) |
| One-shot revision | conditional; a list of required changes | treat as a contract; plan the experiments |
| Reject | terminal for this submission | reframe or re-target; do not resubmit unchanged |
The early reject is data, not just a loss
A round-1 early reject returns reviews well before the round closes. Because MobiCom's rounds roll, those reviews are the highest-value input to your next submission — of the same work, improved, or of a re-scoped version. Do not treat it as a dead end; treat it as a free review cycle that most single-deadline venues do not offer.
The rebuttal window is short and fixed
After round-2 reviews are released, the rebuttal window opens on a clock you do not control.
Its purpose is narrow: correct factual misunderstandings and answer specific reviewer
questions, not to add a new contribution. Plan coauthor availability for it in advance,
because it lands weeks after submission when attention has moved on
(mobicom-author-response). The exact length/format of the rebuttal is 待核实 for the current
cycle — read the instructions live.
Show full SKILL.md (197 more words)Show less
The one-shot revision is a commitment
A one-shot (major) revision is not a soft accept. It is a contract against a specific
list of required changes, usually re-reviewed by the same reviewers where possible. Before
accepting the plan, cost the experiments it demands in testbed-weeks (mobicom-workflow); a
revision that dodges an item on the list, or that re-runs without the requested condition, is
the fastest way to convert a revision into a reject.
Reviewer continuity shapes strategy
Because the same reviewers tend to carry a paper across the rebuttal and a revision:
- A rebuttal that concedes a real weakness credibly is worth more than one that argues every point; the same reviewer reads the revision.
- Promises made in a rebuttal become the revision's checklist — do not promise what you cannot measure by the revision deadline.
- Consistency across rebuttal → revision → camera-ready matters; contradicting your own earlier response is a memorable red flag.
Confidentiality and conduct
Reviews and PC discussion are confidential; do not quote reviewers publicly or attempt to deanonymize them. Reviewer identity is protected the same way author identity is. If you believe a review breaches policy, the chairs are the channel, not social media.
Output format
[State] early-reject / advanced / accept / revision / reject
[Reviews] key issues extracted, sorted by severity
[If advanced] rebuttal plan: factual corrections vs question answers
[If revision] required-changes list -> experiment cost in testbed-weeks
[If early reject] which next round + what to fix first
[Continuity] promises that will become the revision checklist© 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 MobiCom-Skills/skills/mobicom-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mobicom 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 |
|---|---|---|---|---|---|---|
| Mobicom Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| Ejentum Reasoning Harnesssickn33/agentic-awesome-skills | 47k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Nowait Reasoning Optimizerdavila7/claude-code-templates | 33k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Recall Reasoningparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~758 | Automated safety check: Pass | MIT | |
| Nv Reason CxrNVIDIA/skills | 3.6k | — | ~3.9k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Ejentum Reasoning Harness
sickn33/agentic-awesome-skills
MCP server exposing four cognitive harness modes (reasoning, code, anti-deception, memory).
Nowait Reasoning Optimizer
davila7/claude-code-templates
Implements the NOWAIT technique for efficient reasoning in R1-style LLMs.
Recall Reasoning
parcadei/Continuous-Claude-v3
Search past reasoning for relevant decisions and approaches. An agent skill from parcadei/Continuous-Claude-v3.
- Official
Nv Reason Cxr
NVIDIA/skills
Used for command-shape or live NV-Reason-CXR chest X-ray reasoning smoke tests.
Diagnostic Reasoning
kunchenguid/firstmate
Agent-only procedure for diagnosing reported bugs. An agent skill from kunchenguid/firstmate.
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…
Questions about Mobicom Review Process
What does Mobicom Review Process do?
A skill your agent uses when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round…. Mobicom Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one, the released reviews and rebuttal window after round two, the accept / one-shot revision / reject outcome space, reviewer continuity across a revision, and how the rolling-deadline structure shapes what to do next.
When should I use Mobicom Review Process?
Mobicom Review Process fits situations like: reasoning about where a MobiCom paper sits in the two-round review process — the early-reject cut after round one; the released reviews and rebuttal window after round two; the accept / one-shot revision / reject outcome space; reviewer continuity across a revision.
How do I install Mobicom Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-review-process -a claude-code`. Or copy the skill folder (MobiCom-Skills/skills/mobicom-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobicom-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Mobicom Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-review-process -a codex`. Or copy the skill folder (MobiCom-Skills/skills/mobicom-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobicom-review-process in your project. Codex loads it when a task matches its description.
Can I use Mobicom 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 mobicom-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/mobicom-review-process, .gemini/skills/mobicom-review-process, .github/skills/mobicom-review-process and .opencode/skills/mobicom-review-process in your project.
What does Mobicom Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Mobicom Review Process is instructions for the agent only.
Does Mobicom 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 Mobicom 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 Mobicom Review Process use?
Mobicom 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 Mobicom Review Process use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Mobicom Review Process?
Skills that share tags, products or a category with Mobicom Review Process: Deepseek Reason (ruvnet/ruflo, 74k stars), Ejentum Reasoning Harness (sickn33/agentic-awesome-skills, 47k stars), Nowait Reasoning Optimizer (davila7/claude-code-templates, 33k stars) and Recall Reasoning (parcadei/Continuous-Claude-v3, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mobicom 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.