Ngs Amazon Image Studio
binggandata/bggg-skills
Generate Amazon and cross-border ecommerce product images from a product business card.
A skill your agent uses when revising an MLSys paper's prose and structure, building the measured-bottleneck opening, naming the mechanism instead of listing optimizations, writing evaluation…
Install Mlsys Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-writing-style --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-writing-style .claude/skills/mlsys-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-writing-style into .claude/skills/mlsys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-writing-style", 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-writing-styleType 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-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-writing-style --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-writing-style .agents/skills/mlsys-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-writing-style into .agents/skills/mlsys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-writing-style", 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-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-writing-style --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-writing-style .cursor/skills/mlsys-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-writing-style into .cursor/skills/mlsys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-writing-style", 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-writing-style--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-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mlsys-writing-style --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-writing-style .gemini/skills/mlsys-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-writing-style into .gemini/skills/mlsys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-writing-style", 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-writing-styleInstalls 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-writing-style -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-writing-style .github/skills/mlsys-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-writing-style into .github/skills/mlsys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-writing-style", 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-writing-style -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-writing-style --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-writing-style .opencode/skills/mlsys-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/MLSys-Skills/skills/mlsys-writing-style into .opencode/skills/mlsys-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mlsys-writing-style", 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-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 845 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising an MLSys paper's prose and structure, building the measured-bottleneck opening, naming the mechanism instead of listing optimizations, writing evaluation…
- Works in 5 steps: Bottleneck, measured. Open with the… → Why existing designs cannot remove it.… → Insight. The one observation that… → …
- Revising an MLSys papers prose and structure
- SKILL.md covers The first-page arc, Sentence-level rewrites, Evaluation sections answer… and Numbers discipline, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mlsys Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an MLSys paper's prose and structure, building the measured-bottleneck opening, naming the mechanism instead of listing optimizations, writing evaluation sections as answers to research questions, quantifying every performance claim with workload context, and fitting the argument into the venue's 10-page two-column body.
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 Research & Science, covering Brand voice and tone, Hypothesis generation and E-commerce operations. 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
- Revising an MLSys papers prose and structure
- Building the measured-bottleneck opening
- Naming the mechanism instead of listing optimizations
- Writing evaluation sections as answers to research questions
Example prompts
- “/mlsys-writing-style”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Bottleneck, measured. Open with the profiling fact that justifies the paper —
- Why existing designs cannot remove it. Mechanistic reasons per named system or
- Insight. The one observation that unlocks the design, stated in a sentence a
- Mechanism, named. Give the technique a noun. Anonymous "several optimizations"
- Payoff with scope. Ranged improvement, named baseline, stated cost or non-win.
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 Writing Style loads about 1.8k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 845 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). 845 words, ~1,767 tokens.
Download SKILL.mdSave it as
.claude/skills/mlsys-writing-style/SKILL.md (or your agent's skills folder).- name
- mlsys-writing-style
- description
- Use when revising an MLSys paper's prose and structure, building the measured-bottleneck opening, naming the mechanism instead of listing optimizations, writing evaluation sections as answers to research questions, quantifying every performance claim with workload context, and fitting the argument into the venue's 10-page two-column body.
MLSys Writing Style
Use this during drafting and revision. MLSys prose sits between two failure modes: the ML-paper voice (contribution bullets, related-work-first, benchmarks as decoration) and the tech-report voice (system tour, feature list, "extensive experiments"). The venue's own genre is different: a paper here is an argument about where time, memory, or money goes in an ML workload, and how a named idea changes that.
The first-page arc
- Bottleneck, measured. Open with the profiling fact that justifies the paper — a percentage, a stall, a cost line — on a workload the reader recognizes. If the introduction's first numbers appear in the evaluation section, the order is wrong.
- Why existing designs cannot remove it. Mechanistic reasons per named system or design family, not "prior work is limited."
- Insight. The one observation that unlocks the design, stated in a sentence a reader could repeat tomorrow.
- Mechanism, named. Give the technique a noun. Anonymous "several optimizations" is how research contributions disappear into engineering.
- Payoff with scope. Ranged improvement, named baseline, stated cost or non-win.
Sentence-level rewrites
| Draft pattern | MLSys-safe rewrite |
|---|---|
| "achieves up to 3.4x speedup" | "1.6-2.2x goodput at matched p99 across three traces (3.4x peak on the bursty trace)" |
| "significantly reduces memory" | "cuts peak activation memory 38% (Fig. 5), enabling batch 32 on one A100" |
| "our highly optimized implementation" | name the three optimizations and ablate them |
| "extensive experiments demonstrate" | "we answer four questions: (RQ1)..." |
| "existing systems suffer from poor utilization" | "SystemX idles the interconnect 41% of decode time on this trace (§2)" |
| "we believe this generalizes to other accelerators" | state the mechanism's hardware assumptions; claim only what was measured |
Evaluation sections answer questions
Structure the evaluation as research questions, each mapped to figures that answer it:
6. Evaluation
RQ1 Does <mechanism> improve end-to-end serving under realistic load? (6.2)
RQ2 Where does the gain come from? [ablation per component] (6.3)
RQ3 When does it *not* help? [load shapes, model sizes, hardware] (6.4)
RQ4 What does it cost? [memory, complexity, build time, $ ] (6.5)RQ3 and RQ4 are not optional at this venue; their absence is the strongest style-level predictor of skeptical reviews. A results tour organized by dataset instead of by question reads as unanalyzed output.
Numbers discipline
- Every performance number carries its workload, hardware, and variance context on first mention; naked speedups are marketing.
- Prefer goodput/latency-constrained framings over raw throughput when serving is involved — systems readers discount throughput wins that trash tails.
- Use consistent units and precision; a table mixing ms, s, and "x" invites arithmetic audits.
- When a number is estimated (cost models, projections to larger scale), typographically separate it from measured results and say how it was estimated.
Compression into 10 two-column pages
- The design section earns space in proportion to what the evaluation ablates; a component never ablated should be described in two sentences, not two columns.
- Background sections rarely deserve more than half a page — MLSys readers know the transformer, the GPU memory hierarchy, and the serving stack; spend the space on your workload characterization instead.
- Architecture diagrams beat prose walkthroughs; one good figure with numbered dataflow arrows replaces a column of "then the request is forwarded to."
- Move full configuration matrices to the separately-uploaded appendix, but keep the fairness-critical facts (baseline tuning budget) in the body — reviewers are not obliged to open the appendix.
- References are excluded from the 10 pages and must list all authors (2026 rule), so never compress by mutilating the bibliography.
Show full SKILL.md (320 more words)Show less
Figures and tables carry the paper
Systems reviewers form their judgment from the exhibits, then read prose to confirm it.
- The architecture figure: numbered dataflow, the new components visually distinct from inherited infrastructure, and no internal codenames. If a reader cannot locate the contribution in this figure, the design section will not save it.
- The money figure: one plot that shows the headline claim with its constraint — typically goodput versus load with a p99 ceiling marked, both systems on the same axes. Reviewers screenshot this one into their reviews.
- Every performance plot states hardware and trial count in the caption; captions are read during skims, body text is not.
- Log-scale axes are honest for spanning regimes but must be labeled loudly; a log axis that makes a 1.3x gap look large will be caught and remembered.
- Tables: bold the best number per row only if "best" is defined in the caption; include the variance column; never mix measured and projected numbers in one table without typographic separation.
Title and abstract mechanics
- Titles at this venue name the system or mechanism and the setting ("X:
<mechanism>for<workload class>"); cleverness that hides the topic costs discovery, since practitioners search proceedings by problem. - The abstract must contain at least one measured number with its workload context — an abstract with no number reads as a position paper here.
- Spell out the ML property and system constraint being co-designed in the first two
sentences; abstract readers include the reviewers bidding on papers, and bidding
mismatch produces the wrong panel (see
mlsys-review-process).
Anonymization without lobotomy (research track)
Blinding at a systems venue tempts authors to delete the deployment context that makes the paper credible. Keep the facts, drop the identity: "a production recommendation service serving tens of millions of daily requests" survives review; the company name returns at camera-ready. Scrub cluster hostnames and internal codenames from figures — profiler screenshots are the classic leak.
Output format
[Diagnosis] tech-report voice / ML-paper voice / MLSys-ready
[First-page arc] <bottleneck number present? insight? named mechanism? scoped payoff?>
[RQ structure] <RQ list; RQ3 (non-wins) and RQ4 (costs) present?>
[Claim rewrites] <naked number -> contextualized rewrite>
[Compression cuts] <un-ablated design prose, background, config matrices to move>
[Anonymity edits] <identity leaks to fix without deleting context>© 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-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mlsys Writing Style 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 Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Ngs Amazon Image Studiobinggandata/bggg-skills | 605 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Academic Venue Researchjoshua-zyy/academic-paper-writer | 115 | — | ~626 | Automated safety check: Pass | MIT | |
| Ccf Idea Optimizermikubaka88/CCFA-Skills | 3k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Brand Profilesocial-media-skills/skills | 134 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Johnny Suede WriteJasonColapietro/suede-creator-skills | 127 | — | ~7.9k | Automated safety check: Pass | MIT |
Similar skills
Academic Venue Research
joshua-zyy/academic-paper-writer
Research target venue requirements and writing style for CS/AI/ML papers.
Ccf Idea Optimizer
mikubaka88/CCFA-Skills
Develop and optimize rough CCF research ideas into problems, insights, mechanisms, and evidence plans.
Brand Profile
social-media-skills/skills
Use FIRST, before any other social media skill, to load or create the brand profile — the durable record of who a business is, who it serves, how it sounds, and what it will and won't say.
Johnny Suede Write
JasonColapietro/suede-creator-skills
Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection…
Agsy Writing Style
franklee16/academic-research-skills
A skill your agent uses when drafting or polishing an Agricultural Systems (AgSy) manuscript so it reads clearly for a systems-science audience, follows the journal's format, and meets front-matter…
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
Questions about Mlsys Writing Style
What does Mlsys Writing Style do?
A skill your agent uses when revising an MLSys paper's prose and structure, building the measured-bottleneck opening, naming the mechanism instead of listing optimizations, writing evaluation…. Mlsys Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising an MLSys paper's prose and structure, building the measured-bottleneck opening, naming the mechanism instead of listing optimizations, writing evaluation sections as answers to research questions, quantifying every performance claim with workload context, and fitting the argument into the venue's 10-page two-column body.
When should I use Mlsys Writing Style?
Mlsys Writing Style fits situations like: revising an MLSys papers prose and structure; building the measured-bottleneck opening; naming the mechanism instead of listing optimizations; writing evaluation sections as answers to research questions.
How do I install Mlsys Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-writing-style -a claude-code`. Or copy the skill folder (MLSys-Skills/skills/mlsys-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mlsys-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Mlsys Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-writing-style -a codex`. Or copy the skill folder (MLSys-Skills/skills/mlsys-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mlsys-writing-style in your project. Codex loads it when a task matches its description.
Can I use Mlsys Writing Style 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-writing-style -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-writing-style, .gemini/skills/mlsys-writing-style, .github/skills/mlsys-writing-style and .opencode/skills/mlsys-writing-style in your project.
What does Mlsys Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Mlsys Writing Style is instructions for the agent only.
Does Mlsys Writing Style 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 Writing Style 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 Writing Style use?
Mlsys Writing Style 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 Writing Style use?
About 1.8k tokens (SKILL.md is roughly 7.1k 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 Writing Style?
Skills that share tags, products or a category with Mlsys Writing Style: Ngs Amazon Image Studio (binggandata/bggg-skills, 605 stars), Academic Venue Research (joshua-zyy/academic-paper-writer, 115 stars), Ccf Idea Optimizer (mikubaka88/CCFA-Skills, 3k stars) and Brand Profile (social-media-skills/skills, 134 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mlsys Writing Style?
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.