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 the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks…
MITAuto-check passed
Install Sosp Experiments
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-experiments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-experiments .claude/skills/sosp-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 "sosp-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-experiments into .claude/skills/sosp-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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/SOSP-Skills/skills/sosp-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 sosp-experiments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-experiments .agents/skills/sosp-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 "sosp-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-experiments into .agents/skills/sosp-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-experiments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-experiments .cursor/skills/sosp-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 "sosp-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-experiments into .cursor/skills/sosp-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 SOSP-Skills/skills/sosp-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 sosp-experiments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-experiments .gemini/skills/sosp-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 "sosp-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-experiments into .gemini/skills/sosp-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-experiments .github/skills/sosp-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 "sosp-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-experiments into .github/skills/sosp-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-experiments .opencode/skills/sosp-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 "sosp-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-experiments into .opencode/skills/sosp-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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
sosp-experiments- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 566 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 the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks…
- Works in 3 steps: Microbenchmarks isolate mechanisms and… → Application-level or end-to-end… → Trace-driven runs on production or…
- Auditing the evaluation of a SOSP paper — mapping every claim to an experiment
- SKILL.md covers Claims first, experiments second, Baselines a systems PC accepts, Workloads: three layers, each… and Tails, variance, and the…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sosp Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks with end-to-end and failure runs, reporting tails and overheads honestly, and isolating the mechanism the design credits.
Its SKILL.md is about 1.3k 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 the evaluation of a SOSP paper — mapping every claim to an experiment
- Choosing baselines a systems PC will accept as fair
- Mixing microbenchmarks with end-to-end and failure runs
- Reporting tails and overheads honestly
Example prompts
- “/sosp-experiments”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Microbenchmarks isolate mechanisms and expose costs; they prove why.
- Application-level or end-to-end workloads (real applications on top of the
- Trace-driven runs on production or public traces prove relevance; when 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
Sosp Experiments loads about 1.3k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 566 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). 566 words, ~1,321 tokens.
Download SKILL.mdSave it as
.claude/skills/sosp-experiments/SKILL.md (or your agent's skills folder).- name
- sosp-experiments
- description
- Use when designing or auditing the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks with end-to-end and failure runs, reporting tails and overheads honestly, and isolating the mechanism the design credits.
SOSP Experiments
Use this while the evaluation is being designed — it determines whether the paper is writable at all. SOSP reviews concentrate their negative weight on evaluation soundness, and the venue's response phase forbids new experiments (CFP, 2026 cycle, checked 2026-07-08), so a hole discovered in review stays a hole. The evaluation's job is to make each claim's evidence findable, fair, and attributable to the mechanism the paper credits.
Claims first, experiments second
Write the claim list before designing runs; every evaluation subsection should open by naming the claim it discharges.
| Claim type | Required evidence | Classic hole |
|---|---|---|
| "Foo improves throughput/latency" | End-to-end runs vs tuned state-of-the-art baselines, real + synthetic workloads | Baseline in default config while Foo is hand-tuned |
| "The gain comes from mechanism M" | Ablation: Foo with M disabled, or M grafted onto the baseline | Whole-system win credited to one component on faith |
| "Overhead is acceptable" | Cost measured where it hurts: memory, CPU, write amplification, the workload M does not help | Only the favorable workload reported |
| "Foo survives failures" | Kill/partition/restart runs with recovery-time distributions | Availability claimed, only steady state measured |
| "Foo scales" | Sweep to the knee, with the bottleneck at the knee identified | Straight-line plot ending before saturation |
| "Correctness holds under concurrency" | Stress + targeted schedules, or a verification argument | "We ran it for days" |
Baselines a systems PC accepts
- Compare against the published state of the art, not only your own strawman variants; if the strongest system is unrunnable (dead code, unobtainable hardware), say so in the paper and compare against its published numbers with the configuration deltas spelled out.
- Tune the baseline with the same care as your system, and document both tunings. "We used X's defaults" invites the PC member who built X to explain what the defaults are for.
- Match the fairness surface: same kernel, same mitigations, same NIC firmware,
same warm-up policy. An OS-level artifact changes the platform under everything,
so baseline runs need the environment pinned too (see
sosp-reproducibility).
Show full SKILL.md (243 more words)Show less
Workloads: three layers, each with a job
- Microbenchmarks isolate mechanisms and expose costs; they prove why.
- Application-level or end-to-end workloads (real applications on top of the system) prove the why matters; a syscall-path win that vanishes under a real application is a finding, not a failure to report.
- Trace-driven runs on production or public traces prove relevance; when the trace is private, characterize it and pair it with a matched synthetic generator (the tiering that artifact evaluation later formalizes).
Tails, variance, and the numbers reviewers check first
Systems effects live in distributions, and SOSP reviewers reach for the tail:
- Report p50/p99 (p999 where the claim warrants) with repetition counts and spread; a single-run p99 will be called folklore.
- State the load point for every latency number — latency without offered load is meaningless, and latency-throughput curves beat point pairs.
- Account for the denominator: speedups over a baseline that is itself misconfigured are the fastest way to lose the room at the PC meeting.
Evaluation matrix (one row per claim; freeze before the writing sprint)
claim experiment workload/trace baseline+tuning metric+spread figure
throughput at scale e2e sweep to knee YCSB-B + trace T1 X v2.3 tuned §6.1 ops/s, 5 runs, CI Fig 6
gain attributable to M ablation Foo-noM YCSB-B Foo itself delta ops/s Fig 7
recovery independent of kill @ 3 log sizes trace T1 X p50/p99 recov, 10x Fig 9
log size
overhead where M is idle read-only run YCSB-C X CPU%, mem, 5 runs Tab 4Honesty as a strategy
The evaluation section is also where credibility is banked for the PC meeting. Report the workload where the design loses, and explain the regime boundary — a measured loss with a mechanism story reads as understanding; a suspiciously uniform sweep of wins reads as curation. Reviewers at this venue have written these sections themselves; the fastest way to earn a champion is an evaluation that anticipates the attack they were about to write.
Output format
[Claim map] every paper claim -> experiment row? orphans: <list>
[Baseline audit] SOTA present? tuning documented both sides?
[Layer coverage] micro / end-to-end / trace — gaps
[Tail discipline] spreads + load points on all latency numbers?
[Attribution] ablations isolate the credited mechanism?
[Adverse results] where the design loses + is it in the paper?© 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 SOSP-Skills/skills/sosp-experiments of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sosp 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 |
|---|---|---|---|---|---|---|
| Sosp Experiments this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Design Audit Against Rams' Principlesthedotmack/claude-mem | 98k | — | ~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 Sosp Experiments
What does Sosp Experiments do?
A skill your agent uses when designing or auditing the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks…. Sosp Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when designing or auditing the evaluation of a SOSP paper — mapping every claim to an experiment, choosing baselines a systems PC will accept as fair, mixing microbenchmarks with end-to-end and failure runs, reporting tails and overheads honestly, and isolating the mechanism the design credits.
When should I use Sosp Experiments?
Sosp Experiments fits situations like: auditing the evaluation of a SOSP paper — mapping every claim to an experiment; choosing baselines a systems PC will accept as fair; mixing microbenchmarks with end-to-end and failure runs; reporting tails and overheads honestly.
How do I install Sosp Experiments in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-experiments -a claude-code`. Or copy the skill folder (SOSP-Skills/skills/sosp-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sosp-experiments in your project. Claude Code loads it when a task matches its description.
How do I install Sosp Experiments in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-experiments -a codex`. Or copy the skill folder (SOSP-Skills/skills/sosp-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sosp-experiments in your project. Codex loads it when a task matches its description.
Can I use Sosp 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 sosp-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/sosp-experiments, .gemini/skills/sosp-experiments, .github/skills/sosp-experiments and .opencode/skills/sosp-experiments in your project.
What does Sosp Experiments need to run?
SKILL.md names no scripts, command-line tools or credentials: Sosp Experiments is instructions for the agent only.
Does Sosp 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 Sosp 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 Sosp Experiments use?
Sosp 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 Sosp Experiments use?
About 1.3k tokens (SKILL.md is roughly 5.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 Sosp Experiments?
Skills that share tags, products or a category with Sosp Experiments: Design Audit Against Rams' Principles (thedotmack/claude-mem, 98k 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 Sosp Experiments?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.