sosp-experiments
From the author
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.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-experiments -a claude-code
Installs to .claude/skills/sosp-experiments/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- osdi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an OSDI submission — choosing mature baselines and realistic workloads, structuring the section around research questions, measuring scalability and tail behavior, quantifying the design's costs, and fitting the evidence into the 12-page reviewed body.Design★ 1.3K
- icse-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ICSE research-track paper, covering subject and benchmark selection, baseline fairness, statistical tests and effect sizes as SE reviewers expect them, qualitative-methods rigor, ablations for AI-based techniques, and threats-driven study design.Testing★ 1.3K
- nsdi-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems reviewers can see where the design wins, loses, and breaks.DevOps★ 1.3K
- popl-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing the empirical component of a POPL paper — deciding whether evidence should be a mechanization, a prototype, case studies, or benchmarks; reporting proof effort and case-study coverage honestly; and keeping performance numbers in a supporting role so the formal claim stays the paper's center of gravity.Science★ 1.3K
- socc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing ACM SoCC evaluations, covering real or realistic deployments over simulation, production or representative workloads and traces, tail-latency and cost as first-class metrics, fair tuned baselines, scale and multi-tenancy behavior, reproducible measurement pipelines, and matching evidence to the shape of each cloud claim.DevOps★ 1.3K
- atc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds, fair baselines, end-to-end plus microbenchmark results, tail-latency and variance reporting, workload realism, and honest cost accounting.Science★ 1.3K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in