mobicom-author-response
Use when writing a MobiCom rebuttal after round-two reviews or executing a one-shot revision — triaging reviewer points by severity, fitting a factual, concession-honest rebuttal into its length limit, and turning a required-changes list into a change-highlighted revision with a change summary that the same reviewers can verify.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.
# MobiCom Author Response MobiCom gives authors two distinct response instruments, and they are not the same job. The **rebuttal** is a short, bounded reply after round-2 reviews. The **one-shot revision** is a months-long contract against a required-changes list. Using rebuttal tactics on a revision, or revision ambition in a rebuttal, wastes both. ## Triage first, for either instrument Read all reviews once for facts, then sort every point: | Class | Definition | Response posture | |---|---|---| | Factual error | reviewer misread the paper | correct crisply, cite the section/figure | | Answerable question | a real gap you can address in the space/time | answer with the specific evidence | | Valid weakness | a fair criticism you cannot fully fix now | concede honestly; state what you will/can do | | Scope disagreement | reviewer wanted a different paper | acknowledge; defend the chosen scope briefly | The same reviewers usually carry the paper forward (`mobicom-review-process`), so credibility compounds — a fair concession is worth more than winning every argument. ## Writing the rebuttal The rebuttal is short and lands on a fixed clock; its exact length/format is 待核实 for the curr
- Triage first, for either instrument
- Writing the rebuttal
- Executing the one-shot revision
- Consistency across the arc
- Output format
What does the mobicom-author-response skill do?
Use when writing a MobiCom rebuttal after round-two reviews or executing a one-shot revision — triaging reviewer points by severity, fitting a factual, concession-honest rebuttal into its length limit, and turning a required-changes list into a change-highlighted revision with a change summary that the same reviewers can verify.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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 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.