Design Audit Against Rams' Principles
thedotmack/claude-mem
Audits a design against Dieter Rams' ten principles of good design, scores each with evidence, and hands off a make-plan prompt for a new, refined or redesigned outcome.
A skill your agent uses when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with…
MITAuto-check passed
Install Pldi Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-experiments --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-experiments .claude/skills/pldi-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-experiments into .claude/skills/pldi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-experiments", 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-experimentsType 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-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-experiments --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-experiments .agents/skills/pldi-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-experiments into .agents/skills/pldi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-experiments", 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-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-experiments --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-experiments .cursor/skills/pldi-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-experiments into .cursor/skills/pldi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-experiments", 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-experiments--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-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-experiments --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-experiments .gemini/skills/pldi-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-experiments into .gemini/skills/pldi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-experiments", 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-experimentsInstalls 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-experiments -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-experiments .github/skills/pldi-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-experiments into .github/skills/pldi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-experiments", 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-experiments -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-experiments --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-experiments .opencode/skills/pldi-experiments && 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-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-experiments into .opencode/skills/pldi-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-experiments", 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-experiments- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 424 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with…
- Auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations
- SKILL.md covers Benchmark choice is an…, Baselines that survive the PC, Ablations isolate the mechanism and The three currencies, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Measuring runtime
What it does
Pldi Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with warmup and variance discipline, running ablations that isolate the claimed mechanism, and scoping claims to the platforms measured.
Its SKILL.md is about 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
- Auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations
- Measuring runtime
- Memory with warmup and variance discipline
- Running ablations that isolate the claimed mechanism
Example prompts
- “/pldi-experiments”
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 Experiments loads about 1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 424 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). 424 words, ~1,034 tokens.
Download SKILL.mdSave it as
.claude/skills/pldi-experiments/SKILL.md (or your agent's skills folder).- name
- pldi-experiments
- description
- Use when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with warmup and variance discipline, running ablations that isolate the claimed mechanism, and scoping claims to the platforms measured.
PLDI Experiments
A PLDI evaluation answers one question: does the claimed mechanism cause the
claimed effect on programs that matter? Everything in the design flows from
making that causal link auditable. The community's shared rubric is SIGPLAN's
Empirical Evaluation checklist (see pldi-reproducibility for the measurement
hygiene); this skill covers the design choices above the hygiene layer.
Benchmark choice is an argument, not a default
- Justify the suite relative to the claim: an allocation optimizer needs allocation-heavy programs and allocation-light ones (to show no regression); a parser-facing analysis needs real grammars, not microbenchmarks.
- Use community suites where they exist and state versions; add real-world applications when the suite is known to under-represent your phenomenon.
- List exclusions with reasons. "We exclude two SPEC programs that use
setjmp, which our restriction rejects (§4.4)" builds trust; silent dropping destroys it. - Include programs your technique should not help. Flat results on those are evidence the instrument works.
Baselines that survive the PC
| Weak move | Defensible move |
|---|---|
| Compare against -O0 or an untuned build | Strongest published configuration of the standard toolchain (state version + flags) |
| Reimplement a rival technique quickly | Use the authors' artifact where one exists; note deviations |
| Compare only against your own prior system | Add the external baseline reviewers will name in review |
| Report best-of-N runs | Report distribution over all N runs |
| One aggregate number | Aggregate + per-benchmark table, so wins and losses show |
The reviewers most likely to be assigned your paper wrote the baselines. Assume the baseline's author reads your flags line.
Show full SKILL.md (176 more words)Show less
Ablations isolate the mechanism
The claim "our escape signatures cause the speedup" needs the experiment where signatures are replaced by the prior summary while everything else stays fixed. Design one ablation per mechanism named in the contributions list; a mechanism with no ablation is a mechanism the paper does not actually test.
The three currencies
Runtime, compile time, and memory are all first-class at PLDI. A technique that buys 1.1x runtime with 3x compile time must say so in the abstract, not in a footnote. Report all three, each with repetitions and dispersion, even when one of them is "no change" — especially when it is "no change."
Anticipated-objection pass
Run this list before the deadline; it is roughly what a PLDI review's evaluation section says when it goes badly:
[ ] Is the delta bigger than the noise band? (CI overlap check per benchmark)
[ ] Does the effect survive on a second microarchitecture?
[ ] Are the flags/version of every baseline stated and current?
[ ] Is there a benchmark where we lose, and do we explain it?
[ ] Does the ablation exist for every mechanism we claim credit for?
[ ] Is warmup/steady-state handling stated per benchmark family?
[ ] Could the speedup come from an unrelated engineering change? (same-codebase control)Negative and neutral results
A paragraph explaining the two programs where the technique regresses — with a cause, not a shrug — routinely appears in accepted PLDI papers and in Distinguished Paper profiles. Reviewers read it as instrument calibration. Deleting the losing rows reads as the opposite.
Output format
[Suite] chosen + justified? versions pinned? exclusions listed?
[Baselines] strongest config? external baseline present? flags stated?
[Ablations] mechanism -> ablation experiment (n/n covered)
[Currencies] runtime / compile time / memory each measured with variance?
[Objection pass] items failing from the checklist above© 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-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pldi Experiments 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 Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Design Audit Against Rams' Principlesthedotmack/claude-mem | 99k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep | 17k | 1 repos | ~2.7k | Automated safety check: Notes | MIT | |
| Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep | 17k | — | ~3.2k | Automated safety check: Notes | MIT | |
| Experiment Designeralirezarezvani/claude-skills | 28k | 1 repos | ~783 | Automated safety check: Pass | MIT | |
| OpenClaw Design Auditopenclaw/clawhub | 9.5k | — | ~498 | Automated safety check: Pass | MIT |
Similar skills
Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
Experiment Designer
alirezarezvani/claude-skills
A skill your agent uses when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor.
OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
Design System
affaan-m/ECC
Generate a design system from an existing codebase or audit one for visual consistency: extract tokens (colors, typography, spacing, shadows) into design-tokens.json and CSS custom properties with…
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 Experiments
What does Pldi Experiments do?
A skill your agent uses when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with…. Pldi Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring runtime, compile time, and memory with warmup and variance discipline, running ablations that isolate the claimed mechanism, and scoping claims to the platforms measured.
When should I use Pldi Experiments?
Pldi Experiments fits situations like: auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations; measuring runtime; memory with warmup and variance discipline; running ablations that isolate the claimed mechanism.
How do I install Pldi Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-experiments -a claude-code`. Or copy the skill folder (PLDI-Skills/skills/pldi-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pldi-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Pldi Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-experiments -a codex`. Or copy the skill folder (PLDI-Skills/skills/pldi-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pldi-experiments in your project. Codex loads it when a task matches its description.
Can I use Pldi Experiments 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-experiments -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-experiments, .gemini/skills/pldi-experiments, .github/skills/pldi-experiments and .opencode/skills/pldi-experiments in your project.
What does Pldi Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Pldi Experiments is instructions for the agent only.
Does Pldi Experiments 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 Experiments 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 Experiments use?
Pldi Experiments 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 Experiments use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Experiments?
Skills that share tags, products or a category with Pldi Experiments: Design Audit Against Rams' Principles (thedotmack/claude-mem, 99k stars), Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars) and Experiment Designer (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pldi Experiments?
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.