TransformerLens Interpretability
Orchestra-Research/AI-Research-SKILLs
Guides mechanistic interpretability work with TransformerLens: loading models, caching activations, using HookPoints, activation patching and attention-pattern analysis.
A skill your agent uses when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10%…
MITAuto-check passed
Install Pldi Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-review-process --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-review-process .claude/skills/pldi-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-review-process into .claude/skills/pldi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-review-process --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-review-process .agents/skills/pldi-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-review-process into .agents/skills/pldi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-review-process --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-review-process .cursor/skills/pldi-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-review-process into .cursor/skills/pldi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-review-process --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-review-process .gemini/skills/pldi-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-review-process into .gemini/skills/pldi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/pldi-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-review-process into .github/skills/pldi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/pldi-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-review-process into .opencode/skills/pldi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~957 tokens
- SKILL.md length
- 425 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10%…
- Interpreting PLDIs review pipeline — double-blind HotCRP reviewing by a PL-implementor PC
- SKILL.md covers Who is reading you, Stage-by-stage, Distinguished papers and Reading a decision, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The February author-response window
What it does
Pldi Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10% Distinguished Paper selection, and how post-acceptance artifact evaluation and PACMPL publication follow the decision.
Its SKILL.md is about 960 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
- Interpreting PLDIs review pipeline — double-blind HotCRP reviewing by a PL-implementor PC
- The February author-response window
- March notification
- Up-to-10% Distinguished Paper selection
Example prompts
- “/pldi-review-process”
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 Review Process loads about 957 tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 425 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). 425 words, ~957 tokens.
Download SKILL.mdSave it as
.claude/skills/pldi-review-process/SKILL.md (or your agent's skills folder).- name
- pldi-review-process
- description
- Use when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10% Distinguished Paper selection, and how post-acceptance artifact evaluation and PACMPL publication follow the decision.
PLDI Review Process
Model the pipeline from the 2026 cycle (pldi26.sigplan.org, read 2026-07-08), then re-anchor every date to the current edition: papers due November 13, 2025; reviews written over the winter; author response February 17-21, 2026; decisions March 5, 2026; artifact evaluation after acceptance; publication as PACMPL Issue PLDI; talks in Boulder June 17-19, 2026. Chairs rotate per edition — 2026 ran under Program Chair Manu Sridharan — so process details are one-cycle facts.
Who is reading you
The PC is dominated by people who have shipped compilers, runtimes, analyzers, and verifiers. Practical consequences:
- Claims are audited mechanically. A reviewer may re-derive your complexity bound, check your semantics against a corner case, or mentally rerun your benchmark protocol. Vague spots read as hidden flaws.
- "Would this survive contact with real programs?" is the ambient question. Toy-language-only evaluations need an explicit argument for why the toy captures the hard part.
- Double-blind is real but statistical: some reviewers will guess your lab; the process still requires the paper not to confirm it.
Stage-by-stage
| Stage (2026 anchors) | What happens | Your lever |
|---|---|---|
| Nov deadline | Triage: format, page cap, anonymity, scope | Zero summary-rejection triggers (pldi-submission) |
| Winter reviewing | 3+ reviews scored on novelty, soundness, evaluation, clarity | Already spent; the paper argues alone |
| Feb 17-21 response | Authors answer factual errors and direct questions | The one paragraph that saves a soundness doubt (pldi-author-response) |
| PC discussion | Reviews + response reconciled; champions matter | A response that arms your champion with quotable pointers |
| Mar 5 notification | Accept / reject (any shepherding terms come with the letter) | Deliver conditions precisely and fast |
| Post-acceptance | Artifact evaluation, badges, PACMPL production | pldi-artifact-evaluation, pldi-camera-ready |
Whether a given cycle uses conditional acceptance or formal shepherding was not confirmed for 2026 (待核实) — read your notification letter as the authority.
Show full SKILL.md (138 more words)Show less
Distinguished papers
Up to 10% of accepted papers may be designated Distinguished Papers; PLDI 2025 named 6 of 89 (about 6.7%). You cannot apply for it, but the profile is consistent: a crisp problem, a mechanism others can reuse, an evaluation beyond reproach, and usually a strong artifact. Aim the paper at that profile and let the committee do what it does.
Reading a decision
- Reject with soundness objections: fix before anything else; the same PC community reviews for POPL and OOPSLA, and a known-broken theorem follows you.
- Reject on evaluation: usually the cheapest repair — the SIGPLAN Empirical
Evaluation checklist (
pldi-reproducibility) is the reviewers' own rubric. - Reject on fit ("this is a POPL paper", "this is engineering"): a routing
signal, not a quality verdict; rerun
pldi-topic-selectionhonestly. - Accept: your response commitments are now contractual; see
pldi-camera-ready.
Output format
[Stage] pre-submission / in review / response window / decided
[Review posture] champion? soundness doubts? evaluation objections?
[Response leverage] <which objections are answerable from the submitted PDF>
[Decision reading] accept path / repair-and-resubmit / re-route venue
[Next dates] <from the live cycle pages, with 待核实 flags>© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pldi Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~957 | Automated safety check: Pass | MIT | |
| TransformerLens InterpretabilityOrchestra-Research/AI-Research-SKILLs | 13k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Nnsight Remote InterpretabilityOrchestra-Research/AI-Research-SKILLs | 13k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Paper Interpretationdigoal/blog | 8.6k | — | ~1.5k | Automated safety check: Pass | GPL-2.0 | |
| Review Hog Blind Spots GeneralPostHog/posthog | 40k | — | ~475 | Automated safety check: Pass | Custom licence | |
| Blind Review Sanitizeraipoch/medical-research-skills | 1.9k | — | ~2.2k | Automated safety check: Pass | MIT |
Similar skills
Nnsight Remote Interpretability
Orchestra-Research/AI-Research-SKILLs
Provides guidance for interpreting and manipulating neural network internals using nnsight with optional NDIF remote execution.
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
- Official
Review Hog Blind Spots General
PostHog/posthog
The general blind-spot check for PostHog Review, the final sweep that runs after every enabled review perspective has reviewed a chunk.
Blind Review Sanitizer
aipoch/medical-research-skills
Use blind-review-sanitizer for academic writing workflows that need structured anonymization, explicit assumptions, and clear output boundaries for double-blind submission.
Blind Spot Scan
lijigang/ljg-skills
Reads yesterday's AI conversations, identifies one thinking blind spot, picks a WeRead book chapter to address it and writes an analysis note.
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 Review Process
What does Pldi Review Process do?
A skill your agent uses when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10%…. Pldi Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window, March notification, up-to-10% Distinguished Paper selection, and how post-acceptance artifact evaluation and PACMPL publication follow the decision.
When should I use Pldi Review Process?
Pldi Review Process fits situations like: interpreting PLDIs review pipeline — double-blind HotCRP reviewing by a PL-implementor PC; the February author-response window; march notification; up-to-10% Distinguished Paper selection.
How do I install Pldi Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-review-process -a claude-code`. Or copy the skill folder (PLDI-Skills/skills/pldi-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pldi-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Pldi Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-review-process -a codex`. Or copy the skill folder (PLDI-Skills/skills/pldi-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pldi-review-process in your project. Codex loads it when a task matches its description.
Can I use Pldi Review Process 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-review-process -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-review-process, .gemini/skills/pldi-review-process, .github/skills/pldi-review-process and .opencode/skills/pldi-review-process in your project.
What does Pldi Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Pldi Review Process is instructions for the agent only.
Does Pldi Review Process 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 Review Process 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 Review Process use?
Pldi Review Process 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 Review Process use?
About 957 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 Review Process?
Skills that share tags, products or a category with Pldi Review Process: TransformerLens Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Nnsight Remote Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Paper Interpretation (digoal/blog, 8.6k stars) and Review Hog Blind Spots General (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pldi Review Process?
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.