Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
A skill your agent uses when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or…
MITAuto-check passed
Install Pldi Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-topic-selection --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-topic-selection .claude/skills/pldi-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-topic-selection into .claude/skills/pldi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-topic-selection", 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-topic-selectionType 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-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-topic-selection --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-topic-selection .agents/skills/pldi-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-topic-selection into .agents/skills/pldi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-topic-selection", 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-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-topic-selection --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-topic-selection .cursor/skills/pldi-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-topic-selection into .cursor/skills/pldi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-topic-selection", 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-topic-selection--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-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-topic-selection --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-topic-selection .gemini/skills/pldi-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-topic-selection into .gemini/skills/pldi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-topic-selection", 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-topic-selectionInstalls 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-topic-selection -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-topic-selection .github/skills/pldi-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-topic-selection into .github/skills/pldi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-topic-selection", 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-topic-selection -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-topic-selection --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-topic-selection .opencode/skills/pldi-topic-selection && 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-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-topic-selection into .opencode/skills/pldi-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-topic-selection", 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-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 400 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or…
- Works in 3 steps: Where does the claim's proof live? In a… → Who must be convinced? People who build… → Would the paper survive with the…
- Deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence —
- SKILL.md covers The fit test, Routing table, PLDI-shaped in practice and Decision procedure, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pldi Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the claim's evidence actually lives.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence —
- Better routed inside the PACMPL family to POPL
- Outward to ASPLOS
- A systems venue
Example prompts
- “/pldi-topic-selection”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Where does the claim's proof live? In a theorem about a calculus → POPL
- Who must be convinced? People who build compilers and analyzers → PLDI.
- Would the paper survive with the implementation deleted? If yes, the
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
Pldi Topic Selection loads about 1.1k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 400 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). 400 words, ~1,070 tokens.
Download SKILL.mdSave it as
.claude/skills/pldi-topic-selection/SKILL.md (or your agent's skills folder).- name
- pldi-topic-selection
- description
- Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the claim's evidence actually lives.
PLDI Topic Selection
PLDI's scope statement is broad — all aspects of programming language research: design, implementation, theory, applications, performance (PLDI 2026 CFP) — but its acceptance bar has a recognizable shape: an idea about languages, compilers, analyses, runtimes, or verification tooling whose truth is demonstrated by a working implementation evaluated on convincing programs. The routing question is never "is this PL?"; it is "is the decisive evidence an implementation-and-benchmarks story?"
The fit test
Answer three questions honestly:
- Where does the claim's proof live? In a theorem about a calculus → POPL lens. In measurements of a built system → PLDI lens. In how developers experience the language → OOPSLA lens.
- Who must be convinced? People who build compilers and analyzers → PLDI. People who prove type soundness → POPL. People who study software at scale → ICSE/FSE.
- Would the paper survive with the implementation deleted? If yes, the implementation is decoration and PLDI reviewers will say so.
Routing table
| Signal in your project | Better home | Why |
|---|---|---|
| The theorem is the contribution; implementation is a demo | POPL | Semantics-first reviewing |
| Language design + experience/empirical study of use | OOPSLA | Broader evidence styles welcomed |
| Functional-programming technique, typed abstractions | ICFP | Paradigm-native audience |
| Wins depend on hardware features or memory hierarchy | ASPLOS / CGO / PPoPP | Architecture-facing evidence bar |
| The engine is a solver/model checker advance | CAV / TACAS | Verification-algorithms community |
| Claim is about developer behavior or SE process | ICSE / FSE | Human/process evidence expected |
| OS-level mechanism, scheduler, distributed runtime | OSDI / SOSP | Systems reviewing |
| Early idea, no evaluation yet | SIGPLAN workshops (co-located each June) | Feedback without the archival bar |
Show full SKILL.md (146 more words)Show less
Note the family plumbing: POPL, OOPSLA, ICFP, and (since 2023) PLDI all publish in PACMPL, so the choice among them changes reviewers and deadlines, not the journal your paper lands in. Retargeting within the family is cheap editorially — the CFP formats are all acmart — but expensive intellectually if the evidence style does not move with it.
PLDI-shaped in practice
The venue-verified exemplars in resources/exemplars/library.md triangulate the
bar: an automated testing engine on real C code (DART), instrumentation
infrastructure with its design space articulated (Valgrind), a multi-year
empirical campaign against production compilers (Csmith), a DSL whose compiler
proves a named trade-off space (Halide), and proof-engineering tooling with a
badged artifact (Sisyphus). Common denominator: the system is the argument.
Decision procedure
1. Write the one-sentence claim. Underline its verb.
2. If the verb is "we prove" -> POPL unless benchmarks carry equal weight.
3. If the verb is "we measure/build" -> PLDI candidate; check benchmark rigor is achievable by November.
4. If the verb is "we observe/design" -> OOPSLA/ICFP comparison first.
5. Confirm the June-audience test: would a PLDI hallway care?
6. Check the calendar: PLDI's single deadline (Nov) vs POPL (~Jul) vs OOPSLA rounds.
7. Commit; retrofit the framing to the chosen venue, never to two at once.Deadline-driven routing — sending a POPL-shaped theory paper to PLDI because November is closer — produces the characteristic "strong work, wrong evidence" reject and burns a year.
Output format
[Fit] High / Medium / Low, one line
[Claim verb] prove / build / measure / design / observe
[Evidence home] theorem / implementation+benchmarks / study
[Family alternative] POPL / OOPSLA / ICFP, with the switch cost
[Outside routing] ASPLOS / CAV / ICSE / systems venue if applicable
[Calendar] next feasible deadline, from live pages (PLDI 2027: 待核实)© 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-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pldi Topic Selection 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 Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| TopicsZimoLiao/scholaraio | 577 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Add Shape Inferenceonnx/onnx | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Bestblogs Topicginobefun/BestBlogs | 4k | — | ~670 | Automated safety check: Pass | None | |
| Zsxq Topicitwanger/toBeBetterJavaer | 18k | — | ~564 | Automated safety check: Pass | None |
Similar skills
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Add Shape Inference
onnx/onnx
Add or update type and shape inference for an ONNX operator.
Bestblogs Topic
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
Zsxq Topic
itwanger/toBeBetterJavaer
知识星球主题管理：搜索主题、查看主题详情、发布帖子、编辑主题、发表评论、回复某条评论（楼中楼）、回答提问、删除主题；通过 api call 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
Shapely Compute
parcadei/Continuous-Claude-v3
Computational geometry with Shapely - create geometries, boolean operations, measurements, predicates
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…
Questions about Pldi Topic Selection
What does Pldi Topic Selection do?
A skill your agent uses when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or…. Pldi Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the PACMPL family to POPL, OOPSLA, or ICFP, or outward to ASPLOS, CGO, CAV, ICSE/FSE, or a systems venue, based on where the claim's evidence actually lives.
When should I use Pldi Topic Selection?
Pldi Topic Selection fits situations like: deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence —; better routed inside the PACMPL family to POPL; outward to ASPLOS; A systems venue.
How do I install Pldi Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-topic-selection -a claude-code`. Or copy the skill folder (PLDI-Skills/skills/pldi-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pldi-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Pldi Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-topic-selection -a codex`. Or copy the skill folder (PLDI-Skills/skills/pldi-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pldi-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Pldi Topic Selection 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-topic-selection -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-topic-selection, .gemini/skills/pldi-topic-selection, .github/skills/pldi-topic-selection and .opencode/skills/pldi-topic-selection in your project.
What does Pldi Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Pldi Topic Selection is instructions for the agent only.
Does Pldi Topic Selection 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 Topic Selection 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 Topic Selection use?
Pldi Topic Selection 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 Topic Selection use?
About 1.1k tokens (SKILL.md is roughly 4.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 Pldi Topic Selection?
Skills that share tags, products or a category with Pldi Topic Selection: Topics (ZimoLiao/scholaraio, 577 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Add Shape Inference (onnx/onnx, 22k stars) and Bestblogs Topic (ginobefun/BestBlogs, 4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pldi Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.