Agent skill · Data & Analytics

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.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-topic-selection --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: SoCC-Skills/skills/socc-topic-selection/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 systems-and-data intersection that SoCC owns, or is it a pure-systems or pure-data result better served by a specialized flagship?"** SoCC's sweet spot is the paper that a *datacenter operator or cloud platform team* would act on: storage and data services, resource management and scheduling, serverless, multi-tenancy, big-data and ML-systems infrastructure, edge/fog,

What's inside
Steps it walks through
  1. The routing question that matters most
  2. Sibling-venue routing table
  3. Contribution shapes SoCC rewards
  4. The model-swap and re-label tests
  5. Evidence maturity, without the ladder cliché
  6. Cheap reconnaissance before committing
  7. Decision procedure
More from Awesome-Journal-Skills
All skills →
About this skill
What does the socc-topic-selection skill do?

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.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-topic-selection --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.

Keep going