Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Agent skill
Mobisys Reproducibility
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when strengthening MobiSys reproducibility evidence — capturing device, SoC, OS build, framework and model versions, power-instrument setup, seeds, and thermal conditions so…
Install Mobisys Reproducibility
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-reproducibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-reproducibility --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-reproducibility .claude/skills/mobisys-reproducibility && 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-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-reproducibility into .claude/skills/mobisys-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-reproducibility", 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-reproducibilityType 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-reproducibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-reproducibility --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-reproducibility .agents/skills/mobisys-reproducibility && 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-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-reproducibility into .agents/skills/mobisys-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-reproducibility", 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-reproducibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-reproducibility --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-reproducibility .cursor/skills/mobisys-reproducibility && 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-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-reproducibility into .cursor/skills/mobisys-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-reproducibility", 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-reproducibility--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-reproducibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-reproducibility --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-reproducibility .gemini/skills/mobisys-reproducibility && 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-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-reproducibility into .gemini/skills/mobisys-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-reproducibility", 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-reproducibilityInstalls 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-reproducibility -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-reproducibility .github/skills/mobisys-reproducibility && 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-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-reproducibility into .github/skills/mobisys-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-reproducibility", 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-reproducibility -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-reproducibility --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-reproducibility .opencode/skills/mobisys-reproducibility && 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-reproducibility" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-reproducibility into .opencode/skills/mobisys-reproducibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-reproducibility", 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-reproducibility- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 516 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when strengthening MobiSys reproducibility evidence — capturing device, SoC, OS build, framework and model versions, power-instrument setup, seeds, and thermal conditions so…
- Strengthening MobiSys reproducibility evidence — capturing device
- SKILL.md covers Evidence map, What survives a different device, Vignette: an on-device… and Degrees of reproducibility, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Framework and model versions
What it does
Mobisys Reproducibility is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when strengthening MobiSys reproducibility evidence — capturing device, SoC, OS build, framework and model versions, power-instrument setup, seeds, and thermal conditions so an on-device result survives a different phone, deciding what data and firmware can legally ship, and keeping the paper consistent with the artifact for the ACM badge pipeline.
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.
It sits in Research & Science, covering Reproducible research. 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
- Strengthening MobiSys reproducibility evidence — capturing device
- Framework and model versions
- Power-instrument setup
- Thermal conditions so an on-device result survives a different phone
Example prompts
- “/mobisys-reproducibility”
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 Reproducibility loads about 1.1k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 516 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). 516 words, ~1,109 tokens.
Download SKILL.mdSave it as
.claude/skills/mobisys-reproducibility/SKILL.md (or your agent's skills folder).- name
- mobisys-reproducibility
- description
- Use when strengthening MobiSys reproducibility evidence — capturing device, SoC, OS build, framework and model versions, power-instrument setup, seeds, and thermal conditions so an on-device result survives a different phone, deciding what data and firmware can legally ship, and keeping the paper consistent with the artifact for the ACM badge pipeline.
MobiSys Reproducibility
Use this before submission and again before the artifact-evaluation deadline. On-device results are fragile across hardware and framework versions, so reproducibility at MobiSys is mostly about provenance: recording enough of the device and measurement context that someone on a different phone can rebuild the result.
Evidence map
- Map each latency, energy, throughput, and accuracy claim to a verifiable location in the paper, appendix, or artifact package.
- For each on-device result, record device model, SoC, OS build, framework/runtime version, model checkpoint hash, power source, ambient temperature, and thermal state at run start.
- Record the power-instrument setup and the energy boundary so an energy figure can be re-derived rather than trusted.
- For stochastic results, report seeds, repeated runs, and the spread; a single number from a single phone is not reproducible evidence.
- Explain missing data, firmware, or hardware honestly, and describe how a reader could reproduce the result in principle on a different device.
- Keep the artifact consistent with the manuscript; a number in the PDF that the artifact cannot regenerate is a review-risk multiplier and an AEC failure.
What survives a different device
| Provenance item | Turnkey answer | Common failure caught |
|---|---|---|
| Device + SoC + OS build | Named per experiment, in a table | "on a mobile device" with no model |
| Framework / runtime version | Pinned with hashes | Result drifts silently across a minor version |
| Energy instrument + boundary | Instrument, sampling rate, envelope stated | "efficient" with no measured joules |
| Thermal state | Ambient + steady-state trace | 30-second benchmark hides throttling |
| Model / cache version | Checkpoint hash, cache size | Accuracy irreproducible from a different weight file |
Marking a device result "reproducible" without its provenance is a recognizable MobiSys red flag, because the AEC and reviewers cross-check the artifact against the PDF and read a gap as carelessness about the rest of the paper.
Show full SKILL.md (222 more words)Show less
Vignette: an on-device inference paper
Consider a runtime that keeps CNN latency stable under load, validated on four phones. Its reproducibility spine: the four device models and OS builds, the runtime version and model checkpoint hashes, the power-monitor model and sampling rate, the ambient temperature and the steady-state thermal traces, the workload trace, the seeds and run counts — plus one honest sentence about the device it could not test and why the result may differ there.
Degrees of reproducibility
- Turnkey: one script regenerates each figure from logged runs on the target device.
- Scripted: scripts exist but need the specific hardware or manual device setup.
- Descriptive: prose detailed enough that a competent reader could rebuild the pipeline on a comparable device.
For MobiSys, the on-device measurement path should be as turnkey as the hardware allows, and a
hardware-optional downscaled or emulator path should let an evaluator without your exact
device reach at least Functional (mobisys-artifact-evaluation). State the achieved level
honestly rather than overpromising turnkey behavior that fails on a different phone.
Legal and privacy provenance
- Decide early what traces, firmware, and datasets can ship; on-device data often carries user, sensor, or vendor-firmware restrictions.
- Strip identifying content from screenshots, logs, and demo media before release.
- If data cannot ship, provide a synthetic or public substitute and name which results it cannot reproduce.
Output format
[Claim inventory] <claim -> evidence location>
[Provenance status] complete / partial / missing (device/OS/runtime/energy/thermal)
[Reproducibility gaps] <device pinning / seeds / energy boundary / model version>
[Paper fixes] <must appear in main PDF>
[Artifact fixes] <appendix or artifact additions, incl. hardware-optional path>© 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-reproducibility of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mobisys Reproducibility 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 Reproducibility this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Compute Environment Setupaipoch/open-science | 5.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Figure Styleaipoch/open-science | 5.5k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Bactopia Toolbactopia/bactopia | 522 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
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 Reproducibility
What does Mobisys Reproducibility do?
A skill your agent uses when strengthening MobiSys reproducibility evidence — capturing device, SoC, OS build, framework and model versions, power-instrument setup, seeds, and thermal conditions so…. Mobisys Reproducibility is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when strengthening MobiSys reproducibility evidence — capturing device, SoC, OS build, framework and model versions, power-instrument setup, seeds, and thermal conditions so an on-device result survives a different phone, deciding what data and firmware can legally ship, and keeping the paper consistent with the artifact for the ACM badge pipeline.
When should I use Mobisys Reproducibility?
Mobisys Reproducibility fits situations like: strengthening MobiSys reproducibility evidence — capturing device; framework and model versions; power-instrument setup; thermal conditions so an on-device result survives a different phone.
How do I install Mobisys Reproducibility in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-reproducibility -a claude-code`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-reproducibility in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobisys-reproducibility in your project. Claude Code loads it when a task matches its description.
How do I install Mobisys Reproducibility in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-reproducibility -a codex`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-reproducibility in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobisys-reproducibility in your project. Codex loads it when a task matches its description.
Can I use Mobisys Reproducibility 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-reproducibility -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-reproducibility, .gemini/skills/mobisys-reproducibility, .github/skills/mobisys-reproducibility and .opencode/skills/mobisys-reproducibility in your project.
What does Mobisys Reproducibility need to run?
SKILL.md names no scripts, command-line tools or credentials: Mobisys Reproducibility is instructions for the agent only.
Does Mobisys Reproducibility 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 Reproducibility 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 Reproducibility use?
Mobisys Reproducibility 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 Reproducibility use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Reproducibility?
Skills that share tags, products or a category with Mobisys Reproducibility: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Compute Environment Setup (aipoch/open-science, 5.5k stars) and Figure Style (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mobisys Reproducibility?
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.