Individual skill

socc-topic-selection

Use when deciding whether a cloud-computing project belongs at ACM SoCC or should be routed to OSDI, NSDI, EuroSys, USENIX ATC, SOSP, or a data venue (SIGMOD/VLDB), leaning on SoCC's unique joint SIGMOD+SIGOPS identity, its welcome of measurement and experience papers alongside systems-building, and the model-swap and re-label tests.

SoCC-Skills/skills/socc-topic-selection/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
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,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# SoCC Topic Selection

Decide the venue before drafting. SoCC — the ACM Symposium on Cloud Computing — is the **only
conference co-sponsored by SIGMOD and SIGOPS**, and that joint sponsorship *is* its identity: it
sits at the **systems-and-data intersection** of cloud research. Reviewers read for a **cloud
contribution that matters at scale**, and the venue explicitly welcomes not just clean-slate
systems but **measurement studies, experience papers, and cloud-economics work** that a pure
OS/networking flagship might treat as second-class. A technically strong paper whose real home is
kernel scheduling, network fabric, or query-optimizer internals is respected and then routed
elsewhere.

## The routing question that matters most

The decisive question is rarely "is this cloud?" but **"does this contribution live at the
Back to top