Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
A skill your agent uses when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access…
Install Osdi Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-related-work --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-related-work .claude/skills/osdi-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-related-work into .claude/skills/osdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-related-work --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-related-work .agents/skills/osdi-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-related-work into .agents/skills/osdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-related-work --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-related-work .cursor/skills/osdi-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-related-work into .cursor/skills/osdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills osdi-related-work --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-related-work .gemini/skills/osdi-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-related-work into .gemini/skills/osdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/osdi-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-related-work into .github/skills/osdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/osdi-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OSDI-Skills/skills/osdi-related-work into .opencode/skills/osdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "osdi-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 794 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access…
- Positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes
- SKILL.md covers What related work does at OSDI, The six lanes to sweep, USENIX open access is a… and Citing yourself under OSDI '26…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Verifying venues through USENIXs free open-access proceedings and dblp
What it does
Osdi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.
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 Literature review. It works with arXiv. 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
- Positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes
- Verifying venues through USENIXs free open-access proceedings and dblp
- Citing your own precursors without breaking the renamed-system anonymity rule
Example prompts
- “/osdi-related-work”
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 (its code samples are bash).
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 Related Work loads about 1.8k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 794 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). 794 words, ~1,772 tokens.
Download SKILL.mdSave it as
.claude/skills/osdi-related-work/SKILL.md (or your agent's skills folder).- name
- osdi-related-work
- description
- Use when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.
OSDI Related Work
Position the paper the way a systems PC checks it. The anonymity mechanics referenced here are OSDI '26 rules (verified 2026-07-08); the literature lanes are structural and change slowly, but the nearest-neighbor papers change every cycle.
What related work does at OSDI
An OSDI related-work section is not a survey; it is a difference ledger. For each neighboring system: what it does, what it cannot do that yours can, and why — at the mechanism level. Systems reviewers usually know the neighbors personally; they are not reading to learn the area but to test whether you know exactly where you sit.
The strongest form is one sentence of grouping plus one sentence of mechanism-level
difference per group, with the difference tied to your design's named idea (see
osdi-writing-style). "Unlike X, we are faster" is not a difference; "X orders its log
cluster-wide, so its recovery scope is the cluster; ours is the tenant" is.
The six lanes to sweep
| Lane | Where it lives | What reviewers check |
|---|---|---|
| Direct competitors | Recent OSDI/SOSP programs | Is the nearest published system compared head-on, in the evaluation and not only in prose? |
| The same problem, different layer | NSDI (network object), FAST (storage stack), EuroSys | Did you claim novelty for something solved one layer away? |
| The mechanism's ancestry | Classic OSDI/SOSP/ATC papers, possibly decades old | Is the lineage acknowledged? Systems memory is long — leases, logs, and schedulers all have ancestors |
| Production/industry reports | Operational-track papers, company engineering literature | Does deployed practice already do this quietly? |
| Concurrent work | arXiv, the venue cycle immediately before yours | Handled generously — parallel invention is normal in a two-flagship annual cadence |
| Your own precursors | Your arXiv/tech reports/talks | Cited without deanonymizing (rules below) |
USENIX open access is a verification tool
Every OSDI paper — and every NSDI, FAST, and (historical) ATC paper — is a free PDF
on usenix.org, available to everyone from the day its event began. Consequences:
- There is no excuse for citing a systems paper from its abstract. Download and check the claim you attribute; misdescribing a neighbor's mechanism is the fastest way to lose a reviewer who built it.
- Venue attribution is checkable in seconds and must be exact. The systems canon
scatters confusingly (GFS is SOSP, Raft is ATC, Firecracker is NSDI — see the trap
list in
../../resources/exemplars/library.md); verify ondblp.org/db/conf/osdi/before writing "at OSDI." - SOSP-side papers live in the ACM DL rather than usenix.org; verify those through dblp plus the SIGOPS pages.
# Venue sanity pass over the bibliography (run before the anonymity sweep)
grep -nEi 'booktitle.*(OSDI|SOSP|NSDI|FAST|EuroSys|ATC|Annual Technical)' refs.bib |
sort | uniq -c | sort -rn
# For each OSDI-attributed entry: confirm a conf/osdi/ dblp key exists.
# For each ATC entry dated 2026+: USENIX ATC ended after ATC '25 — recheck the
# actual venue (successor is stewarded by ACM SIGOPS).Citing yourself under OSDI '26 anonymity
OSDI '26 allowed prior non-peer-reviewed exposure — arXiv, tech reports, talks, social media — but with a sharp condition: the submission must use an anonymized system name different from any used in those contexts. Operational rules:
- Cite your precursor in the third person, as if it were someone else's system, under its public name; your submission's system carries its new name.
- Never write "we extend our earlier work"; the sentence itself is the leak.
- Sweep for indirect leaks: repository URLs in footnotes, trace names that appear only
in your group's papers, acknowledgment stubs,
\citekeys visible in comments. - Do not omit the precursor entirely if it is publicly findable — omission plus a renamed system reads worse in shepherding than a clean third-person citation.
Show full SKILL.md (265 more words)Show less
Difference-ledger template
Draft the section as a ledger before writing prose; prose written first hides the gaps the ledger exposes:
related-work-ledger.md (one row per neighbor; groups become paragraphs)
neighbor | venue+yr | its mechanism | why ours differs (mechanism level) | in eval?
ReplayFS | OSDI 'xx | cluster-wide log | recovery scope = cluster, ours = tenant | yes (fig 7)
CkptStore | SOSP 'xx | boundary checkpoints | moves the stall, doesn't bound it | yes (fig 7)
LeaseKV | NSDI 'xx | per-key leases | network object, no crash-adoption path | prose only
<1990s ancestor>| SOSP '9x | leases (original) | we inherit; delta = epoch-bump adoption | n/aRules the ledger enforces: every row's difference is a mechanism, not an adjective; any row marked "prose only" whose mechanism competes head-on is an evaluation gap to fix or explicitly justify; and the ancestry row is mandatory — writing it is how era-blindness gets caught before a PC member catches it for you.
Failure patterns PCs flag
- The missing obvious neighbor — the one paper everyone on the PC thinks of within ten seconds, absent from the ledger. Fatal in a no-rebuttal cycle: nobody can ask "did you know about X?", they just score.
- Citation without comparison — the nearest system cited in Section 2 but absent
from the evaluation table (
osdi-experimentsowns the fix). - Era-blindness — treating a 2020s reinvention as novel over a 1990s mechanism; OSDI PCs contain people who wrote the 1990s paper.
- Wrong-venue attributions — individually small, collectively a credibility tax.
Neighbors that exist only on arXiv
Systems work increasingly surfaces as arXiv-only preprints months before any PC sees it. Handle by class: a preprint clearly targeting the same cycle is concurrent work — cite it, note the concurrency, and do not let reviewers discover it for you; an older unreviewed preprint with real adoption is engaged on its technical content (reviewers will know it); and an abandoned preprint may still claim the idea's name, in which case position by mechanism, not by name. In all three cases the citation is dated — arXiv versions move, and "vN, month year" pins what you actually compared against.
Output format
[Ledger status] complete / gaps in lanes: <list of the six lanes>
[Nearest neighbor] <system, venue, year> — compared in eval? yes/no
[Mechanism differences] <top 3, each one sentence, tied to the named idea>
[Self-citation audit] precursors renamed + third-person? leaks found: <list>
[Venue attributions] verified via dblp/usenix.org? unverified count: <n>© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Osdi Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Paper Research on arXivXiaomiMiMo/MiMo-Code | 14k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Literature Review AgentAr9av/PaperOrchestra | 679 | 1 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Arxiv MCP Serverblazickjp/arxiv-mcp-server | 3.2k | — | ~353 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Systematic Literature Review Builder
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
Paper Research on arXiv
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
Literature Review Agent
Ar9av/PaperOrchestra
Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.
Arxiv MCP Server
blazickjp/arxiv-mcp-server
A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…
Arxiv Paper Writer
appautomaton/latex-arxiv-SKILL
Write LaTeX ML/AI review articles for arXiv using the IEEEtran template and verified BibTeX citations.
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
Works with
Categories
Questions about Osdi Related Work
What does Osdi Related Work do?
A skill your agent uses when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access…. Osdi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.
When should I use Osdi Related Work?
Osdi Related Work fits situations like: positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes; verifying venues through USENIXs free open-access proceedings and dblp; citing your own precursors without breaking the renamed-system anonymity rule.
How do I install Osdi Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-related-work -a claude-code`. Or copy the skill folder (OSDI-Skills/skills/osdi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/osdi-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Osdi Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-related-work -a codex`. Or copy the skill folder (OSDI-Skills/skills/osdi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/osdi-related-work in your project. Codex loads it when a task matches its description.
Can I use Osdi Related Work 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-related-work -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-related-work, .gemini/skills/osdi-related-work, .github/skills/osdi-related-work and .opencode/skills/osdi-related-work in your project.
What does Osdi Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Osdi Related Work is instructions for the agent only.
Does Osdi Related Work 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 Related Work 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 Related Work use?
Osdi Related Work 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 Related Work 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 Osdi Related Work?
Skills that share tags, products or a category with Osdi Related Work: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars), Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars) and Literature Review Agent (Ar9av/PaperOrchestra, 679 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Osdi Related Work?
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.