Research Writing
alfonso0512/research-writing-skill
科研论文写作助手，提供 30 个 Prompt 模板覆盖论文写作全流程. An agent skill from alfonso0512/research-writing-skill.
A skill your agent uses when preparing an accepted MLSys paper for publication on proceedings.mlsys.org, covering de-anonymization of the research-track PDF, restoring company and repository…
Install Mlsys Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-camera-ready --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-camera-ready .claude/skills/mlsys-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-camera-ready into .claude/skills/mlsys-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-camera-ready", 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-camera-readyType 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-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-camera-ready --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-camera-ready .agents/skills/mlsys-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-camera-ready into .agents/skills/mlsys-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-camera-ready", 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-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-camera-ready --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-camera-ready .cursor/skills/mlsys-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-camera-ready into .cursor/skills/mlsys-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-camera-ready", 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-camera-ready--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-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-camera-ready --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-camera-ready .gemini/skills/mlsys-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-camera-ready into .gemini/skills/mlsys-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-camera-ready", 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-camera-readyInstalls 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-camera-ready -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-camera-ready .github/skills/mlsys-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-camera-ready into .github/skills/mlsys-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-camera-ready", 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-camera-ready -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-camera-ready --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-camera-ready .opencode/skills/mlsys-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-camera-ready into .opencode/skills/mlsys-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-camera-ready", 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-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 903 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing an accepted MLSys paper for publication on proceedings.mlsys.org, covering de-anonymization of the research-track PDF, restoring company and repository…
- Preparing an accepted MLSys paper for publication on proceedings.mlsys.org
- SKILL.md covers Post-acceptance timeline…, De-anonymization sweep…, Reconciling the review record and Camera-ready package checklist, plus 4 more sections
- Calls pdftotext
- Covering de-anonymization of the research-track PDF
What it does
Mlsys Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted MLSys paper for publication on proceedings.mlsys.org, covering de-anonymization of the research-track PDF, restoring company and repository identity, reconciling promised rebuttal edits, the reserved-ticket registration window for authors, and sequencing camera-ready work against the artifact-evaluation deadline.
Its SKILL.md is about 1.8k 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 Documents & Office. 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
- Preparing an accepted MLSys paper for publication on proceedings.mlsys.org
- Covering de-anonymization of the research-track PDF
- Restoring company and repository identity
- Reconciling promised rebuttal edits
Example prompts
- “/mlsys-camera-ready”
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 Camera Ready loads about 1.8k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 903 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). 903 words, ~1,839 tokens.
Download SKILL.mdSave it as
.claude/skills/mlsys-camera-ready/SKILL.md (or your agent's skills folder).- name
- mlsys-camera-ready
- description
- Use when preparing an accepted MLSys paper for publication on proceedings.mlsys.org, covering de-anonymization of the research-track PDF, restoring company and repository identity, reconciling promised rebuttal edits, the reserved-ticket registration window for authors, and sequencing camera-ready work against the artifact-evaluation deadline.
MLSys Camera Ready
Use this after an MLSys acceptance. Two things make this venue's post-acceptance phase unusual: proceedings are published on the conference's own open archive (proceedings.mlsys.org, no publisher paywall and no APC), and the artifact-evaluation deadline lands in the same post-notification stretch — in 2026, notifications came January 25-26 and AE submissions were due March 8, so camera-ready and artifact packaging compete for the same weeks. Plan them as one project.
Post-acceptance timeline (2026-cycle anchors)
| Milestone | 2026 anchor | Owner risk |
|---|---|---|
| Notification | January 25-26, 2026 | — |
| Camera-ready deadline | 待核实 — appears in the decision email, not verified on a public page | Missing it silently drops the paper's polish window |
| Artifact submission to AE site | March 8, 2026 | Same people who owe the camera-ready |
| AE review window | March 8 - April 8, 2026 | Authors answer AE questions anonymously |
| Conference | May 18-22, 2026, Bellevue | Speaker travel, visas |
The camera-ready page allowance for accepted papers could not be verified from public pages (待核实): take limits, forms, and the exact due date from the decision email and the current author instructions, and treat any remembered number from prior cycles as stale.
De-anonymization sweep (research track)
The flip from blinded to published touches more than the author block:
- Restore authors, affiliations, acknowledgements, and funding lines, then recheck page fit — the added block can push a tight 10-page body over whatever the final limit is.
- Reverse the anonymization rewrites: "the system of [12]" becomes "our earlier system X" where that improves clarity; anonymous repository mirrors become the real, licensed, citable repository.
- Reinstate the production context the research track forced you to blur — cluster names, deployment scale, company identity — exactly where it strengthens claims, and get any employer publication-approval done before the deadline, not after.
- Verify every URL in the PDF from a logged-out browser: the artifact link in particular will be followed by AE reviewers and by readers for years.
# Confirm no anonymization debris survived the flip
pdftotext camera_ready.pdf - | grep -inE 'anonym|blinded|redacted|under review' | head
# Confirm metadata now identifies the authors intentionally
pdfinfo camera_ready.pdf | grep -iE 'author|title'Reconciling the review record
- Implement every edit promised in the author response, and keep a private map from reviewer concern to the section where the fix landed — program chairs spot-check, and the discipline prevents accidental promise-dropping.
- Do not smuggle in new headline results. Numbers may be re-run for polish, but a claim the reviewers never saw does not belong in the proceedings version; route genuinely new material to the artifact appendix or a follow-up.
- Update the "why now" framing only if reviews demanded it — the LLM-systems literature moves fast enough that intros rot in three months, but rewriting the story post- acceptance risks inconsistency with what was evaluated.
Camera-ready package checklist
- Final PDF built from the official style kit in its accepted-paper mode.
- Source files if the instructions require them (待核实 per cycle).
- Abstract and title in the conference system matching the PDF exactly — these feed the proceedings page and the schedule.
- Artifact Appendix aligned with the AE submission, so the paper's pointers and the evaluated artifact do not diverge.
- Whatever copyright or release form the decision email specifies (待核实; MLSys's own proceedings model means this may be lighter than ACM/IEEE norms — read, don't assume).
Show full SKILL.md (398 more words)Show less
Proceedings metadata and long-term findability
proceedings.mlsys.org is the paper's permanent address; its metadata is generated from what you submit, so errors fossilize:
- Author name forms: agree the canonical spelling (diacritics, middle initials) across all authors before submission — proceedings pages, DBLP scraping, and citation managers will propagate whatever lands there.
- The abstract on the proceedings page is what most future readers see before deciding to click; re-read it as a standalone advertisement after de-anonymization, since blinding sometimes left it vaguer than it needs to be.
- Put the artifact repository URL and badge status in the paper's stated location (footnote or dedicated section per the current instructions) so the proceedings PDF and the badge record reinforce each other.
- If you also maintain an arXiv version, update it to the camera-ready after publication and add the proceedings reference — divergent public versions of an MLSys paper confuse the exact readers (practitioners) the venue reaches best.
Talk and poster preparation
- MLSys audiences mix researchers with practitioners who may adopt the system that week; open the talk with the measured bottleneck and the mechanism, compress related work to one slide, and end with the artifact link and badge status.
- Prepare the demo-or-plot fallback: sessions run tight, and a talk that depends on a live cluster fails in predictable ways. Pre-record anything that touches a network.
- Poster sessions at this venue turn into whiteboard debugging conversations; bring the architecture diagram and the ablation table, not sixteen result plots.
Registration and presentation logistics
- Verified: authors of accepted papers get a two-week window of access to reserved registration tickets (mlsys.org registration FAQ), protecting them if the conference sells out — but the window expires, so register inside it.
- Whether at least one author must present in person, and any remote-presentation fallback, could not be verified for 2026 (待核实) — confirm from the decision email before anyone declines travel.
- Prepare the talk/poster against the conference's published session format; MLSys mixes academic and industry audiences, so lead the talk with the measured bottleneck, not related work.
- Visa timelines are the silent killer for a late-May US conference with late-January notification; the presenting author's travel paperwork starts the week of acceptance, and a backup presenter is named at the same time.
- Budget the trip against the venue's hotel block early — the 2026 edition ran in a single conference hotel (Hyatt Regency Bellevue), where blocks sell out before camera-ready season ends.
Output format
[Camera-ready status] Ready / Needs fixes / Blocked
[Deadline sources] <decision email items confirmed: due date / page limit / forms>
[De-anonymization sweep] <author block/URLs/acknowledgements/approval status>
[Reviewer-promise map] <concern -> section where fixed>
[AE collision plan] <who does camera-ready vs artifact, and when>
[Registration] <reserved-window deadline + who registers>© 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-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mlsys Camera Ready 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 Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Research Writingalfonso0512/research-writing-skill | 487 | 1 repos | ~818 | Automated safety check: Pass | MIT | |
| Paper WritingMLNLP-World/Paper-Writing-Tips | 4.7k | — | ~630 | Automated safety check: Pass | None | |
| PaperjurySpark-To-Paper-Skills/paperjury | 1.2k | — | ~5.3k | Automated safety check: Pass | MIT | |
| Literature Surveyai4s-research/ai4s-skills | 237 | 2 repos | ~2k | 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
Paper Writing
MLNLP-World/Paper-Writing-Tips
学术论文写作检查与优化助手。基于 MLNLP-World 社区整理的论文写作技巧，帮助检查和优化学术论文。Use when: (1) 检查论文 LaTeX 格式和排版, (2) 优化公式符号使用, (3) 改进图表设计, (4) 润色英文学术表达, (5) 检查参考文献格式, (6) 投稿前终稿检查, (7) 用户询问论文写作技巧或规范。
Paperjury
Spark-To-Paper-Skills/paperjury
Three modes for CS-conference papers (CVPR/ICCV/ECCV vision, ACL/EMNLP/NAACL NLP, ICLR/NeurIPS/ICML/AAAI ML).
Literature Survey
ai4s-research/ai4s-skills
A skill your agent uses when the user wants a comprehensive literature survey on a specific research topic.
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.
Press Conference Revision Evidence Bound
lensback940701/Evidence-Bound-Press-Conference-Revision-Skill
Diagnose and revise defensive academic writing while preserving claim ceilings, evidence status, scope conditions, rival explanations, and conceptual hierarchy.
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 Mlsys Camera Ready
What does Mlsys Camera Ready do?
A skill your agent uses when preparing an accepted MLSys paper for publication on proceedings.mlsys.org, covering de-anonymization of the research-track PDF, restoring company and repository…. Mlsys Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills.org, covering de-anonymization of the research-track PDF, restoring company and repository identity, reconciling promised rebuttal edits, the reserved-ticket registration window for authors, and sequencing camera-ready work against the artifact-evaluation deadline.
When should I use Mlsys Camera Ready?
Mlsys Camera Ready fits situations like: preparing an accepted MLSys paper for publication on proceedings.mlsys.org; covering de-anonymization of the research-track PDF; restoring company and repository identity; reconciling promised rebuttal edits.
How do I install Mlsys Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-camera-ready -a claude-code`. Or copy the skill folder (MLSys-Skills/skills/mlsys-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mlsys-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Mlsys Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-camera-ready -a codex`. Or copy the skill folder (MLSys-Skills/skills/mlsys-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mlsys-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Mlsys Camera Ready 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-camera-ready -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-camera-ready, .gemini/skills/mlsys-camera-ready, .github/skills/mlsys-camera-ready and .opencode/skills/mlsys-camera-ready in your project.
What does Mlsys Camera Ready need to run?
Going by SKILL.md and its folder, Mlsys Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Mlsys Camera Ready 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 Camera Ready 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 Camera Ready use?
Mlsys Camera Ready 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 Camera Ready use?
About 1.8k 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 Camera Ready?
Skills that share tags, products or a category with Mlsys Camera Ready: Research Writing (alfonso0512/research-writing-skill, 487 stars), Paper Writing (MLNLP-World/Paper-Writing-Tips, 4.7k stars), Paperjury (Spark-To-Paper-Skills/paperjury, 1.2k stars) and Literature Survey (ai4s-research/ai4s-skills, 237 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mlsys Camera Ready?
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.