osdi-writing-style
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: 1. **Pain** — something operational breaks, stalls, or costs money, and the trend makes it worse. Not "X is important." 2. **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. 3. **The idea, named** — one abstraction, principle, or mechanism another builder could reuse, stated in a sentence a reviewer could repeat in the PC meeting. 4. **The design that realizes it** — decisions justified against the idea, with the trade-offs admitted where they are made, not in a limitations afterthought. 5. **The system that exists** — implementation reality: lines, language, what is real versus mocked. 6. **Measurements that answe
- The narrative arc
- Writing under the 12-page regime
- Sentence-level habits of accepted systems prose
- Mechanical format anchors (2026 cycle)
- The abstract in seven sentences
- Revision passes, in order
- Output format
What does the osdi-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.