socc-artifact-evaluation
Use when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what a cloud-systems evaluator checks first, reproducing tail-latency and cost results on a testbed, DOI-issuing archives, and the fact that whether SoCC runs a dedicated artifact-evaluation track for a given edition must be verified.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# SoCC Artifact Evaluation Use this for artifact preparation. SoCC — as an ACM venue — follows the **ACM Artifact Review and Badging** scheme where an edition offers evaluation. **First, verify whether the current SoCC edition runs a dedicated artifact-evaluation track, and which badges it offers** — unlike some sibling systems flagships that run a standing AE process, SoCC's artifact track and badge set are decided per edition and are **待核实** as of 2026-07-09. The advice below applies once the edition's call confirms evaluation. Two things to internalize: badges are earned by evaluators actually **reproducing** your cloud results, and the review artifact (anonymized, for the paper's reviewers) is not the same deliverable as the badge artifact (de-anonymized, permanently archived). ## The ACM badges (verify the current set and names) | Badge | What it certifies | What earns it for a cloud paper | |---|---|---| | Artifacts Available | The artifact is permanently, publicly retrievable | Deposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage) | | Artifacts Evaluated - Functional | The artifact runs and does what the paper says | A documented testbed setup, a workload re
- The ACM badges (verify the current set and names)
- What a cloud-systems evaluator opens first
- Packaging plan
- Anonymized review artifact vs. badge artifact
- Worked vignette: packaging an autoscaler + trace study
- Calibration
- Output format
What does the socc-artifact-evaluation skill do?
Use when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what a cloud-systems evaluator checks first, reproducing tail-latency and cost results on a testbed, DOI-issuing archives, and the fact that whether SoCC runs a dedicated artifact-evaluation track for a given edition must be verified.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-artifact-evaluation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.