A skill your agent uses when revising a MobiSys paper for a mobile-systems first page, the pain → system-design → on-device-evidence arc, 12-page double-column compression, double-blind wording, and…

MITAuto-check passedWriting & Content

Install Mobisys Writing Style

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

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

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-writing-style --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-writing-style .claude/skills/mobisys-writing-style && 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-writing-style
GitHub stars
1.2k
Token cost
~922 tokens
SKILL.md length
421 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when revising a MobiSys paper for a mobile-systems first page, the pain → system-design → on-device-evidence arc, 12-page double-column compression, double-blind wording, and…

  • Revising a MobiSys paper for a mobile-systems first page
  • SKILL.md covers Revision rules, System-presentation discipline, Sentence-level rewrites and Vignette: compressing into…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • The pain → system-design → on-device-evidence arc

What it does

Mobisys Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a MobiSys paper for a mobile-systems first page, the pain → system-design → on-device-evidence arc, 12-page double-column compression, double-blind wording, and claims disciplined by measured latency, energy, memory, and thermal budgets rather than superlatives, so the draft survives systems-and-services reviewers.

Its SKILL.md is about 920 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 Writing & Content, covering Brand voice and tone. 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

  • Revising a MobiSys paper for a mobile-systems first page
  • The pain → system-design → on-device-evidence arc
  • 12-page double-column compression
  • Double-blind wording

Example prompts

  • “/mobisys-writing-style”

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 Writing Style loads about 922 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 421 words of instructions outside code blocks.

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

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). 421 words, ~922 tokens.

Download SKILL.mdSave it as .claude/skills/mobisys-writing-style/SKILL.md (or your agent's skills folder).
name
mobisys-writing-style
description
Use when revising a MobiSys paper for a mobile-systems first page, the pain → system-design → on-device-evidence arc, 12-page double-column compression, double-blind wording, and claims disciplined by measured latency, energy, memory, and thermal budgets rather than superlatives, so the draft survives systems-and-services reviewers.

MobiSys Writing Style

Use this when revising the main paper. A MobiSys paper needs a compact statement of the on-device problem, the system that solves it, and the measurements that prove it — in the 12-page double-column body.

Revision rules

  • Put the mobile-system contribution on the first page: the on-device pain, why current systems fail on the device, the mechanism, and the measured payoff.
  • Name the device budget explicitly. MobiSys reviewers are sensitive to hidden compute, energy, latency, memory, and thermal assumptions.
  • Pair every major claim with a measurement on real hardware, a design argument, or a reproducibility detail — never a superlative.
  • Use the 12-page body for the system's spine; move long protocols, extra device sweeps, and extended ablations to the appendix without making the main paper unintelligible.
  • Avoid overclaiming wins when the distribution is unreported or the gain is inside run-to-run spread.
  • Maintain double-blind style in self-citations, prior-system references, acknowledgements, funding, screenshots, and artifact descriptions.

System-presentation discipline

  • State the operating point: the device, the workload, and the budget the system respects. A latency number without its device and workload is not interpretable.
  • Give each design decision a why-on-the-device justification; MobiSys readers audit whether a choice is forced by the mobile constraint or merely convenient.
  • Report costs as distributions — p50/p95 latency, energy-per-operation, memory footprint — not single "up to N×" peaks.
  • Separate measured from estimated: an energy figure from a power monitor and an energy figure from a model are different claims and must be labeled so.
  • Keep the accuracy/quality trade-off honest: a system that is faster or cooler at a cost must state the cost in the same breath.
Show full SKILL.md (153 more words)Show less

Sentence-level rewrites

Draft patternMobiSys-safe rewrite
"Our system significantly outperforms...""cuts p95 latency from X ms to Y ms on <device> over N runs"
"Runs efficiently on mobile devices...""holds 30 fps within a 3 W budget on <device>, App. A"
"Saves substantial energy...""reduces energy-per-frame by X mJ (p50), measured on <monitor>"
"Achieves real-time performance..."Claim scoped to the device, workload, and thermal state tested

Vignette: compressing into twelve double-column pages

A draft with a runtime design, five device studies, and a sprawling background section: keep the design, one decision-critical figure (the latency-under-load curve) and one budget figure (energy-per-frame), and the accuracy-cost table; compress background into the specific failures current systems show on the device; move three device sweeps and the full protocol to the appendix with forward references. The test of a good cut: a systems reviewer should reconstruct the whole system and its evidence without opening the supplement.

Output format

text
[Writing diagnosis] clear / under-measured / overclaimed / overloaded
[First-page fix] <new mobile-system framing>
[Claim discipline] <claim -> measurement/design/limitation>
[Compression cuts] <move/delete/merge>
[Anonymity edits] <phrases, screenshots, or repo strings to rewrite>

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

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Mobisys Writing Style 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 Writing Style compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobisys Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~922Automated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
BrandOhh-889/skyroc79513 repos~733Automated safety check: PassMIT
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k1 repos~2.9kAutomated safety check: PassMIT
Writing Guidelinesvercel-labs/agent-skills32k7 repos~309Automated safety check: PassNone
Unslop AI Writing Cleanuptheclaymethod/unslop518—~1.7kAutomated safety check: PassMIT

Similar skills

  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • Brand

    Ohh-889/skyroc

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency.

    795 GitHub starsUsed in 13 repos~733 tokens
    Writing & ContentAuto-check passed
  • Khazix WeChat Article Writer

    KKKKhazix/khazix-skills

    Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.

    21k GitHub starsUsed in 1 repo~2.9k tokens
    Writing & ContentAuto-check passed
  • Writing Guidelines

    vercel-labs/agent-skills

    Official

    Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.

    32k GitHub starsUsed in 7 repos~309 tokens
    Writing & ContentAuto-check passed
  • Unslop AI Writing Cleanup

    theclaymethod/unslop

    Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.

    518 GitHub stars~1.7k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • UX Writing

    content-designer/ux-writing-skill

    Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.

    224 GitHub starsUsed in 1 repo~3.8k tokens
    Writing & ContentAuto-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 Writing Style

What does Mobisys Writing Style do?

A skill your agent uses when revising a MobiSys paper for a mobile-systems first page, the pain → system-design → on-device-evidence arc, 12-page double-column compression, double-blind wording, and…. Mobisys Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a MobiSys paper for a mobile-systems first page, the pain → system-design → on-device-evidence arc, 12-page double-column compression, double-blind wording, and claims disciplined by measured latency, energy, memory, and thermal budgets rather than superlatives, so the draft survives systems-and-services reviewers.

When should I use Mobisys Writing Style?

Mobisys Writing Style fits situations like: revising a MobiSys paper for a mobile-systems first page; the pain → system-design → on-device-evidence arc; 12-page double-column compression; double-blind wording.

How do I install Mobisys Writing Style in Claude Code?

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

How do I install Mobisys Writing Style in Codex?

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

Can I use Mobisys Writing Style 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-writing-style -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-writing-style, .gemini/skills/mobisys-writing-style, .github/skills/mobisys-writing-style and .opencode/skills/mobisys-writing-style in your project.

What does Mobisys Writing Style need to run?

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

Does Mobisys Writing Style 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 Writing Style 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 Writing Style use?

Mobisys Writing Style 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 Writing Style use?

About 922 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 Writing Style?

Skills that share tags, products or a category with Mobisys Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobisys Writing Style?

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.