Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
A skill your agent uses when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles…
Install Pldi Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-related-work .claude/skills/pldi-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 "pldi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-related-work into .claude/skills/pldi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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/PLDI-Skills/skills/pldi-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 pldi-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-related-work .agents/skills/pldi-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 "pldi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-related-work into .agents/skills/pldi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 pldi-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-related-work .cursor/skills/pldi-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 "pldi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-related-work into .cursor/skills/pldi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 PLDI-Skills/skills/pldi-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 pldi-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-related-work .gemini/skills/pldi-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 "pldi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-related-work into .gemini/skills/pldi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 pldi-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 pldi-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/PLDI-Skills/skills/pldi-related-work .github/skills/pldi-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 "pldi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-related-work into .github/skills/pldi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 pldi-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 pldi-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/PLDI-Skills/skills/pldi-related-work .opencode/skills/pldi-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 "pldi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-related-work into .opencode/skills/pldi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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
pldi-related-work- GitHub stars
- 1.2k
- Token cost
- ~947 tokens
- SKILL.md length
- 391 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 PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles…
- Positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line
- SKILL.md covers The delta discipline, Coverage map, Cite the PACMPL era correctly and Verification before submission, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the last few PLDI/POPL/OOPSLA/ICFP cycles
What it does
Pldi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.
Its SKILL.md is about 950 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. 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 PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line
- Covering the last few PLDI/POPL/OOPSLA/ICFP cycles
- Citing PACMPL-era papers in journal form
- Verifying every venue attribution on dblp before it ships
Example prompts
- “/pldi-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 bibtex).
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
Pldi Related Work loads about 947 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 391 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). 391 words, ~947 tokens.
Download SKILL.mdSave it as
.claude/skills/pldi-related-work/SKILL.md (or your agent's skills folder).- name
- pldi-related-work
- description
- Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.
PLDI Related Work
At PLDI, related work is an adversarial exercise: your reviewers are frequently the authors of your closest baselines. The section must therefore do two things — prove you know the landscape's mechanisms (not just its citations), and state, line by line, what this paper does that each prior technique cannot.
The delta discipline
Ban survey sentences ("Much work has studied pointer analysis [3,7,12,19]"). Every citation earns its place with a mechanism and a delta:
Steensgaard-style unification [7] scales linearly but merges all callees' effects; our signatures keep callee effects separate at equal asymptotic cost (§4.3).
If you cannot write the delta clause, you have not read the paper closely enough to cite it at PLDI — where the cited author may be reviewer B.
Coverage map
| Neighbor | What to check there | Typical relationship to a PLDI paper |
|---|---|---|
| PLDI, last ~4 cycles | The direct competition; reviewers expect these compared, not just cited | Baseline or head-to-head |
| POPL | The semantic foundations your system builds on | "We implement/scale what [x] formalized" |
| OOPSLA | Language design, empirical SE-flavored PL studies | Alternative evidence styles for similar claims |
| ICFP | Functional-language techniques, typed IRs | Technique transfer across paradigms |
| ASPLOS / CGO / PPoPP | Architecture-facing compilation and parallelism | Same optimization, different evidence bar |
| CAV / TACAS | Verification engines and solvers | Your backend or your competitor's |
| ICSE / FSE | Testing and analysis at software-engineering scale | Scale claims to compare honestly |
Since POPL, OOPSLA, ICFP, and PLDI all publish in PACMPL, "recent PACMPL papers" is a single searchable stream — sweep it by issue name so a POPL 2025 article does not get labeled PLDI 2025 in your bibliography.
Show full SKILL.md (128 more words)Show less
Cite the PACMPL era correctly
PLDI 2023 and later papers are journal articles, not proceedings entries:
@article{gopinathan2023proofrepair,
author = {Gopinathan, Kiran and Keoliya, Mayank and Sergey, Ilya},
title = {Mostly Automated Proof Repair for Verified Libraries},
journal = {Proc. ACM Program. Lang.},
volume = {7},
number = {PLDI},
articleno = {107},
year = {2023},
doi = {10.1145/3591221}
}Pre-2023 PLDI papers keep @inproceedings form with page ranges. Mixing the two
conventions — or citing a PACMPL article as "In PLDI '23, pp. ..." — is the most
common bibliography error since the switch, and PL reviewers notice.
Verification before submission
- Confirm every venue attribution on dblp; the classics are the traps (LLVM is
CGO 2004, CompCert's certification paper is POPL 2006, RustBelt is PACMPL
Issue POPL — see
resources/exemplars/library.mdfor the curated list). - For arXiv-only concurrent work, cite it as a preprint and position gently; it is context, not an archival obligation.
- Double-blind interacts here: your own prior papers appear in third person, cited normally — omitting them is itself an identity signal.
Output format
[Delta audit] citations without a delta clause: <list>
[Coverage] PLDI recent cycles / POPL / OOPSLA / ICFP / systems neighbors — gaps?
[Head-to-head] which cited techniques appear in the evaluation as baselines?
[Bibliography form] PACMPL-era entries in journal form? venues dblp-verified?
[Anonymity] self-citations third person, none omitted?© 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 PLDI-Skills/skills/pldi-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pldi 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 |
|---|---|---|---|---|---|---|
| Pldi Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~947 | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| 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 | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence |
Similar skills
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.
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim 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
Categories
Questions about Pldi Related Work
What does Pldi Related Work do?
A skill your agent uses when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles…. Pldi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the last few PLDI/POPL/OOPSLA/ICFP cycles, citing PACMPL-era papers in journal form, and verifying every venue attribution on dblp before it ships.
When should I use Pldi Related Work?
Pldi Related Work fits situations like: positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line; covering the last few PLDI/POPL/OOPSLA/ICFP cycles; citing PACMPL-era papers in journal form; verifying every venue attribution on dblp before it ships.
How do I install Pldi Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-related-work -a claude-code`. Or copy the skill folder (PLDI-Skills/skills/pldi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pldi-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Pldi Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-related-work -a codex`. Or copy the skill folder (PLDI-Skills/skills/pldi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pldi-related-work in your project. Codex loads it when a task matches its description.
Can I use Pldi 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 pldi-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/pldi-related-work, .gemini/skills/pldi-related-work, .github/skills/pldi-related-work and .opencode/skills/pldi-related-work in your project.
What does Pldi Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Pldi Related Work is instructions for the agent only.
Does Pldi 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 Pldi 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 Pldi Related Work use?
Pldi 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 Pldi Related Work use?
About 947 tokens (SKILL.md is roughly 3.8k 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 Pldi Related Work?
Skills that share tags, products or a category with Pldi Related Work: Nature Paper Card (Yuan1z0825/nature-skills, 47k stars), Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars) and Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pldi 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.