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 ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and…
Install Asplos Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-related-work .claude/skills/asplos-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 "asplos-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-related-work into .claude/skills/asplos-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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/ASPLOS-Skills/skills/asplos-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 asplos-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-related-work .agents/skills/asplos-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 "asplos-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-related-work into .agents/skills/asplos-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-related-work .cursor/skills/asplos-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 "asplos-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-related-work into .cursor/skills/asplos-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 ASPLOS-Skills/skills/asplos-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 asplos-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills asplos-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/ASPLOS-Skills/skills/asplos-related-work .gemini/skills/asplos-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 "asplos-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-related-work into .gemini/skills/asplos-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-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 asplos-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/ASPLOS-Skills/skills/asplos-related-work .github/skills/asplos-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 "asplos-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-related-work into .github/skills/asplos-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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 asplos-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 asplos-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/ASPLOS-Skills/skills/asplos-related-work .opencode/skills/asplos-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 "asplos-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ASPLOS-Skills/skills/asplos-related-work into .opencode/skills/asplos-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "asplos-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
asplos-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 805 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 ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and…
- Works in 4 steps: For each lane, list the 5-10 systems a… → Mark each entry: boundary-competitor… → Have the co-author closest to each… → …
- Positioning an ASPLOS submission against three communities literatures at once — covering the architecture
- SKILL.md covers The five lanes, Differentiate on the boundary,…, Double-blind handling of your… and Format constraints that…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Asplos Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and prior-ASPLOS lines, handling own-work and arXiv material under the 2027 double-blind rules, and meeting the full-name/DOI citation format.
Its SKILL.md is about 1.7k 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, Academic paper search and Positioning and messaging. 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 ASPLOS submission against three communities literatures at once — covering the architecture
- PL/compiler lanes plus accelerator and prior-ASPLOS lines
- Handling own-work and arXiv material under the 2027 double-blind rules
- Meeting the full-name/DOI citation format
Example prompts
- “/asplos-related-work”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- For each lane, list the 5-10 systems a reviewer from that community would
- Mark each entry: boundary-competitor (gets a template paragraph),
- Have the co-author closest to each community audit their lane's list — the
- Recheck the map at every gate: between April and September a spring
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
Asplos Related Work loads about 1.7k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 805 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). 805 words, ~1,720 tokens.
Download SKILL.mdSave it as
.claude/skills/asplos-related-work/SKILL.md (or your agent's skills folder).- name
- asplos-related-work
- description
- Use when positioning an ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and prior-ASPLOS lines, handling own-work and arXiv material under the 2027 double-blind rules, and meeting the full-name/DOI citation format.
ASPLOS Related Work
An ASPLOS reviewer pool is assembled from three communities, and each reviewer checks whether their literature is handled competently. Related work at this venue is therefore a coverage problem across parallel lanes — a paper positioned beautifully against the OS literature and blankly against the architecture literature reads as half-researched to half its reviewers.
The five lanes
| Lane | What must be shown | Failure the lane's reviewers spot |
|---|---|---|
| Architecture (ISCA/MICRO/HPCA lineage) | The hardware structure or mechanism is new relative to prior microarchitectural work | Reinvented prefetcher/hint/metadata scheme under a new name |
| OS/systems (SOSP/OSDI/EuroSys/ATC lineage) | The policy/runtime layer differs from existing kernel or hypervisor mechanisms | "The kernel already does this with tunables" |
| PL/compilers (PLDI/POPL/CGO lineage) | Language/compiler-level alternatives are acknowledged when the problem admits them | Hardware solution to a problem the compiler community solved statically |
| Accelerator/domain (when applicable) | Placement in the accelerator design space with honest technology normalization | Comparing against a three-generation-old design point |
| Prior ASPLOS | The intersection lineage itself — what earlier cross-layer attempts did | Missing the exact ASPLOS paper a PC member wrote or shepherded |
For the last lane, mine the venue's own memory: the ACM DL ASPLOS series and the
Influential Paper Award list (see ../../resources/exemplars/library.md) identify
the papers the community regards as canonical for a given boundary.
Differentiate on the boundary, not the components
The distinctive ASPLOS positioning move: prior work usually shares components with yours (a similar hardware structure, a similar kernel policy) while drawing the hardware/software boundary elsewhere. Say precisely where each prior system draws it and why yours moves it:
Template, per closest-prior system:
"<System> provides <capability> at <layer>, which requires <cost/assumption>.
Because it keeps <decision> in <layer>, it cannot <the thing your boundary
placement enables>. We move <decision> to <layer>, which is what makes
<headline property> possible."Three such paragraphs beat fifteen one-line dismissals — and the systems that get this treatment should be the ones a hostile reviewer would name.
Double-blind handling of your own line of work (2027 rules)
- Cite your prior published work in the third person, treated exactly like a competitor's system.
- Your own arXiv postings and tech reports are not prior publications under the 2027 CFP, and the submission may ignore them — you are not forced into contortions differentiating against your own preprint.
- A workshop paper this submission extends, or your related manuscript under review
elsewhere, goes in as anonymized supplemental material so reviewers can judge
the delta (mechanics in
asplos-supplementary). - Never use "removed for blind review" placeholders — disallowed wording.
Format constraints that reshape this section
ASPLOS's citation rules (verified 2026-07-08) have an underappreciated interaction
with related work: every entry needs all co-authors' full first and last names
and a DOI/link, which makes each citation long. Since references are outside the
11-page limit this costs no body pages — but it means bibliography hygiene is a
real task: budget an editing pass to expand names (asplos-submission has the
mechanical sweep) rather than discovering 90 malformed entries at the deadline.
Timing and staleness
- Sweep the most recent two editions of ASPLOS, ISCA, MICRO, SOSP/OSDI, and PLDI before each gate (the September 9, 2026 deadline follows a spring conference season — its output is your reviewers' freshest context).
- Concurrent work that appears between cycles: acknowledge it neutrally in a revision or camera-ready; a Major Revision's change note is an expected place to add "since submission" positioning.
Show full SKILL.md (292 more words)Show less
Building the lane map before writing
Construct the section from a spreadsheet, not from memory:
- For each lane, list the 5-10 systems a reviewer from that community would expect to see; source them from the last two editions' proceedings tables of contents (ACM DL for ASPLOS/ISCA/MICRO/SOSP; the respective sites for USENIX and SIGPLAN venues) rather than from citation chains, which propagate one group's blind spots.
- Mark each entry: boundary-competitor (gets a template paragraph), component-overlap (grouped sentence), or context (grouped citation).
- Have the co-author closest to each community audit their lane's list — the embarrassing omission is almost always in the lane nobody on the team calls home.
- Recheck the map at every gate: between April and September a spring conference season publishes, and a reviewer's own new paper is the citation they miss first.
Using the venue's own canon
The Influential Paper Award list is a positioning instrument, not just an
exemplar source: if your boundary has an award-validated ancestor (an
accelerator argued from data movement, a virtualization boundary redraw — see
../../resources/exemplars/library.md), citing the lineage and stating your
delta against it signals venue literacy to every senior reviewer. Conversely,
discovering that a canon paper already occupies your claimed boundary is
cheaper during this pass than in a review.
Where the section lives
With 11 figure-inclusive pages, a late monolithic related-work section is
expensive real estate. The pattern that survives compression: inline
differentiation at first mention for the two or three boundary-competitors
(they are part of the argument, not an appendix to it), plus a compact
lane-organized section that proves coverage. What must not be compressed away
is the boundary-competitor analysis — cutting it saves half a page and costs
the review that says "does not engage with <System>."
Output format
[Lane coverage] arch / OS / PL / accelerator / prior-ASPLOS — each: covered / thin / n-a
[Boundary paragraphs] closest-prior systems given the template treatment: list
[Hostile-reviewer test] the 3 systems a skeptic would name — all addressed? Y/N
[Own-work handling] third-person OK · supplements needed · arXiv stance decided
[Bibliography hygiene] full-name + DOI pass scheduled/done
[Staleness] newest cited edition per lane© 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 ASPLOS-Skills/skills/asplos-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Asplos 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 |
|---|---|---|---|---|---|---|
| Asplos Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | 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 Asplos Related Work
What does Asplos Related Work do?
A skill your agent uses when positioning an ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and…. Asplos Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and prior-ASPLOS lines, handling own-work and arXiv material under the 2027 double-blind rules, and meeting the full-name/DOI citation format.
When should I use Asplos Related Work?
Asplos Related Work fits situations like: positioning an ASPLOS submission against three communities literatures at once — covering the architecture; PL/compiler lanes plus accelerator and prior-ASPLOS lines; handling own-work and arXiv material under the 2027 double-blind rules; meeting the full-name/DOI citation format.
How do I install Asplos Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-related-work -a claude-code`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/asplos-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Asplos Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-related-work -a codex`. Or copy the skill folder (ASPLOS-Skills/skills/asplos-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/asplos-related-work in your project. Codex loads it when a task matches its description.
Can I use Asplos 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 asplos-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/asplos-related-work, .gemini/skills/asplos-related-work, .github/skills/asplos-related-work and .opencode/skills/asplos-related-work in your project.
What does Asplos Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Asplos Related Work is instructions for the agent only.
Does Asplos 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 Asplos 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 Asplos Related Work use?
Asplos 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 Asplos Related Work use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Asplos Related Work?
Skills that share tags, products or a category with Asplos 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 Asplos 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.