Agent skill

Osdi Supplementary

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

MITAuto-check passed

Install Osdi Supplementary

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-supplementary --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-supplementary .claude/skills/osdi-supplementary && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "osdi-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-supplementary into .claude/skills/osdi-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-supplementary", 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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-supplementary

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-supplementary --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .agents/skills/osdi-supplementary && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "osdi-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-supplementary into .agents/skills/osdi-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-supplementary", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-supplementary --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .cursor/skills/osdi-supplementary && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "osdi-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-supplementary into .cursor/skills/osdi-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-supplementary", 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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path OSDI-Skills/skills/osdi-supplementary

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-supplementary --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .gemini/skills/osdi-supplementary && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "osdi-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-supplementary into .gemini/skills/osdi-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-supplementary", 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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-supplementary

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-supplementary .github/skills/osdi-supplementary && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "osdi-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-supplementary into .github/skills/osdi-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-supplementary", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-supplementary --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-supplementary .opencode/skills/osdi-supplementary && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "osdi-supplementary" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-supplementary into .opencode/skills/osdi-supplementary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-supplementary", 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-supplementary
GitHub stars: 1.2k
Token cost: ~1.6k tokens
SKILL.md length: 660 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body
SKILL.md covers The three destinations, Living without an appendix at…, Planning the June expansion in… and Triage decision flow, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
The 14-page-plus-appendices final paper

What it does

Osdi Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body, the 14-page-plus-appendices final paper, and the public artifact, since OSDI (unlike appendix-friendly venues) reviews nothing outside the body.

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.

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

Deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body
The 14-page-plus-appendices final paper
The public artifact
Since OSDI (unlike appendix-friendly venues) reviews nothing outside the body

Example prompts

“/osdi-supplementary”

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 Supplementary loads about 1.6k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 660 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~75
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

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). 660 words, ~1,606 tokens.

Download SKILL.mdSave it as .claude/skills/osdi-supplementary/SKILL.md (or your agent's skills folder).

name: osdi-supplementary
description: Use when deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body, the 14-page-plus-appendices final paper, and the public artifact, since OSDI (unlike appendix-friendly venues) reviews nothing outside the body.

OSDI Supplementary Material

OSDI inverts the supplement habit most authors bring from ML and ACM venues. Rules below are the OSDI '26 cycle (verified 2026-07-08): submissions get 12 pages plus unlimited references and nothing else — the CFP permits extra pages for references "but not for supplementary material in appendices." There is no supplement upload, no appendix, no ZIP. Accepted papers later expand to 14 pages plus references and appendices, plus an optional two-page Artifact Appendix for papers passing artifact evaluation.

The three destinations

Every piece of material has exactly one correct home:

Destination	What belongs there	When it exists
12-page reviewed body	Everything a reviewer needs to judge correctness and significance	Submission (December)
Final-paper appendix (post-acceptance)	Depth for readers: full protocol details, extended results, proofs written out, the Artifact Appendix	Final papers (June)
Public artifact	Code, traces, configurations, raw data, runbooks	Archived by the May artifact deadline

The triage question for any candidate paragraph, proof, table, or figure: "Does a skeptical reviewer need this to accept the paper?" Yes → it earns body space, and something weaker must leave to make room. No → it waits for the final-paper appendix or the artifact, and the body carries a one-line summary of what exists.

Living without an appendix at submission

Techniques for material that would be an appendix elsewhere:

Proofs and invariants — state the invariant and the proof's one load-bearing step in the body ("safety follows because a lease transfer requires quorum acknowledgment of the epoch bump"); the full proof is final-paper appendix material. If the paper is unacceptable without the full formal argument, OSDI's format is telling you something about venue fit (osdi-topic-selection).
Extended result grids — the body shows the RQ-answering figure; the sweep across every configuration goes to the artifact as data plus plotting scripts, referenced in one sentence without a link that breaks anonymity.
Protocol/config detail — compress into a table; systems reviewers extract more from a dense parameter table than from two pages of prose.
Never point to an external URL as a de facto appendix. An anonymous link carrying material the paper depends on violates the spirit of the rule reviewers enforce, and any non-anonymous link is a double-blind breach (osdi-submission).

Show full SKILL.md (298 more words)Show less

Planning the June expansion in December

Write the submission with a marked expansion plan so the accepted version is an unfolding, not a rewrite:

text

% submission-time annotations, kept in comments in the source
% [FINAL-14pp] restore lease-protocol failure cases cut from §4.2
% [FINAL-APPENDIX-A] full safety proof (draft in proofs/safety.tex)
% [FINAL-APPENDIX-B] full workload sweep grid (artifact: plots/sweep/)
% [ARTIFACT-APPENDIX] runbook skeleton -> becomes the 2-page AE appendix
% rule: nothing in FINAL-* may be load-bearing for acceptance

The rule in the last comment is the audit: if any FINAL-* item is something a reviewer would have needed, it must be promoted into the body now — after acceptance is too late to have convinced anyone, and OSDI '26 offered no response period in which to supply missing material on request.

Triage decision flow

Run each candidate item through this flow when the draft first crosses 12 pages — not on deadline night:

text

item: proof / table / protocol detail / extra experiment / config dump
  |
  needed by a skeptical reviewer to ACCEPT? --yes--> body (cut something weaker;
  |                                                  osdi-writing-style compression
  no                                                 pass runs first)
  |
  needed by a READER or REPRODUCER later? --yes--> is it prose/math?
  |                                                  yes -> final-paper appendix
  no                                                 no (code/data/runs)
  |                                                       -> artifact
  cut entirely (deadline-week sunk cost is not a reason to keep it)

Two calibration notes: reviewers differ, so when genuinely unsure whether an item is acceptance-critical, it goes in the body — the no-response process gives no chance to supply it on request; and the body must summarize every deferred item in one sentence ("the full sweep, 240 configurations, accompanies the artifact"), because an unmentioned deferral is indistinguishable from a gap.

The Artifact Appendix (the one supplement OSDI formalizes)

For papers that pass artifact evaluation, the final paper may add up to two pages documenting the artifact in a standard format: what the artifact contains, hardware and software requirements, how to reproduce which claims. Treat it as the public, citable interface to the artifact — written from the runbook the AE committee already exercised (osdi-artifact-evaluation), not composed fresh in June.

Triage failure modes

Submitting a paper that silently assumes appendix space exists — discovered at page 13, two days before the deadline.
Cutting load-bearing evidence to fit, instead of cutting redundancy (osdi-writing-style's compression pass comes first).
An external "anonymous supplement" link standing in for the forbidden appendix.
Deferring so much to the final version that reviewers correctly judge the submission incomplete — conditional acceptance mandates fixes, but only for papers strong enough to conditionally accept.

Output format

text

[No-appendix compliance] submission = body + refs only? violations: <list>
[Triage table] each deferred item -> destination (final-appendix / artifact) + body summary line present?
[Load-bearing audit] any FINAL-* item a reviewer actually needs? <list or none>
[External links] none that carry evidence / none that break anonymity? yes/no
[June plan] expansion annotations in source? artifact-appendix runbook started?

Files

Just SKILL.md in OSDI-Skills/skills/osdi-supplementary of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Osdi Supplementary 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.

Osdi Supplementary compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Osdi Supplementary this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.6k	Automated safety check: Pass	MIT	14 days ago
Live DashboardNousResearch/hermes-agent	252k	—	~2.1k	Automated safety check: Pass	MIT	yesterday
Openclaw Live Updateropenclaw/openclaw	392k	—	~3.7k	Automated safety check: Pass	MIT	today
Live Dashboardnexu-io/open-design	100k	—	~2.1k	Automated safety check: Pass	Apache-2.0	yesterday
Living Docs Governanceaffaan-m/ECC	277k	1 repos	~2.1k	Automated safety check: Pass	MIT	today
Team Live OpsDonchitos/Claude-Code-Game-Studios	26k	—	~4.2k	Automated safety check: Notes	MIT	3 days ago

Similar skills

Live Dashboard
NousResearch/hermes-agent
Build self-updating dashboards from live sources. An agent skill from NousResearch/hermes-agent.
252k GitHub stars~2.1k tokensUpdated yesterday
Auto-check passed
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
392k GitHub stars~3.7k tokensUpdated today
DevOps & CloudAuto-check passed
Live Dashboard
nexu-io/open-design
Notion-style team dashboard rendered as a Live Artifact. An agent skill from nexu-io/open-design.
100k GitHub stars~2.1k tokensUpdated yesterday
Productivity & AutomationAuto-check passed
Living Docs Governance
affaan-m/ECC
Keep a long-lived project's documentation from rotting by assigning existing project docs clear constitution, map, status, and history roles, then wiring the active agent harness to those canonical…
277k GitHub starsUsed in 1 repo~2.1k tokens
DevelopmentAuto-check passed
Team Live Ops
Donchitos/Claude-Code-Game-Studios
Orchestrate the live-ops team — live-ops-designer, economy-designer, analytics-engineer, community-manager, writer — for a season or live event.
26k GitHub stars~4.2k tokensUpdated 3 days ago
Game DevelopmentAuto-check: notes
Aria Live Regions
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Announce dynamic content with ARIA live regions.
74k GitHub stars~478 tokensUpdated 4 days ago
Frontend & DesignAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 14 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 14 days ago
Auto-check passed

Questions about Osdi Supplementary

What does Osdi Supplementary do?

A skill your agent uses when deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body, the 14-page-plus-appendices final paper…. Osdi Supplementary is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body, the 14-page-plus-appendices final paper, and the public artifact, since OSDI (unlike appendix-friendly venues) reviews nothing outside the body.

When should I use Osdi Supplementary?

Osdi Supplementary fits situations like: deciding where OSDI content lives given the no-appendix submission rule — triaging material between the 12-page reviewed body; the 14-page-plus-appendices final paper; the public artifact; since OSDI (unlike appendix-friendly venues) reviews nothing outside the body.

How do I install Osdi Supplementary in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-supplementary in your project. Claude Code loads it when a task matches its description.

How do I install Osdi Supplementary in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-supplementary -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-supplementary in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-supplementary in your project. Codex loads it when a task matches its description.

Can I use Osdi Supplementary 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-supplementary -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-supplementary, .gemini/skills/osdi-supplementary, .github/skills/osdi-supplementary and .opencode/skills/osdi-supplementary in your project.

What does Osdi Supplementary need to run?

SKILL.md names no scripts, command-line tools or credentials: Osdi Supplementary is instructions for the agent only.

Does Osdi Supplementary 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 Supplementary 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 Supplementary use?

Osdi Supplementary 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 Supplementary 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 Supplementary?

Skills that share tags, products or a category with Osdi Supplementary: Live Dashboard (NousResearch/hermes-agent, 252k stars), Openclaw Live Updater (openclaw/openclaw, 392k stars), Live Dashboard (nexu-io/open-design, 100k stars) and Living Docs Governance (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Osdi Supplementary?

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.

Install Osdi Supplementary

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

OSDI Supplementary Material

The three destinations

Living without an appendix at submission

Planning the June expansion in December

Triage decision flow

The Artifact Appendix (the one supplement OSDI formalizes)

Triage failure modes

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Osdi Supplementary