Authoring VPhone Patch Sets
Lakr233/vphone-cli
Explains how to declare a firmware patch in a vphone patch set, add a new set, or write a preset, including naming, gating and the checks that catch undeclared patches.
Agent skill
Mobisys Topic Selection
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is…
Install Mobisys Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-topic-selection --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-topic-selection .claude/skills/mobisys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-topic-selection into .claude/skills/mobisys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-topic-selection", 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-topic-selectionType 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-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-topic-selection --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-topic-selection .agents/skills/mobisys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-topic-selection into .agents/skills/mobisys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-topic-selection", 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-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-topic-selection --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-topic-selection .cursor/skills/mobisys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-topic-selection into .cursor/skills/mobisys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-topic-selection", 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-topic-selection--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-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-topic-selection --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-topic-selection .gemini/skills/mobisys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-topic-selection into .gemini/skills/mobisys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-topic-selection", 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-topic-selectionInstalls 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-topic-selection -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-topic-selection .github/skills/mobisys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-topic-selection into .github/skills/mobisys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-topic-selection", 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-topic-selection -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-topic-selection --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-topic-selection .opencode/skills/mobisys-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-topic-selection into .opencode/skills/mobisys-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-topic-selection", 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-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 594 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is…
- Works in 4 steps: Is the contribution a mobile or embedded… → Does the device constraint shape the… → Is there on-device evidence, or a… → …
- Deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile
- SKILL.md covers The fit test, Routing map, Contribution-type honesty and Common misfit patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mobisys Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is the result, and routing wireless, sensor-network, distributed-systems, ubicomp, or early-idea misfits to MobiCom, SenSys, NSDI/OSDI, IMWUT, or HotMobile.
Its SKILL.md is about 1.3k 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 Development, covering Embedded systems. 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
- Deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile
- Embedded system
- Service whose on-device behavior is the result
- Routing wireless
Example prompts
- “/mobisys-topic-selection”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Is the contribution a mobile or embedded system? A runtime, an OS/platform mechanism,
- Does the device constraint shape the result? If compute, energy, latency, memory, or
- Is there on-device evidence, or a credible plan for it? MobiSys expects real phones,
- Would MobiSys's systems-and-services reviewers be the right audience? Say why in one
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 Topic Selection loads about 1.3k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 594 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). 594 words, ~1,338 tokens.
Download SKILL.mdSave it as
.claude/skills/mobisys-topic-selection/SKILL.md (or your agent's skills folder).- name
- mobisys-topic-selection
- description
- Use when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is the result, and routing wireless, sensor-network, distributed-systems, ubicomp, or early-idea misfits to MobiCom, SenSys, NSDI/OSDI, IMWUT, or HotMobile.
MobiSys Topic Selection
MobiSys is the ACM SIGMOBILE venue for mobile systems, applications, and services — the system that runs on the device, not the radio underneath it. The fastest way to waste a year-long cycle is to submit a paper whose real contribution belongs one venue over. This skill is a fit and routing tool, not a substitute for the current CFP scope list.
The fit test
A MobiSys-shaped paper answers all four:
- Is the contribution a mobile or embedded system? A runtime, an OS/platform mechanism, an on-device inference engine, a sensing pipeline, an offload scheduler, a mobile application or service — something built and run on the device, not an algorithm evaluated in the abstract.
- Does the device constraint shape the result? If compute, energy, latency, memory, or thermal budget could be idealized away with no loss, the contribution is probably not MobiSys's.
- Is there on-device evidence, or a credible plan for it? MobiSys expects real phones,
wearables, or embedded boards; a simulation-only story is a fit risk
(
mobisys-experiments). - Would MobiSys's systems-and-services reviewers be the right audience? Say why in one sentence using the venue's vocabulary, not "it is a top conference."
Routing map
Route by contribution type, not prestige. The nearest siblings and what pulls a paper to each:
| Signal in the contribution | Better-fit venue |
|---|---|
| Wireless/PHY-MAC mechanism, protocol, or RF sensing as the core | ACM MobiCom |
| Sensor-network / embedded-sensing infrastructure at large | ACM SenSys |
| Data-center, cloud, or distributed-systems design and implementation | USENIX NSDI / OSDI |
| Operating-system generality beyond mobile | USENIX OSDI / ACM SOSP |
| Ubiquitous-computing / on-body inference as the finding | ACM IMWUT (UbiComp) |
| Security or privacy of mobile as the central claim | a security venue |
| Early idea without a full on-device evaluation | HotMobile or a workshop |
The MobiSys↔MobiCom line is the one authors get wrong most: a wireless mechanism is MobiCom; an end-to-end mobile system whose device behavior is the point is MobiSys. The MobiSys↔SenSys line is the second: a sensing infrastructure is SenSys; a mobile platform, app, or service built on sensing is MobiSys. When two are present, decide which is the contribution and which is the vehicle.
Show full SKILL.md (243 more words)Show less
Contribution-type honesty
Name the contribution before choosing the venue:
[Contribution type] mobile runtime / OS-platform mechanism / on-device ML system /
sensing service / offload scheduler / mobile app-service / other
[Device dependence] does the result change if compute/energy/latency is idealized? y/n
[Evidence form] real-device measurement / deployment / user study / trace / simulation-only
[Primary audience] the MobiSys sub-community that should review itIf the type is "on-device ML system," MobiSys rewards a resource-management or runtime contribution (scheduling, approximation, placement, thermal control), not a better model — a new architecture with mobile motivation routes to a machine-learning venue. If it is "sensing service," the mobile system and its on-device budget must be the contribution, not just the sensor.
Common misfit patterns
- The better-model paper. A more accurate network that happens to run on a phone; the system is incidental → a machine-learning venue, unless the runtime is the contribution.
- The wireless paper wearing a systems hat. A link/PHY result with a phone demo → MobiCom.
- The sensor-network paper. A multi-node embedded-sensing infrastructure → SenSys.
- The simulation-only system. A scheduler or runtime evaluated only in a simulator; strong ones still need on-device measurement to clear the bar.
- The distributed-systems paper with a mobile example. A cloud/back-end contribution with a mobile motivating scenario → NSDI/OSDI.
Re-routing decision
If the paper misses MobiSys's bar, do not force it into the December deadline — re-route by type and record why. A wireless mechanism goes to MobiCom, a sensing infrastructure to SenSys, a distributed-systems design to NSDI/OSDI, a ubicomp finding to IMWUT, an early idea to HotMobile. Because MobiSys runs one deadline a year, a misfit costs a full cycle, and the two-round review often surfaces it as an early reject after round 1 rather than a rescue — re-routing early is by far the cheaper move.
Output format
[Fit] High / Medium / Low (one-line reason in MobiSys's vocabulary)
[Contribution type] <named>
[Device dependence] result depends on compute/energy/latency/memory? y/n
[Evidence form] real-device / deployment / user study / trace / simulation-only
[Main gap] the single most important missing system mechanism or measurement
[Re-route] <sibling venue if not a fit, with the signal that sends it there>© 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-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mobisys Topic Selection 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 Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Authoring VPhone Patch SetsLakr233/vphone-cli | 15k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Sipeed I2C and SPI Hardware Controlsipeed/picoclaw | 30k | — | ~578 | Automated safety check: Pass | MIT | |
| RuView Hardware Setupruvnet/RuView | 97k | — | ~1.8k | Automated safety check: Notes | MIT | |
| Esp32 Firmware Engineeralxv2016/folloup-sticky | 116 | 1 repos | ~3.8k | Automated safety check: Pass | GPL-3.0 | |
| ExecuTorch Binary Size Reductionpytorch/executorch | 5.1k | — | ~793 | Automated safety check: Pass | Custom licence |
Similar skills
Sipeed I2C and SPI Hardware Control
sipeed/picoclaw
Reads and controls I2C and SPI peripherals on Sipeed boards such as LicheeRV Nano, MaixCAM and NanoKVM through the i2c and spi tools.
RuView Hardware Setup
ruvnet/RuView
Brings a RuView CSI sensing node online by building ESP32-S3 or ESP32-C6 firmware, flashing the board, provisioning WiFi and checking the serial output.
Esp32 Firmware Engineer
alxv2016/folloup-sticky
ESP32 firmware engineering for ESP-IDF projects. An agent skill from alxv2016/folloup-sticky.
ExecuTorch Binary Size Reduction
pytorch/executorch
Measures and shrinks the ExecuTorch runtime binary by building a size test, analyzing it with bloaty and landing each reduction as its own pull request.
RuView mmWave Radar Setup
ruvnet/RuView
Sets up and runs 60 GHz and 24 GHz mmWave radar sensing on ESP32 boards in RuView, alone or fused with WiFi CSI.
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 Topic Selection
What does Mobisys Topic Selection do?
A skill your agent uses when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is…. Mobisys Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile or embedded system, application, or service whose on-device behavior is the result, and routing wireless, sensor-network, distributed-systems, ubicomp, or early-idea misfits to MobiCom, SenSys, NSDI/OSDI, IMWUT, or HotMobile.
When should I use Mobisys Topic Selection?
Mobisys Topic Selection fits situations like: deciding whether a project belongs at MobiSys — testing whether the core contribution is a mobile; embedded system; service whose on-device behavior is the result; routing wireless.
How do I install Mobisys Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-topic-selection -a claude-code`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobisys-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Mobisys Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-topic-selection -a codex`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobisys-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Mobisys Topic Selection 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-topic-selection -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-topic-selection, .gemini/skills/mobisys-topic-selection, .github/skills/mobisys-topic-selection and .opencode/skills/mobisys-topic-selection in your project.
What does Mobisys Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Mobisys Topic Selection is instructions for the agent only.
Does Mobisys Topic Selection 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 Topic Selection 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 Topic Selection use?
Mobisys Topic Selection 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 Topic Selection use?
About 1.3k tokens (SKILL.md is roughly 5.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 Topic Selection?
Skills that share tags, products or a category with Mobisys Topic Selection: Authoring VPhone Patch Sets (Lakr233/vphone-cli, 15k stars), Sipeed I2C and SPI Hardware Control (sipeed/picoclaw, 30k stars), RuView Hardware Setup (ruvnet/RuView, 97k stars) and Esp32 Firmware Engineer (alxv2016/folloup-sticky, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mobisys Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.