Individual skill
socc-experiments
Use 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.
SoCC-Skills/skills/socc-experiments/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,409
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# SoCC Experiments
Use this before submission when the evaluation is not yet locked. SoCC reviewers come from **both
SIGMOD and SIGOPS**, and the evaluation is where a good cloud idea is won or lost. The organizing
principle is **measured evidence proportional to the claim** — the study must test the thing the
paper asserts, on a system and workloads a skeptic from either community would accept, with **tail
latency and cost** reported, not just the mean.
## Evaluation audit
- **Prefer a real or realistic deployment over simulation.** A cloud claim about a system needs the
system running on a testbed or cluster; simulation alone invites the "does it hold on real
hardware?" reject. Where full scale is impossible, run a faithful scaled deployment and say so.
- **Use production or representative workloads/traces,** with stated provenance and selection, and