Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
A skill your agent uses when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that…
Install Mlsys Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-submission --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-submission .claude/skills/mlsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-submission into .claude/skills/mlsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-submission --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-submission .agents/skills/mlsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-submission into .agents/skills/mlsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-submission --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-submission .cursor/skills/mlsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-submission into .cursor/skills/mlsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-submission --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-submission .gemini/skills/mlsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-submission into .gemini/skills/mlsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/mlsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-submission into .github/skills/mlsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-submission", 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-submission -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-submission --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-submission .opencode/skills/mlsys-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-submission into .opencode/skills/mlsys-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 887 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that…
- Works in 6 steps: Freeze the evaluation: no new runs after… → Rebuild every figure and table from… → Move one decision-critical element back… → …
- Auditing an MLSys submission for OpenReview readiness
- SKILL.md covers Track decision comes first, Format audit (2026-cycle…, Anonymity model — stricter and… and Dual-submission rules, plus 5 more sections
- Calls pdftotext
What it does
Mlsys Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that still permit arXiv posting, research-versus-industrial track requirements, dual-submission exceptions, style-kit compliance, and desk-reject triage before the deadline.
Its SKILL.md is about 1.9k 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 Research & Science, covering Academic paper search. It works with arXiv. 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
- Auditing an MLSys submission for OpenReview readiness
- Covering the two-column 10-page body excluding references
- The separate appendix upload
- Double-blind rules that still permit arXiv posting
Example prompts
- “/mlsys-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze the evaluation: no new runs after this point except reviewer-anticipation ablations
- Rebuild every figure and table from logged results with one command, so the PDF and the
- Move one decision-critical element back from the appendix into the body — the most common
- Run the anonymity sweep above on PDF, appendix, and any linked anonymous repo.
- Verify the bibliography lists all authors per reference; regenerate with a compliant style.
- Upload paper, then appendix (separate file), then re-open both from OpenReview as a
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.9k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 887 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). 887 words, ~1,850 tokens.
Download SKILL.mdSave it as
.claude/skills/mlsys-submission/SKILL.md (or your agent's skills folder).- name
- mlsys-submission
- description
- Use when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that still permit arXiv posting, research-versus-industrial track requirements, dual-submission exceptions, style-kit compliance, and desk-reject triage before the deadline.
MLSys Submission
Use this to run a pre-deadline audit of a Conference on Machine Learning and Systems submission. Facts below are anchored to the 2026 cycle (verified 2026-07-08); reopen the current Call for Research Papers and the Industrial Track call on mlsys.org before acting, because MLSys restructures its calls between cycles — the Industrial Track itself only appeared in 2026.
Track decision comes first
Everything downstream differs by track, so settle this before formatting anything.
| Question | Research track | Industrial track (new in 2026) |
|---|---|---|
| Novelty required? | Yes — previously unpublished research | No — but design methodology and detailed benchmarks of a built, large-scale system are expected |
| Anonymization | Full: authors, affiliations, self-references, acknowledgements | Author names hidden, but company names, product names, and URLs may remain |
| Typical author | Academic or industrial researcher with a new mechanism | Team reporting a production ML system's design and measured behavior |
| Cross-track submission | Forbidden to submit the same paper to both tracks | Same |
If the paper's strongest asset is deployment scale and operational insight rather than a new idea, the industrial track is the honest home — reviewers there are told not to demand novelty but will demand benchmark depth.
Format audit (2026-cycle anchors)
- Two-column layout from the official style kit (
mlsys2026style.zipin 2026, explicitly the same format as 2025). Do not touch margins, fonts, or spacing macros. - Main body up to 10 pages, references excluded. Every reference must list all authors —
no "et al." truncation in the bibliography; this is an explicit MLSys rule that automated
.bstchoices can silently violate. - Appendices are unlimited but are uploaded separately from the main PDF, are due at the same time, and reviewers are not required to read them. Anything decision-critical — the key ablation, the baseline configuration table — must live in the 10 pages.
- Abstract, title, and author fields in OpenReview must match the PDF; the submission goes
through the MLSys OpenReview group (in 2026:
MLSys.org/2026/Conference).
Anonymity model — stricter and looser than you expect
MLSys is double-blind and arXiv-tolerant: posting the paper publicly is allowed, but the submitted PDF must still make a good-faith anonymization effort. Practical consequences:
- Strip affiliations, acknowledgements, and grant numbers; rewrite "our system X, deployed at
<company>" phrasing in the research track. - Self-citations stay in third person ("Prior work [12] showed...", not "In our prior work").
- Do not cite your own arXiv version in a way that equates it with the submission.
- GitHub links in a research-track submission should point to anonymized mirrors; the named repository comes back at camera-ready and artifact evaluation.
# Pre-upload leak sweep on the built PDF and source tree
pdfinfo paper.pdf | grep -iE 'author|producer' # metadata identity
pdftotext paper.pdf - | grep -inE 'acknowledg|grant|@|github.com/[a-z0-9-]+' | head
grep -rinE 'copyright|institute|univers' *.tex | grep -v style | headDual-submission rules
- Ineligible: any paper simultaneously under review elsewhere or already published.
- Explicitly allowed: arXiv/technical-report versions of the submission.
- Conditionally allowed: expanded versions of papers from workshops with proceedings, subject to program-chair approval — email the workshop paper to the chairs and explain the delta; reviewers judge the added contribution, not the whole paper.
- The industrial track applies the same no-concurrent-review rule.
Desk-reject and triage table
| Trigger | Severity | Repair window |
|---|---|---|
| Body over 10 pages or modified style kit | Desk reject | None after the deadline |
| Identity leak in a research-track PDF | Desk reject or chair flag | None |
| Same paper in both tracks | Desk reject of both | None |
| Concurrent submission discovered | Reject plus venue-relations damage | None |
| References missing full author lists | Chair-level format flag | Before deadline only |
| Headline claim only supported in the appendix | Review-stage damage | Fixable in the writing pass |
Show full SKILL.md (336 more words)Show less
Final-week sequence for a systems paper
- Freeze the evaluation: no new runs after this point except reviewer-anticipation ablations already scripted; late numbers breed inconsistent tables.
- Rebuild every figure and table from logged results with one command, so the PDF and the future artifact cannot diverge.
- Move one decision-critical element back from the appendix into the body — the most common MLSys structural error is a main paper that outsources its proof of work.
- Run the anonymity sweep above on PDF, appendix, and any linked anonymous repo.
- Verify the bibliography lists all authors per reference; regenerate with a compliant style.
- Upload paper, then appendix (separate file), then re-open both from OpenReview as a logged-out check that the right files landed.
OpenReview field audit
The form is part of the submission; mismatches between form and PDF surface at the worst possible times (proceedings generation, conflict detection, notification email).
- Title and abstract: character-identical to the PDF — the form copy feeds the program and, on acceptance, the proceedings page.
- Author list: complete and ordered at submission time even though hidden from reviewers; adding an author later requires chair intervention.
- Conflicts: every author's DBLP-visible collaborators and institutions, including recent internships — MLSys's reviewer pool is small enough that a missed conflict is likely to actually bite.
- Subject areas: choose from the current CFP's list (systems-for-ML and ML-for-systems areas differ in reviewer routing); a mis-tagged paper draws the wrong culture of reviewer, which is a real scoring effect at this venue.
- Track selector: research vs industrial, irreversible after the deadline.
- Appendix upload slot: the separate file, confirmed present — an empty slot is a silent loss, not an error.
Cycle-volatility warnings
- The 10-page limit, separate-appendix mechanic, style-kit name, and track structure are 2026-cycle facts; the 2027 call may change any of them.
- No AI-use policy for authors was verifiable for the 2026 cycle (待核实) — check the current call rather than assuming either permission or prohibition.
- Deadlines in this pack's workflow skill are historical anchors, not next-cycle predictions.
Output format
[MLSys readiness] Ready / Needs fixes / Not ready
[Track] research / industrial / undecided (reason)
[Blocking checks] <pages/style/anonymity/appendix-split/references/dual-submission>
[Decision-critical content in body?] yes / no -> <what to pull forward>
[Desk-reject risk] <single highest risk>
[Fix order] <ordered fixes before upload>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mlsys Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Read arXiv Paperkarpathy/nanochat | 59k | 1 repos | ~494 | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Openalex Databaseneflibata-feng/MyArxiv-Agent | 126 | 12 repos | ~3k | Automated safety check: Pass | Custom licence | |
| Citation ManagementK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.9k | Automated safety check: Notes | MIT | |
| Citation Managementneflibata-feng/MyArxiv-Agent | 126 | 19 repos | ~8.1k | Automated safety check: Notes | MIT |
Similar skills
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Openalex Database
neflibata-feng/MyArxiv-Agent
Query and analyze scholarly literature using the OpenAlex database.
Citation Management
K-Dense-AI/claude-scientific-writer
Finds papers in OpenAlex, PubMed and Google Scholar, turns DOIs, PMIDs and arXiv IDs into clean BibTeX, and validates citations for a manuscript or thesis.
Citation Management
neflibata-feng/MyArxiv-Agent
Comprehensive citation management for academic research. An agent skill from neflibata-feng/MyArxiv-Agent.
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
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
Works with
Categories
Questions about Mlsys Submission
What does Mlsys Submission do?
A skill your agent uses when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that…. Mlsys Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an MLSys submission for OpenReview readiness, covering the two-column 10-page body excluding references, the separate appendix upload, double-blind rules that still permit arXiv posting, research-versus-industrial track requirements, dual-submission exceptions, style-kit compliance, and desk-reject triage before the deadline.
When should I use Mlsys Submission?
Mlsys Submission fits situations like: auditing an MLSys submission for OpenReview readiness; covering the two-column 10-page body excluding references; the separate appendix upload; double-blind rules that still permit arXiv posting.
How do I install Mlsys Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-submission -a claude-code`. Or copy the skill folder (MLSys-Skills/skills/mlsys-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mlsys-submission in your project. Claude Code loads it when a task matches its description.
How do I install Mlsys Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-submission -a codex`. Or copy the skill folder (MLSys-Skills/skills/mlsys-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mlsys-submission in your project. Codex loads it when a task matches its description.
Can I use Mlsys Submission 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-submission -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-submission, .gemini/skills/mlsys-submission, .github/skills/mlsys-submission and .opencode/skills/mlsys-submission in your project.
What does Mlsys Submission need to run?
Going by SKILL.md and its folder, Mlsys Submission needs the command-line tools its instructions call (pdftotext).
Does Mlsys Submission 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 Submission 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 Submission use?
Mlsys Submission 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 Submission use?
About 1.9k tokens (SKILL.md is roughly 7.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 Mlsys Submission?
Skills that share tags, products or a category with Mlsys Submission: Read arXiv Paper (karpathy/nanochat, 59k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Openalex Database (neflibata-feng/MyArxiv-Agent, 126 stars) and Citation Management (K-Dense-AI/claude-scientific-writer, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mlsys Submission?
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.