A skill your agent uses when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right…

MITAuto-check passedResearch & Science

Install Mobisys Related Work

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-related-work -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-related-work --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-related-work .claude/skills/mobisys-related-work && rm -rf skills-src

Use ~/.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/

Facts

Skill name
mobisys-related-work
GitHub stars
1.2k
Token cost
~1.1k tokens
SKILL.md length
465 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right…

  • Positioning a MobiSys submission against the mobile-systems literature — offload
  • SKILL.md covers Positioning checks, Literature lanes to sweep, Venue-verification discipline and Concurrent-work judgment calls, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Mobile OS and runtimes

What it does

Mobisys Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right lanes, handling concurrent work, verifying that cited "MobiSys papers" are MobiSys rather than MobiCom/SenSys/OSDI, and self-citing without breaking double-blind.

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 Literature review and Positioning and messaging. 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

  • Positioning a MobiSys submission against the mobile-systems literature — offload
  • Mobile OS and runtimes
  • Sensing services
  • Energy — covering the right lanes

Example prompts

  • “MobiSys papers”
  • “/mobisys-related-work”

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 Related Work loads about 1.1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 465 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~91
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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). 465 words, ~1,063 tokens.

Download SKILL.mdSave it as .claude/skills/mobisys-related-work/SKILL.md (or your agent's skills folder).
name
mobisys-related-work
description
Use when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right lanes, handling concurrent work, verifying that cited "MobiSys papers" are MobiSys rather than MobiCom/SenSys/OSDI, and self-citing without breaking double-blind.

Use this to audit novelty and coverage. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors. At MobiSys the failure mode is usually a too-narrow related-work section that misses a sibling-venue predecessor.

Positioning checks

  • Separate the system contribution from an engineering improvement: a new runtime mechanism, scheduling policy, on-device inference system, sensing service, or platform.
  • Cover the mobile-systems lanes below; a bibliography that cites only machine-learning papers tells a systems reviewer that known mobile-systems work may be getting rediscovered.
  • Treat ACM DL, USENIX, and IEEE proceedings as archival unless current rules say otherwise.
  • Cite arXiv and workshop versions in a way that preserves double-blind review; do not point reviewers to identity-revealing pages.
  • Use related work to sharpen what is new: a tighter energy budget, a lower latency tail, an on-device capability that previously required the cloud, or a deployment others only simulated.

Literature lanes to sweep

LaneTypical venuesWhat MobiSys reviewers check
Computation offload / edgeMobiSys, MobiCom, NSDI, EuroSysWhether the nearest offload system is compared or distinguished
On-device ML systemsMobiSys, SenSys, MLSys, ASPLOSWhether prior on-device runtimes/schedulers are acknowledged
Mobile OS / runtimeMobiSys, OSDI, SOSP, EuroSysWhether the platform mechanism has an OS-systems predecessor
Mobile sensing / ubicompMobiSys, SenSys, IMWUTWhether the sensing-service line is covered without misfiling
Energy / measurementMobiSys, SenSys, IMCWhether energy methodology follows established practice

A related-work section that ignores the SenSys or OSDI predecessor of a mobile-systems idea is a recognizable MobiSys reject pattern that no amount of on-device polish repairs.

Show full SKILL.md (209 more words)Show less

Venue-verification discipline

The mobile-systems canon is easy to misattribute because MobiSys, MobiCom, and SenSys share the SIGMOBILE umbrella:

  • Verify each cited "MobiSys paper" on the ACM DL and dblp by matching the conf/mobisys record; TaintDroid is OSDI, CenceMe is SenSys, RF-sensing classics are MobiCom/SIGCOMM (see ../../resources/exemplars/library.md).
  • Do not cite a paper as MobiSys from memory; a misattributed venue signals careless scholarship to a specialist reviewer.

Concurrent-work judgment calls

  • Independently concurrent arXiv work: cite neutrally, state the technical difference, and avoid priority claims reviewers cannot verify.
  • Your own workshop (e.g., HotMobile) version: typically non-archival and citable, but verify against the current CFP and phrase the citation so double-blind review survives.
  • When in doubt about the archival status of a venue, declare the overlap in the submission form rather than gambling on a chair's interpretation.

Positioning vignette

Imagine the paper proposes a thermal-aware on-device inference runtime. Its nearest neighbors: an on-device DNN scheduler at MobiSys with no thermal model, a mobile-GPU inference framework at MobiSys tuned for peak not sustained load, and an OS-level DVFS mechanism at OSDI. The novelty sentence should name all three contrasts — thermal-awareness where the scheduler had none, sustained-load stability where the GPU framework optimized peak, and application-level control where the OS mechanism was generic.

Output format

text
[Eligibility] clear / needs declaration / risky
[Closest lanes] <offload / on-device ML / mobile OS / sensing / energy>
[Nearest 3 works] <work -> distinction>
[Venue-verification risk] <none / misattribution issues>
[Novelty sentence] <MobiSys-ready contribution contrast>

© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Mobisys Related Work 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.

Mobisys Related Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobisys Related Work this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.1kAutomated safety check: PassMIT
Ieee Paper ReaderCloudWave818/ieee-skills359—~591Automated safety check: PassMIT
Novelty MatrixWILLOSCAR/research-units-pipeline-skills513—~364Automated safety check: PassNone
Gec Literature Positioningfranklee16/academic-research-skills2231 repos~855Automated safety check: PassNone
Jpsp Literature Positioningfranklee16/academic-research-skills2231 repos~850Automated safety check: PassNone
Neurips Related Workfranklee16/academic-research-skills2231 repos~491Automated safety check: PassNone

Similar skills

  • Ieee Paper Reader

    CloudWave818/ieee-skills

    Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.

    359 GitHub stars~591 tokensUpdated 2 mo ago
    Research & ScienceAuto-check passed
  • Novelty Matrix

    WILLOSCAR/research-units-pipeline-skills

    A skill your agent uses when paper-review needs overlap/delta positioning against provided related work.

    513 GitHub stars~364 tokensUpdated 6 days ago
    Research & ScienceAuto-check passed
  • Gec Literature Positioning

    franklee16/academic-research-skills

    A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.

    223 GitHub starsUsed in 1 repo~855 tokens
    Research & ScienceAuto-check passed
  • Jpsp Literature Positioning

    franklee16/academic-research-skills

    A skill your agent uses when positioning a Journal of Personality and Social Psychology (JPSP) manuscript against the literatures its section's readers expect, building the long-format introduction…

    223 GitHub starsUsed in 1 repo~850 tokens
    Research & ScienceAuto-check passed
  • Neurips Related Work

    franklee16/academic-research-skills

    A skill your agent uses when positioning a NeurIPS submission against current-cycle ML literature, contemporaneous work, preprints, neighboring conferences, and the exact technical delta from prior…

    223 GitHub starsUsed in 1 repo~491 tokens
    Research & ScienceAuto-check passed
  • Rje Literature Positioning

    franklee16/academic-research-skills

    A skill your agent uses to position a manuscript against the industrial-organization frontier for The RAND Journal of Economics (RJE) — staking the contribution against prior IO work without a…

    223 GitHub starsUsed in 1 repo~720 tokens
    Research & ScienceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo
  • Aaag 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed
  • 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…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Questions about Mobisys Related Work

What does Mobisys Related Work do?

A skill your agent uses when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right…. Mobisys Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a MobiSys submission against the mobile-systems literature — offload, on-device ML, mobile OS and runtimes, sensing services, and energy — covering the right lanes, handling concurrent work, verifying that cited "MobiSys papers" are MobiSys rather than MobiCom/SenSys/OSDI, and self-citing without breaking double-blind.

When should I use Mobisys Related Work?

Mobisys Related Work fits situations like: positioning a MobiSys submission against the mobile-systems literature — offload; mobile OS and runtimes; sensing services; energy — covering the right lanes.

How do I install Mobisys Related Work in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-related-work -a claude-code`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobisys-related-work in your project. Claude Code loads it when a task matches its description.

How do I install Mobisys Related Work in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-related-work -a codex`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobisys-related-work in your project. Codex loads it when a task matches its description.

Can I use Mobisys Related Work 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-related-work -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-related-work, .gemini/skills/mobisys-related-work, .github/skills/mobisys-related-work and .opencode/skills/mobisys-related-work in your project.

What does Mobisys Related Work need to run?

SKILL.md names no scripts, command-line tools or credentials: Mobisys Related Work is instructions for the agent only.

Does Mobisys Related Work 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 Related Work 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 Related Work use?

Mobisys Related Work 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 Related Work 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 Mobisys Related Work?

Skills that share tags, products or a category with Mobisys Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Novelty Matrix (WILLOSCAR/research-units-pipeline-skills, 513 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars) and Jpsp Literature Positioning (franklee16/academic-research-skills, 223 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobisys Related Work?

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.