Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Agent skill
Mobisys Author Response
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting a MobiSys rebuttal after round-2 reviews — working within the scope limit (correct factual errors, answer specific reviewer questions), adding only…
MITAuto-check passed
Install Mobisys Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-author-response --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-author-response .claude/skills/mobisys-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-author-response into .claude/skills/mobisys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-author-response", 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-author-responseType 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-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-author-response --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-author-response .agents/skills/mobisys-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-author-response into .agents/skills/mobisys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-author-response", 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-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-author-response --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-author-response .cursor/skills/mobisys-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-author-response into .cursor/skills/mobisys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-author-response", 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-author-response--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-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-author-response --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-author-response .gemini/skills/mobisys-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-author-response into .gemini/skills/mobisys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-author-response", 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-author-responseInstalls 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-author-response -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-author-response .github/skills/mobisys-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-author-response into .github/skills/mobisys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-author-response", 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-author-response -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-author-response --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-author-response .opencode/skills/mobisys-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-author-response into .opencode/skills/mobisys-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-author-response", 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-author-response- GitHub stars
- 1.2k
- Token cost
- ~930 tokens
- SKILL.md length
- 419 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting a MobiSys rebuttal after round-2 reviews — working within the scope limit (correct factual errors, answer specific reviewer questions), adding only…
- Works in 4 steps: State the decision-critical correction… → Point to exact submitted evidence… → Explain the systems consequence — what… → …
- Drafting a MobiSys rebuttal after round-2 reviews — working within the scope limit (correct factual errors
- SKILL.md covers Scope discipline, Triage, Drafting pattern and Systems-reviewer pushback…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mobisys Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 930 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
- 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
Example prompts
- “/mobisys-author-response”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- State the decision-critical correction or concession first.
- Point to exact submitted evidence (figure, table, appendix, artifact).
- Explain the systems consequence — what it means for the device claim.
- Promise a camera-ready fix only if it adds no unsupported claim and you can deliver it.
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 Author Response loads about 930 tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 419 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). 419 words, ~930 tokens.
Download SKILL.mdSave it as
.claude/skills/mobisys-author-response/SKILL.md (or your agent's skills folder).- name
- mobisys-author-response
- description
- 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.
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 who thinks you tested one device when you tested four), then address requests for a missing baseline, an energy boundary, or a break-condition experiment.
- One decision-critical point per reviewer beats an exhaustive reply; the AC reads for whether the central objection was actually resolved.
Drafting pattern
- State the decision-critical correction or concession first.
- Point to exact submitted evidence (figure, table, appendix, artifact).
- Explain the systems consequence — what it means for the device claim.
- Promise a camera-ready fix only if it adds no unsupported claim and you can deliver it.
Show full SKILL.md (163 more words)Show less
Systems-reviewer pushback patterns
| Pushback | What it signals | MobiSys-ready fix |
|---|---|---|
| "Evaluated on one device" | Generalization doubt | Point to the multi-device table, or promise the added device honestly |
| "Energy numbers are unconvincing" | Undefined instrument/boundary | Name the power monitor, sampling rate, and envelope already in App. A |
| "Only a 30-second benchmark" | Throttling hidden | Reference the sustained-load run and thermal trace, or promise one |
| "This is a better model, not a system" | Fit doubt | Re-anchor the contribution as the runtime/scheduling mechanism, with the ablation that isolates it |
Response micro-example
Reviewer objection: the latency win might vanish once the device throttles. Reply skeleton:
- Concede the concern is the right one to raise for sustained load.
- Point to the 20-minute run in Fig. 1 and the thermal trace in App. A, already submitted.
- Note the win holds to steady state on all four devices, with the numbers regenerable from the artifact.
- Offer one camera-ready sentence making the steady-state result explicit in the body.
Output format
[Priority issue] <reviewer concern>
[Decision dimension] contribution / on-device evidence / energy-latency rigor / clarity
[Draft response] <MobiSys-ready anonymous text within scope>
[Evidence anchor] <figure/table/appendix/artifact item>
[Out-of-scope content removed] <reargument, identity leaks, undeliverable promises>© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mobisys Author Response 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 Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~930 | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Socc Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Tacas Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Fast Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Icassp Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Socc Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ACM SoCC author response (rebuttal) during a round's response window, covering the single written turn, answering both the systems and the data/measurement…
Tacas Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting a TACAS (ETAPS) author response for the rebuttal window, covering the short single-round rebuttal, answering soundness and benchmark-fairness objections with…
Fast Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…
Icassp Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…
Aaai Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance…
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 Mobisys Author Response
What does Mobisys Author Response do?
A skill your agent uses when drafting a MobiSys rebuttal after round-2 reviews — working within the scope limit (correct factual errors, answer specific reviewer questions), adding only…. Mobisys Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Mobisys Author Response?
Mobisys Author Response fits situations like: 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.
How do I install Mobisys Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-author-response -a claude-code`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobisys-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Mobisys Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-author-response -a codex`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobisys-author-response in your project. Codex loads it when a task matches its description.
Can I use Mobisys Author Response 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-author-response -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-author-response, .gemini/skills/mobisys-author-response, .github/skills/mobisys-author-response and .opencode/skills/mobisys-author-response in your project.
What does Mobisys Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Mobisys Author Response is instructions for the agent only.
Does Mobisys Author Response 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 Author Response 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 Author Response use?
Mobisys Author Response 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 Author Response use?
About 930 tokens (SKILL.md is roughly 3.7k 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 Author Response?
Skills that share tags, products or a category with Mobisys Author Response: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Socc Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Tacas Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Fast Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mobisys Author Response?
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.