Arize Evaluator
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
A skill your agent uses when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer…
MITAuto-check passed
Install Ppopp Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ppopp-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/PPoPP-Skills/skills/ppopp-review-process .claude/skills/ppopp-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 "ppopp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PPoPP-Skills/skills/ppopp-review-process into .claude/skills/ppopp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ppopp-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/PPoPP-Skills/skills/ppopp-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 ppopp-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ppopp-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/PPoPP-Skills/skills/ppopp-review-process .agents/skills/ppopp-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 "ppopp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PPoPP-Skills/skills/ppopp-review-process into .agents/skills/ppopp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ppopp-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 ppopp-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ppopp-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/PPoPP-Skills/skills/ppopp-review-process .cursor/skills/ppopp-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 "ppopp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PPoPP-Skills/skills/ppopp-review-process into .cursor/skills/ppopp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ppopp-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 PPoPP-Skills/skills/ppopp-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 ppopp-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ppopp-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/PPoPP-Skills/skills/ppopp-review-process .gemini/skills/ppopp-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 "ppopp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PPoPP-Skills/skills/ppopp-review-process into .gemini/skills/ppopp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ppopp-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 ppopp-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 ppopp-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/PPoPP-Skills/skills/ppopp-review-process .github/skills/ppopp-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 "ppopp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PPoPP-Skills/skills/ppopp-review-process into .github/skills/ppopp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ppopp-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 ppopp-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 ppopp-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/PPoPP-Skills/skills/ppopp-review-process .opencode/skills/ppopp-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 "ppopp-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PPoPP-Skills/skills/ppopp-review-process into .opencode/skills/ppopp-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ppopp-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
ppopp-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 735 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer…
- Reasoning about how a PPoPP submission is evaluated
- SKILL.md covers Process model, What PPoPP reviewers weigh, Reading a decision and How PPoPP differs from its…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering double-blind review
What it does
Ppopp Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer matching, the author-response rebuttal, the accept/reject decision with automatic poster consideration, and how PPoPP's process differs from PLDI's and CGO's.
Its SKILL.md is about 1.6k 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
- Reasoning about how a PPoPP submission is evaluated
- Covering double-blind review
- The Program Committee plus External/Extended Review Committee model
- TPMS reviewer matching
Example prompts
- “s process differs from PLDI”
- “/ppopp-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
Ppopp Review Process loads about 1.6k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 735 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). 735 words, ~1,620 tokens.
Download SKILL.mdSave it as
.claude/skills/ppopp-review-process/SKILL.md (or your agent's skills folder).- name
- ppopp-review-process
- description
- Use when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer matching, the author-response rebuttal, the accept/reject decision with automatic poster consideration, and how PPoPP's process differs from PLDI's and CGO's.
PPoPP Review Process
Model the pipeline before interpreting any single review. PPoPP runs a single-round, double-blind conference review with a scheduled author-response rebuttal and an unusual safety net: papers not accepted for a talk are automatically considered for posters. The most consequential mental shift for authors arriving from a journal-style venue is that there is (as verified) no guaranteed revise-and-resubmit round — the rebuttal is your one written turn, so it must land.
Process model
- Submission and review run on HotCRP with double-blind anonymity: author identities are hidden from reviewers and reviewer identities from authors.
- Papers are read by the Program Committee and an External/Extended Review Committee (ERC); declare conflicts against both pools. Reviewer assignment may use the Toronto Paper Matching System (TPMS), so your abstract and topic tags shape who reads you.
- After the initial reviews there is a fixed author-response period (PPoPP 2026: 27–29 October 2025). Authors respond within a word cap; reviewers then discuss and decide.
- The primary decision is accept / reject for a regular presentation. Whether an explicit intermediate "Revision" category is offered in a given cycle is 待核实 — do not assume it.
- Automatic poster consideration: submissions not accepted for a talk are automatically considered for the poster track, with a two-page summary in the proceedings.
What PPoPP reviewers weigh
| Axis | What they check | Common failure |
|---|---|---|
| Parallelism as the contribution | Is the concurrency/parallel-performance the point? | A compiler/theory result wearing a parallel costume (a CGO/POPL reroute) |
| Correctness under concurrency | Races, linearizability/progress, the memory model | "It passed my tests" with no argument about interleavings |
| Scalability | Speedup curves, core sweeps, NUMA/GPU, saturation | One thread count; a win that vanishes on another topology |
| Baseline honesty | Comparison to the strongest real competitor | Beating a strawman or the authors' own unoptimized code |
| Measurement rigor | Variance, warm-up, pinning, repeated runs | A single-run bar chart with no error bars |
| Reproducibility | Enough to re-run; an artifact | Hardware and topology unstated |
Reading a decision
| Decision | What it means | Author move |
|---|---|---|
| Accept (talk) | Contribution and evidence hold | Camera-ready + artifact; do not reopen scope |
| Poster (auto-considered) | The idea is of interest but not a full talk this cycle | Decide in advance whether the 2-page proceedings summary is worth it |
| Reject | Structural: wrong scope, weak baseline, no scaling story | Reframe or reroute (CGO/PLDI/ASPLOS/SC or a later round) |
| "Revision" (if offered — 待核实) | Repairable gaps within a bounded window | Treat as an R&R; make or explicitly decline every request with evidence |
The strategic reading: because there is (as verified) one written turn, design the submission so its weakest point is answerable in the rebuttal with a number you already have (a pre-run baseline, an extra core-count) rather than something requiring a month of new machine time.
Show full SKILL.md (291 more words)Show less
How PPoPP differs from its siblings
- vs. PLDI/CGO: those judge a language/compiler contribution; PPoPP judges the parallel-program
behavior. A great pass with a thin scaling story fails here and would pass there. Different
template too (PPoPP two-column
acmartsigplan, 10 pages). - vs. POPL: POPL rewards the concurrency proof itself; PPoPP wants the proof plus a measured parallel system. A pure logic is a POPL paper.
- vs. ASPLOS/HPCA: those own the machine; a PPoPP reviewer reads your hardware as the platform, not the result, and will discount a win that is really a microarchitecture artifact.
Where author leverage actually exists
[Before submission] abstract + topic tags -> TPMS/PC matching (largest early lever)
[Initial reviews] factual corrections, a pre-run number, a clarified interleaving argument
[Rebuttal] the decisive turn: answer "does it scale?" and "baseline X?" with data
already in hand, within the word cap
[After reject] no appeal; reroute to a co-located sibling or the next roundA rebuttal moves borderline papers when it supplies a scaling point or a baseline a reviewer said was missing; it does not move papers when it argues taste or promises future experiments. The classic PPoPP loss is a reviewer asking "how does this behave at 128 cores / on a second GPU?" and the authors having only the one machine's numbers.
Reading a review packet
Weight reviews before answering. A review that cites your speedup figure, your baseline choice, and your correctness argument was read closely; answer each reviewer on the axis they raised — correctness reviewers with an interleaving argument, performance reviewers with a number. A review that only questions novelty has left soundness to the others; do not spend your word budget there.
Misreadings to avoid
- Assuming a revise-and-resubmit safety net — as verified there is one written turn; the rebuttal is not a placeholder.
- Treating the poster path as failure — the two-page proceedings summary is a real, citable outcome; decide about it deliberately.
- Ignoring the ERC — external reviewers carry real weight and real conflicts.
- Projecting last year's cadence — round count, rebuttal timing, and any "Revision" category are decided per edition.
Output format
[Process stage] pre-submission / awaiting reviews / rebuttal / decided
[Decision] accept / poster / reject / revision(if offered), with the driving criterion
[Criterion map] each review point -> parallelism-as-point | correctness | scalability | baseline | measurement | reproducibility
[Leverage plan] the rebuttal number or correction that can actually change the outcome
[Forbidden moves] identity leak / promised-but-unrun experiments / arguing taste© 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 PPoPP-Skills/skills/ppopp-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ppopp 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 |
|---|---|---|---|---|---|---|
| Ppopp Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| LLM Evaluationdavila7/claude-code-templates | 33k | 12 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Agent Evaluationsickn33/agentic-awesome-skills | 47k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Deepseek Reasonruvnet/ruflo | 74k | — | ~626 | Automated safety check: Notes | MIT | |
| EvaluatorsArize-ai/phoenix | 12k | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
LLM Evaluation
davila7/claude-code-templates
Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.
Agent Evaluation
sickn33/agentic-awesome-skills
Evaluate agent behavior with versioned cases and explicit verifiers.
Deepseek Reason
ruvnet/ruflo
Reasoning-mode completion against DeepSeek's deepseek-reasoner model (R1) via /v1/chat/completions.
Evaluators
Arize-ai/phoenix
Author or refine a Phoenix evaluator — code or LLM-as-a-judge — that scores a run's output.
Agent Evaluation Reporting
sickn33/agentic-awesome-skills
A skill your agent uses when summarizing agent evaluations where autonomous, assisted, failed, timed-out, or invalid outcomes must remain distinct and comparable.
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 Ppopp Review Process
What does Ppopp Review Process do?
A skill your agent uses when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer…. Ppopp Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a PPoPP submission is evaluated, covering double-blind review, the Program Committee plus External/Extended Review Committee model, TPMS reviewer matching, the author-response rebuttal, the accept/reject decision with automatic poster consideration, and how PPoPP's process differs from PLDI's and CGO's.
When should I use Ppopp Review Process?
Ppopp Review Process fits situations like: reasoning about how a PPoPP submission is evaluated; covering double-blind review; the Program Committee plus External/Extended Review Committee model; TPMS reviewer matching.
How do I install Ppopp Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-review-process -a claude-code`. Or copy the skill folder (PPoPP-Skills/skills/ppopp-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ppopp-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Ppopp Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-review-process -a codex`. Or copy the skill folder (PPoPP-Skills/skills/ppopp-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ppopp-review-process in your project. Codex loads it when a task matches its description.
Can I use Ppopp 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 ppopp-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/ppopp-review-process, .gemini/skills/ppopp-review-process, .github/skills/ppopp-review-process and .opencode/skills/ppopp-review-process in your project.
What does Ppopp Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Ppopp Review Process is instructions for the agent only.
Does Ppopp 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 Ppopp 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 Ppopp Review Process use?
Ppopp 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 Ppopp Review Process use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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 Ppopp Review Process?
Skills that share tags, products or a category with Ppopp Review Process: Arize Evaluator (github/awesome-copilot, 40k stars), LLM Evaluation (davila7/claude-code-templates, 33k stars), Agent Evaluation (sickn33/agentic-awesome-skills, 47k stars) and Deepseek Reason (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ppopp 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.