Venue
LeoYeAI/openclaw-master-skills
Music venue where AI agents stream concerts as mathematics. An agent skill from LeoYeAI/openclaw-master-skills.
A skill your agent uses when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response…
MITAuto-check passed
Install Mlsys Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-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/MLSys-Skills/skills/mlsys-workflow .claude/skills/mlsys-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 "mlsys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-workflow into .claude/skills/mlsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-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/MLSys-Skills/skills/mlsys-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 mlsys-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-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/MLSys-Skills/skills/mlsys-workflow .agents/skills/mlsys-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 "mlsys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-workflow into .agents/skills/mlsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-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 mlsys-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-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/MLSys-Skills/skills/mlsys-workflow .cursor/skills/mlsys-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 "mlsys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-workflow into .cursor/skills/mlsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-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 MLSys-Skills/skills/mlsys-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 mlsys-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-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/MLSys-Skills/skills/mlsys-workflow .gemini/skills/mlsys-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 "mlsys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-workflow into .gemini/skills/mlsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-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 mlsys-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 mlsys-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/MLSys-Skills/skills/mlsys-workflow .github/skills/mlsys-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 "mlsys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-workflow into .github/skills/mlsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-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 mlsys-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 mlsys-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/MLSys-Skills/skills/mlsys-workflow .opencode/skills/mlsys-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 "mlsys-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-workflow into .opencode/skills/mlsys-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-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
mlsys-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 743 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response…
- Planning an MLSys submission cycle end to end
- SKILL.md covers The 2026-cycle shape, Backward plan from the paper…, Standing team rituals and Failure modes by stage, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- From venue-fit and track choice through evaluation freeze
What it does
Mlsys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response, notification, camera-ready, the March artifact-evaluation submission, and the May conference, with backward planning built around scarce GPU time and team ownership.
Its SKILL.md is about 1.7k 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 an MLSys submission cycle end to end
- From venue-fit and track choice through evaluation freeze
- The October deadline
- The four-day January response
Example prompts
- “/mlsys-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
Mlsys Workflow loads about 1.7k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 743 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). 743 words, ~1,710 tokens.
Download SKILL.mdSave it as
.claude/skills/mlsys-workflow/SKILL.md (or your agent's skills folder).- name
- mlsys-workflow
- description
- Use when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response, notification, camera-ready, the March artifact-evaluation submission, and the May conference, with backward planning built around scarce GPU time and team ownership.
MLSys Workflow
Use this as the project-management skill for a Conference on Machine Learning and Systems submission. MLSys runs one cycle per year, so a missed gate costs twelve months or a reroute to another venue. All dates below are the verified 2026-cycle timetable (access 2026-07-08) — treat them as shape, and replace every one with the current mlsys.org dates page before committing a plan.
MLSys is a conference with rotating per-edition leadership (2026: General Chair Luis Ceze; Program Chairs Zhihao Jia and Aakanksha Chowdhery) and no APC — proceedings publish open on proceedings.mlsys.org, and the money side is registration, where accepted-paper authors get a two-week reserved-ticket window.
The 2026-cycle shape
| Gate | 2026 anchor | What it demands |
|---|---|---|
| CFP and track choice | Summer 2025 (CFP publicized ~August) | Research vs industrial routing decided |
| Paper + appendix deadline | October 30, 2025 | Frozen evaluation, blinded PDF, separate appendix upload |
| Reviews released | January 12, 2026 | All authors on deck immediately |
| Author response due | January 16, 2026 | Four days — pre-planned, not improvised |
| Notification | January 25-26, 2026 | Branch: camera-ready+AE, or postmortem+reroute |
| Artifact evaluation submission | March 8, 2026 | Badge-ready package + Artifact Appendix |
| AE window | March 8 - April 8, 2026 | One author on call for evaluator questions |
| Conference | May 18-22, 2026 (Bellevue) | Registration inside reserved window, talk, travel |
Backward plan from the paper deadline
| Weeks out | Systems-paper milestone |
|---|---|
| 12+ | Bottleneck measurement done; mechanism designed; venue/track locked |
| 10 | Baselines installed, version-pinned, tuning protocol agreed |
| 8 | End-to-end prototype produces its first honest comparison |
| 6 | Full experiment matrix launched — GPU allocation is the critical path from here |
| 4 | Ablations and sensitivity sweeps done; figures generated from logs |
| 3 | Complete draft in the official two-column style; internal review by one systems and one ML reader |
| 2 | Evaluation freeze; only reviewer-anticipation runs remain |
| 1 | Anonymity sweep, appendix assembly as separate file, bibliography full-author check |
| 0 | Upload paper + appendix; verify both files from a logged-out view |
The distinctive constraint versus ML-venue planning: the evaluation competes for shared hardware. Reserve cluster time for weeks 6-4 when the matrix runs, and again for the January response window, where two rebuttal experiments may need machines on two days' notice.
Standing team rituals
Weekly (weeks 12->2):
- experiment-matrix review: rows launched / landed / failed, GPU budget burned
- claims board: abstract claim -> supporting figure -> status (red/yellow/green)
- baseline watch: new releases of compared systems since last week?
Once (week 3): mock review — one systems-culture and one ML-culture reader,
scored on workload realism, baseline fairness, attribution, and tails.
Response-week protocol (pre-agreed in December):
- who reads reviews hour 0, who owns machines, who drafts, who signs offFailure modes by stage
- Week 6 matrix slip: the sweep launches late, so ablations get cut — and ablation absence is precisely what MLSys reviews punish. Cut breadth (hardware variants) before cutting attribution (ablations).
- Baseline rot: a compared system ships a major release in September; deciding whether to re-run everything at week 4 needs a pre-agreed rule ("re-run headline comparisons if the release notes claim >10% on our metric").
- Response-window surprise: the four-day window found nobody available in January. It is on the calendar from the day of submission.
- Post-acceptance pile-up: camera-ready, AE package, and conference logistics all land in February-March; assign three different owners at notification time.
- Reroute paralysis after rejection: the systems-venue calendar (OSDI/SOSP/NSDI/ ASPLOS/ATC deadlines) should be listed in the postmortem doc before the decision arrives.
Show full SKILL.md (264 more words)Show less
The reroute decision, prepared in advance
Because the cycle is annual, "revise and resubmit to next MLSys" costs a year. Write the decision rule before the notification arrives:
| Rejection pattern | Indicated move |
|---|---|
| Workload/baseline objections, mechanism praised | Strengthen evaluation, resubmit to next MLSys — the reviews are a work list |
| "Insufficient novelty, solid engineering" | Industrial track next cycle, or a systems venue that weighs deployment insight |
| "Wrong audience" signals from both cultures | Re-read mlsys-topic-selection; the project may be OSDI/ASPLOS/NSDI-shaped |
| Split reviews, one culture convinced | Rewrite for the unconvinced culture; the paper, not the project, missed |
Maintain the alternative-deadline list (OSDI, SOSP, NSDI, ASPLOS, ATC, EuroSys, SC) with dates in the project doc from week 12, so a January rejection flows into a concrete February plan instead of a stall.
Ownership map (minimum viable)
- Evaluation owner: matrix, logs, figure regeneration.
- Baseline owner: versions, tuning parity, release watch.
- Writing owner: 10-page budget, style-kit compliance, claims board.
- Compliance owner: anonymity, appendix upload, OpenReview fields, deadlines.
- (Post-acceptance) AE owner: package, badges, evaluator on-call.
One person may hold two hats; no hat may be unassigned. Industrial-track submissions add a sixth hat that academic teams forget: the internal-approval owner, who clears company names, trace releases, and benchmark numbers with legal/PR — a process whose latency routinely exceeds the writing itself, so it starts at week 10, not week 1.
Cycle-volatility warning
Every date above, the track structure, the response-window length, and the AE mechanics are 2026 facts. The 2027 CFP was not yet visible at access time (待核实, all of it) — rebuild this table from mlsys.org before planning a real cycle.
Output format
[Current stage] fit / building / evaluating / writing / submitted / response / decided / AE
[Next official gate] <date + source URL>
[Critical path] <three tasks, with GPU-time dependencies flagged>
[Claims board] <claim -> figure -> status>
[Ownership] <evaluation/baseline/writing/compliance/AE -> person>
[Risk register] <matrix slip / baseline rot / response availability / logistics pile-up>© 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 MLSys-Skills/skills/mlsys-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mlsys 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 |
|---|---|---|---|---|---|---|
| Mlsys Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| VenueLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Credit Cycle Analysissickn33/agentic-awesome-skills | 47k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Scientific Venue Templatesdavila7/claude-code-templates | 32k | 9 repos | ~5.1k | Automated safety check: Notes | MIT | |
| Venue Templatesaipoch/medical-research-skills | 2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Venue TemplatesK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Credit Cycle Analysis
sickn33/agentic-awesome-skills
Debtor and creditor credit-cycle analysis: weighted collection or payment days, ageing buckets, credit limit utilisation and gap against benchmark.
Scientific Venue Templates
davila7/claude-code-templates
Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.
Venue Templates
aipoch/medical-research-skills
Venue-specific LaTeX templates, formatting requirements, and submission guidelines for journals, conferences, posters, and grants—use when a target venue imposes strict layout, page limits…
Venue Templates
K-Dense-AI/claude-scientific-writer
Prepare journal manuscripts, conference papers, research posters, and grant documents using venue-specific formatting guidance and bundled LaTeX scaffolds.
Academic Venue Templates
foryourhealth111-pixel/Vibe-Skills
Supplies venue-specific LaTeX templates and formatting rules for journals, conferences and posters, and checks a manuscript against page limits and submission requirements.
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 Mlsys Workflow
What does Mlsys Workflow do?
A skill your agent uses when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response…. Mlsys Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an MLSys submission cycle end to end, from venue-fit and track choice through evaluation freeze, the October deadline, the four-day January response, notification, camera-ready, the March artifact-evaluation submission, and the May conference, with backward planning built around scarce GPU time and team ownership.
When should I use Mlsys Workflow?
Mlsys Workflow fits situations like: planning an MLSys submission cycle end to end; from venue-fit and track choice through evaluation freeze; the October deadline; the four-day January response.
How do I install Mlsys Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-workflow -a claude-code`. Or copy the skill folder (MLSys-Skills/skills/mlsys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mlsys-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Mlsys Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-workflow -a codex`. Or copy the skill folder (MLSys-Skills/skills/mlsys-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mlsys-workflow in your project. Codex loads it when a task matches its description.
Can I use Mlsys 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 mlsys-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/mlsys-workflow, .gemini/skills/mlsys-workflow, .github/skills/mlsys-workflow and .opencode/skills/mlsys-workflow in your project.
What does Mlsys Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Mlsys Workflow is instructions for the agent only.
Does Mlsys 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 Mlsys 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 Mlsys Workflow use?
Mlsys 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 Mlsys Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Mlsys Workflow?
Skills that share tags, products or a category with Mlsys Workflow: Venue (LeoYeAI/openclaw-master-skills, 2.2k stars), Credit Cycle Analysis (sickn33/agentic-awesome-skills, 47k stars), Scientific Venue Templates (davila7/claude-code-templates, 32k stars) and Venue Templates (aipoch/medical-research-skills, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mlsys Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,216 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.