Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when drafting or revising an OSDI paper's prose and structure — building the pain → abstraction → mechanism → measurement narrative, fitting it into the 12-page reviewed body…
Install Osdi Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-writing-style .claude/skills/osdi-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 "osdi-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-writing-style into .claude/skills/osdi-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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/OSDI-Skills/skills/osdi-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 osdi-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-writing-style .agents/skills/osdi-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 "osdi-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-writing-style into .agents/skills/osdi-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-writing-style .cursor/skills/osdi-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 "osdi-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-writing-style into .cursor/skills/osdi-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 OSDI-Skills/skills/osdi-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 osdi-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-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/OSDI-Skills/skills/osdi-writing-style .gemini/skills/osdi-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 "osdi-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-writing-style into .gemini/skills/osdi-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-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 osdi-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/OSDI-Skills/skills/osdi-writing-style .github/skills/osdi-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 "osdi-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-writing-style into .github/skills/osdi-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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 osdi-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 osdi-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/OSDI-Skills/skills/osdi-writing-style .opencode/skills/osdi-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 "osdi-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-writing-style into .opencode/skills/osdi-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-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
osdi-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 746 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting or revising an OSDI paper's prose and structure — building the pain → abstraction → mechanism → measurement narrative, fitting it into the 12-page reviewed body…
- Works in 6 steps: Pain — something operational breaks,… → Why existing designs cannot fix it —… → The idea, named — one abstraction,… → …
- Revising an OSDI papers prose and structure — building the pain → abstraction → mechanism → measurement narrative
- SKILL.md covers The narrative arc, Writing under the 12-page regime, Sentence-level habits of… and Mechanical format anchors…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Osdi Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising an OSDI paper's prose and structure — building the pain → abstraction → mechanism → measurement narrative, fitting it into the 12-page reviewed body with no appendix escape hatch, and writing for a PC told to down-rank padded papers and given no rebuttal to clarify with.
Its SKILL.md is about 1.6k 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 Writing & Content, covering Brand voice and tone. 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 OSDI papers prose and structure — building the pain → abstraction → mechanism → measurement narrative
- Fitting it into the 12-page reviewed body with no appendix escape hatch
- Writing for a PC told to down-rank padded papers and given no rebuttal to clarify with
Example prompts
- “/osdi-writing-style”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Pain — something operational breaks, stalls, or costs money, and the trend
- Why existing designs cannot fix it — each plausible alternative dispatched
- The idea, named — one abstraction, principle, or mechanism another builder
- The design that realizes it — decisions justified against the idea, with the
- The system that exists — implementation reality: lines, language, what is
- Measurements that answer questions — evaluation organized by research
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
Osdi Writing Style loads about 1.6k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 746 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). 746 words, ~1,591 tokens.
Download SKILL.mdSave it as
.claude/skills/osdi-writing-style/SKILL.md (or your agent's skills folder).- name
- osdi-writing-style
- description
- Use when drafting or revising an OSDI paper's prose and structure — building the pain → abstraction → mechanism → measurement narrative, fitting it into the 12-page reviewed body with no appendix escape hatch, and writing for a PC told to down-rank padded papers and given no rebuttal to clarify with.
OSDI Writing Style
Shape the paper the way OSDI reviewers read. Format numbers below are the OSDI '26 rules (12 reviewed pages including figures and tables, unlimited references, no appendices at submission — verified 2026-07-08); recheck the live CFP before trusting any of them for a later cycle.
The narrative arc
An OSDI paper is an argument that a design decision was right, carried by a built system. The arc, section by section:
- Pain — something operational breaks, stalls, or costs money, and the trend makes it worse. Not "X is important."
- Why existing designs cannot fix it — each plausible alternative dispatched with a mechanism-level reason. In a no-response cycle this paragraph is your rebuttal, delivered in advance.
- The idea, named — one abstraction, principle, or mechanism another builder could reuse, stated in a sentence a reviewer could repeat in the PC meeting.
- The design that realizes it — decisions justified against the idea, with the trade-offs admitted where they are made, not in a limitations afterthought.
- The system that exists — implementation reality: lines, language, what is real versus mocked.
- Measurements that answer questions — evaluation organized by research
question, each answered by an experiment (see
osdi-experiments).
The worked rewrite in
../../resources/worked-examples/01-introduction.md
executes this arc on a fictional storage system; the verified papers in
../../resources/exemplars/library.md execute
it for real.
Writing under the 12-page regime
Two 2026 rules jointly define the discipline:
- No appendices in the submission. References are unlimited, but everything reviewers may weigh lives in the 12 pages. There is no "details in Appendix B" move — either the detail earns body space or the paper must be convincing without it.
- Padding is penalized, not just wasted. The CFP tells authors the paper should be "the right length," possibly under 12 pages, and tells reviewers to down-rank overly padded papers. Twelve pages is a cap, not a target.
Practical consequences:
| Draft habit | Under OSDI '26 rules | Replacement |
|---|---|---|
| "See appendix for proof/protocol" | Nothing to point at | Compress the invariant into the body or cut the claim |
| Restating results in intro, design, and eval | Down-rank bait | Say each result once, where it lands hardest |
| Screenshot-quality figure walls | Page cost without argument | One figure per claim; captions that state the takeaway |
| Ten-line contribution bullet lists | First-page budget burned | Three claims a reviewer can test |
| Related-work essay | Crowds out the design | Positioning by difference (see osdi-related-work) |
Sentence-level habits of accepted systems prose
- Numbers carry their context. "3.2x faster" is meaningless until the baseline, workload, and cost ride in the same sentence.
- Agency stays with the design. "Ledger bounds recovery" not "recovery is bounded" — passive voice hides which component does the work.
- Trade-offs are sentences, not subordinate clauses. "This costs 11% write amplification" standing alone reads as honesty; buried mid-sentence it reads as concealment.
- Present tense for the system, past tense for the experiments. The system is; the runs were.
- No unresolved forward references. With no rebuttal, a reviewer confused on page 4 stays confused into the PC meeting.
Show full SKILL.md (251 more words)Show less
Mechanical format anchors (2026 cycle)
Body: <= 12 pages, single-spaced, 8.5" x 11", incl. figures & tables
References: unlimited pages, excluded from the 12
Appendices: NOT permitted in the submission (final papers: allowed, 14pp body)
Type: 10-point Times-like font on 12-point leading
Layout: two columns, text block 7" wide x 9" deep
Anonymity: authors AND institutions anonymized (see osdi-submission)Use the current USENIX template unmodified. Space is recovered by cutting argument redundancy — never by geometry, font, or leading tricks that chairs detect mechanically and treat as violations.
The abstract in seven sentences
OSDI abstracts follow the arc in miniature; a reliable skeleton:
- The operational pain, with its worsening trend.
- Why the standard fixes fail (one clause each is enough here).
- "We present
<System>," plus the named idea in the same sentence. - The mechanism that realizes the idea, one sentence.
- The trade-off, admitted plainly.
- Build fact + evaluation anchor: what was built, measured against what, on what.
- The headline result with its cost attached.
Sentence 5 is the one first drafts omit and the one that most changes how a triage reviewer scores honesty. The worked example shows the skeleton filled in.
Revision passes, in order
- Arc pass — can a reader reconstruct pain → gap → idea → evidence from section openers alone?
- Objection pass — list the five likeliest reviewer objections; verify each is answered in the text, since no response period will exist to answer it later.
- Claim audit — every superlative gets a number; every number gets a baseline, a workload, and a cost.
- Compression pass — cut to the right length; hunt duplicated explanation, decorative figures, and throat-clearing openers.
- Cold read — a colleague outside the project reads pages 1–2 and states the contribution back; if they name the wrong idea, rewrite the front, not them.
Output format
[Arc] intact / broken at: <pain|gap|idea|design|build|eval>
[Named idea] <the one-sentence reusable claim, quoted from the draft>
[Padding risk] low / medium / high + worst offender section
[Unanswered objections] <list — each is a rebuttal you will never get to make>
[Page verdict] current length vs "right length" judgment
[Rewrite order] <ordered list of passes still needed>© 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 OSDI-Skills/skills/osdi-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Osdi 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 |
|---|---|---|---|---|---|---|
| Osdi Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
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 Osdi Writing Style
What does Osdi Writing Style do?
A skill your agent uses when drafting or revising an OSDI paper's prose and structure — building the pain → abstraction → mechanism → measurement narrative, fitting it into the 12-page reviewed body…. Osdi Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising an OSDI paper's prose and structure — building the pain → abstraction → mechanism → measurement narrative, fitting it into the 12-page reviewed body with no appendix escape hatch, and writing for a PC told to down-rank padded papers and given no rebuttal to clarify with.
When should I use Osdi Writing Style?
Osdi Writing Style fits situations like: revising an OSDI papers prose and structure — building the pain → abstraction → mechanism → measurement narrative; fitting it into the 12-page reviewed body with no appendix escape hatch; writing for a PC told to down-rank padded papers and given no rebuttal to clarify with.
How do I install Osdi Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-writing-style -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Osdi Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-writing-style -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-writing-style in your project. Codex loads it when a task matches its description.
Can I use Osdi 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 osdi-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/osdi-writing-style, .gemini/skills/osdi-writing-style, .github/skills/osdi-writing-style and .opencode/skills/osdi-writing-style in your project.
What does Osdi Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Osdi Writing Style is instructions for the agent only.
Does Osdi 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 Osdi 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 Osdi Writing Style use?
Osdi 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 Osdi Writing Style use?
About 1.6k tokens (SKILL.md is roughly 6.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 Osdi Writing Style?
Skills that share tags, products or a category with Osdi Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Osdi 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.