Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
A skill your agent uses when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal…
MITAuto-check passed
Install Mobisys Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-workflow --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-workflow .claude/skills/mobisys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-workflow into .claude/skills/mobisys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-workflow --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-workflow .agents/skills/mobisys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-workflow into .agents/skills/mobisys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-workflow --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-workflow .cursor/skills/mobisys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-workflow into .cursor/skills/mobisys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mobisys-workflow --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-workflow .gemini/skills/mobisys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-workflow into .gemini/skills/mobisys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/mobisys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-workflow into .github/skills/mobisys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/mobisys-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MobiSys-Skills/skills/mobisys-workflow into .opencode/skills/mobisys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobisys-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 528 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal…
- Planning a MobiSys project timeline backward from the single early-December paper deadline through registration
- SKILL.md covers The one-deadline calendar, Milestones, Backward plan from the… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Two-round review with an early-reject cut
What it does
Mobisys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal, notification, artifact evaluation, camera-ready, and the June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Planning a MobiSys project timeline backward from the single early-December paper deadline through registration
- Two-round review with an early-reject cut
- Artifact evaluation
- The June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit
Example prompts
- “/mobisys-workflow”
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 Workflow loads about 1.2k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 528 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). 528 words, ~1,160 tokens.
Download SKILL.mdSave it as
.claude/skills/mobisys-workflow/SKILL.md (or your agent's skills folder).- name
- mobisys-workflow
- description
- Use when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal, notification, artifact evaluation, camera-ready, and the June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit.
MobiSys Workflow
Use this as the project-management skill for a MobiSys submission. Replace every date with the
current official timetable and work backward from the one hard December cutoff on the
mobisys<yy>.hotcrp.com/deadlines page.
MobiSys is a conference, not a journal: no standing editor-in-chief, no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Chairs (2026 General Chairs: Fahim Kawsar and Cecilia Mascolo; Program Chairs 待核实). Committees rotate yearly — re-check the current organizing-committee page rather than carrying a name forward.
The one-deadline calendar
Unlike MobiCom and NSDI, which run two deadlines a year, MobiSys runs a single paper deadline in early December feeding the following June conference. There is no second gate this cycle to catch a slip. That single fact governs the whole plan: the device experiments must be finished, not started, before December.
Milestones
- Venue fit: confirm the contribution is a mobile/embedded system whose device behavior is
the result (
mobisys-topic-selection). - Evidence lock: freeze the system design and finish the on-device measurement campaign — energy, latency, memory, thermal, and any deployment/user study.
- Paper registration: register title, abstract, authors, and conflicts on HotCRP before the registration cutoff that precedes the paper upload.
- Paper deadline: upload the anonymous 12-page double-column PDF and required HotCRP fields.
- Round-1 outcome: early-reject notifications go out; survivors proceed to round 2.
- Round-2 reviews + rebuttal: read reviews, then draft a scope-limited rebuttal
(
mobisys-author-response). - Notification: archive reviews, rebuttal, and decision.
- Acceptance: prepare the ACM camera-ready, artifact-evaluation submission, registration, and the June in-person talk and demo.
Backward plan from the December deadline
| Weeks out (heuristic) | Mobile-systems milestone |
|---|---|
| 12+ | System built; measurement harness and power instrument working end to end |
| 8 | On-device runs complete on all target devices; energy/latency logged with provenance |
| 6 | Deployment or user study done if the claim is a service |
| 4 | Full draft sitting in the 12-page ACM double-column template |
| 3 | Internal mock review by a systems reader; break-condition experiment added |
| 2 | Anonymity sweep including device/trace giveaways; artifact package smoke-tested |
| 1 | Numbers regenerated from logs so PDF and artifact cannot diverge |
| 0 | Registration then paper on HotCRP before the UTC cutoff |
These offsets are planning heuristics only — anchor each to the current official timetable, never to a previous cycle's calendar.
Show full SKILL.md (163 more words)Show less
Failure modes by stage
- Starting device measurement in November forces single-device, single-run results that read as under-evaluated — the classic MobiSys evidence reject.
- Leaving format conversion to the final week surfaces overflow late; the 12-page double-column budget is tighter than a working draft once figures are placed.
- Skipping the mock review forfeits the only chance to hear "your energy boundary is undefined" from a colleague instead of a reviewer.
- Building the artifact after the paper deadline forfeits the ACM badges, which need a working
script-first package the AEC can run on its own machines (
mobisys-artifact-evaluation).
Coordination notes
- Assign one named owner for the on-device measurement provenance and another for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, supplement, and artifact commit, since rebuttal replies must quote them precisely and camera-ready must match the reviewed version.
- Because a miss costs a full year, decide the go/no-go on evidence completeness by the four-week mark, not on deadline night.
Output format
[Current stage] idea / building / measuring / writing / registration / submitted / rebuttal / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <device evidence / page budget / anonymity / artifact / one-deadline slip>
[Owner map] <task -> person or role>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mobisys Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 99k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Tabler Backward Compatibilitytabler/tabler | 42k | — | ~4k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Tabler Backward Compatibility
tabler/tabler
Keeps changes to @tabler/core backward compatible so patch and minor releases never break projects, covering what counts as public API and how to alias renames.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
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…
Questions about Mobisys Workflow
What does Mobisys Workflow do?
A skill your agent uses when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal…. Mobisys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a MobiSys project timeline backward from the single early-December paper deadline through registration, two-round review with an early-reject cut, the rebuttal, notification, artifact evaluation, camera-ready, and the June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit.
When should I use Mobisys Workflow?
Mobisys Workflow fits situations like: planning a MobiSys project timeline backward from the single early-December paper deadline through registration; two-round review with an early-reject cut; artifact evaluation; the June conference — with device-experiment lead time built in and the one-deadline-per-year risk made explicit.
How do I install Mobisys Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-workflow -a claude-code`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mobisys-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Mobisys Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobisys-workflow -a codex`. Or copy the skill folder (MobiSys-Skills/skills/mobisys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mobisys-workflow in your project. Codex loads it when a task matches its description.
Can I use Mobisys Workflow 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-workflow -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-workflow, .gemini/skills/mobisys-workflow, .github/skills/mobisys-workflow and .opencode/skills/mobisys-workflow in your project.
What does Mobisys Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Mobisys Workflow is instructions for the agent only.
Does Mobisys Workflow 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 Workflow 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 Workflow use?
Mobisys Workflow 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 Workflow use?
About 1.2k tokens (SKILL.md is roughly 4.6k 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 Workflow?
Skills that share tags, products or a category with Mobisys Workflow: Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Tabler Backward Compatibility (tabler/tabler, 42k stars) and Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mobisys Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.