Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing…
Install Sosp Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-related-work .claude/skills/sosp-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 "sosp-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-related-work into .claude/skills/sosp-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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/SOSP-Skills/skills/sosp-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 sosp-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-related-work .agents/skills/sosp-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 "sosp-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-related-work into .agents/skills/sosp-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-related-work .cursor/skills/sosp-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 "sosp-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-related-work into .cursor/skills/sosp-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 SOSP-Skills/skills/sosp-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 sosp-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-related-work .gemini/skills/sosp-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 "sosp-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-related-work into .gemini/skills/sosp-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-related-work .github/skills/sosp-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 "sosp-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-related-work into .github/skills/sosp-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-related-work .opencode/skills/sosp-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 "sosp-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-related-work into .opencode/skills/sosp-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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
sosp-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 606 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing…
- Works in 2 steps: Ancestry pass: walk the problem back… → Recency pass: both SOSP and OSDI have…
- Positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know
- SKILL.md covers Know the lineage or be…, Compare structures, not…, Double-blind mechanics in the… and Concurrent work across an…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sosp Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing, third-person self-citation under double-blind rules, and handling concurrent work across the now-annual systems deadline circuit.
Its SKILL.md is about 1.3k 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, Citation management and Positioning and messaging. 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 a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know
- Structural comparison instead of citation listing
- Third-person self-citation under double-blind rules
- Handling concurrent work across the now-annual systems deadline circuit
Example prompts
- “/sosp-related-work”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Ancestry pass: walk the problem back through prior SOSP/OSDI editions via
- Recency pass: both SOSP and OSDI have run annually since 2024, so the "last
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
Sosp Related Work loads about 1.3k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 606 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). 606 words, ~1,318 tokens.
Download SKILL.mdSave it as
.claude/skills/sosp-related-work/SKILL.md (or your agent's skills folder).- name
- sosp-related-work
- description
- Use when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing, third-person self-citation under double-blind rules, and handling concurrent work across the now-annual systems deadline circuit.
SOSP Related Work
Use this when writing or auditing the related-work section of a SOSP paper. At this venue the section is a load-bearing wall: the PC contains authors of the systems you must compare against, the meeting will replay any positioning gap out loud, and the "how does this differ from X" review is the most common avoidable negative. Rules below reflect the 2026-cycle CFP's double-blind policy (checked 2026-07-08).
Know the lineage or be corrected in public
A SOSP reviewer expects the paper to place itself in the SOSP/OSDI line of work on its problem — often decades deep — plus the adjacent venues where the problem also lives (EuroSys, USENIX ATC, NSDI for networked systems, FAST for storage, ASPLOS at the architecture boundary). Two search passes are mandatory before the freeze:
- Ancestry pass: walk the problem back through prior SOSP/OSDI editions via
dl.acm.org/conference/sosp, dblp, and the SIGOPS Hall of Fame list (sigops.org/awards/hof/) — a HoF paper on your problem uncited is a credibility wound out of proportion to its citation value. - Recency pass: both SOSP and OSDI have run annually since 2024, so the "last edition" is now at most a year old, and the paper most likely to sink yours appeared months ago. Sweep the two most recent programs of each sibling venue.
Compare structures, not abstracts
Listing citations with one-line summaries is a survey; SOSP wants positioning — for each nearest neighbor, the axis on which your design differs and why that axis matters for the paper's claims:
| Comparison axis | Positioning sentence shape | Weak version it replaces |
|---|---|---|
| Assumption | "X assumes a trusted hypervisor; Foo removes that trust and pays for it in §5.3" | "X is a related virtualization system" |
| Mechanism | "Both log; X logs operations, Foo logs allocation intents, which is what makes recovery size-independent" | "Unlike X, we use a different log format" |
| Guarantee | "X provides per-object linearizability; Foo's per-session guarantee is weaker and §2 argues sufficient" | "Foo has better consistency" |
| Evidence | "X evaluates on synthetic skew; the trace-driven results in §6 cover the regime X excludes" | "X's evaluation is limited" |
Comparisons that end in a section pointer are meeting-proof: an advocate can answer "how is this different from X" by reading your sentence aloud.
Show full SKILL.md (239 more words)Show less
Double-blind mechanics in the citations
- Cite your own prior work in third person, normally, as if written by others. Omitting a needed self-citation is worse anonymization than citing it neutrally.
- The unpublishable case — the submission directly extends your identifiable tech report or workshop paper — is the one place to consult the current CFP's precise language rather than improvise (待核实 per cycle whether anonymized citation or chair consultation is prescribed).
- Acknowledgment-style credits ("thanks to the Bar team for traces") leak identity; hold them for the camera-ready.
Concurrent work across an annual circuit
With SOSP and OSDI both annual and EuroSys/ATC/NSDI in between, "concurrent" now means a sliding window of months:
- Work published after your submission freeze is genuinely concurrent; note it
gracefully in the response if reviewers raise it, and integrate it at
camera-ready with the shepherd's blessing (see
sosp-camera-ready). - An arXiv preprint of a competing system is citable context; treat it as unrefereed and compare against its claims cautiously and visibly.
- Do not silently ignore a known concurrent system hoping reviewers missed it — at this PC, someone reviewed it.
Related-work matrix (build before writing the section)
assumption mechanism guarantee evidence regime
Foo (ours) <...> <...> <...> <...>
X [SOSP'24] same op logging stronger synthetic only
Y [OSDI'25] weaker: <..> similar: <..> same no failure runs
Z [arXiv'26] unclear (unrefereed) ...
-> nearest neighbor: X; the axis that matters: recovery cost vs log size (§6.2)Placement and length
Three-quarters of a page is typical (see sosp-writing-style's budget). Early
placement (after the intro) suits papers whose contribution is best seen against a
specific prior design; end placement suits papers whose design needs absorbing
first. Either way, the intro must already name the nearest neighbor — burying the
closest competitor until page 11 reads as evasion.
Output format
[Lineage audit] HoF / SOSP / OSDI ancestors cited? gaps: <list>
[Recency sweep] last two editions of SOSP, OSDI, EuroSys, ATC checked? finds: <list>
[Matrix] nearest neighbor + decisive axis + section pointer
[Blind check] self-citations third person? credits deferred?
[Concurrent] known unpublished competitors + handling plan© 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 SOSP-Skills/skills/sosp-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sosp 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 |
|---|---|---|---|---|---|---|
| Sosp Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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 Sosp Related Work
What does Sosp Related Work do?
A skill your agent uses when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing…. Sosp Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing, third-person self-citation under double-blind rules, and handling concurrent work across the now-annual systems deadline circuit.
When should I use Sosp Related Work?
Sosp Related Work fits situations like: positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know; structural comparison instead of citation listing; third-person self-citation under double-blind rules; handling concurrent work across the now-annual systems deadline circuit.
How do I install Sosp Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-related-work -a claude-code`. Or copy the skill folder (SOSP-Skills/skills/sosp-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sosp-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Sosp Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-related-work -a codex`. Or copy the skill folder (SOSP-Skills/skills/sosp-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sosp-related-work in your project. Codex loads it when a task matches its description.
Can I use Sosp 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 sosp-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/sosp-related-work, .gemini/skills/sosp-related-work, .github/skills/sosp-related-work and .opencode/skills/sosp-related-work in your project.
What does Sosp Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Sosp Related Work is instructions for the agent only.
Does Sosp 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 Sosp 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 Sosp Related Work use?
Sosp 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 Sosp Related Work use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Sosp Related Work?
Skills that share tags, products or a category with Sosp Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sosp 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.