mobisys-artifact-evaluation
Use when packaging a MobiSys artifact for the Artifact Evaluation Committee — choosing among the three independent ACM badges (Available, Evaluated–Functional, Results Reproduced), building the workflow scripts the single-blind AEC runs on its own machines, and providing a hardware-optional path for evaluators who lack the exact phone, wearable, or board.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MobiSys Artifact Evaluation Use this for the MobiSys artifact submission. MobiSys has a strong, **script-first** artifact culture: the single-blind AEC runs the authors' workflow scripts on the reviewers' own systems, so an artifact that only works on your bench is not an artifact. ## The three ACM badges Authors may seek one, two, or all three independent badges; passing badges are printed on t
What does the mobisys-artifact-evaluation skill do?
Use when packaging a MobiSys artifact for the Artifact Evaluation Committee — choosing among the three independent ACM badges (Available, Evaluated–Functional, Results Reproduced), building the workflow scripts the single-blind AEC runs on its own machines, and providing a hardware-optional path for evaluators who lack the exact phone, wearable, or board.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-artifact-evaluation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.