Agent skill

sigmetrics-topic-selection

Use when deciding whether a computer-systems performance project belongs at ACM SIGMETRICS or should be routed to IMC, SIGCOMM/NSDI/OSDI, INFOCOM, a learning venue (NeurIPS/ICML), or a performance journal (Performance Evaluation/TON/QUESTA), and when picking the right SIGMETRICS track (Theory / Measurement & Applied Modeling / Learning / Operational Systems).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-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: SIGMETRICS-Skills/skills/sigmetrics-topic-selection/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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

# SIGMETRICS Topic Selection Decide the venue and track before drafting. SIGMETRICS — the ACM flagship for **performance measurement, modeling, and evaluation of computer systems** — rewards a **rigorous performance-evaluation contribution**: a stochastic/queueing model with a **proven bound**, a **principled measurement study**, or a **learning-for-systems** algorithm with guarantees. A technically strong paper whose real lesson is a *built system* (route to NSDI/OSDI), a *pure network measurement* (route to IMC), or a *learning-theory result with no systems payoff* (route to NeurIPS/COLT) is respected and then rejected as out of scope. ## The routing question that matters most The decisive question is rarely "is this about systems performance?" but **"is the contribution an analyzed/measured performance result, or is it something else with performance numbers attached?"** SIGMETRICS wants the *why* — a model, a proof, a validated methodology — not only a faster system or a bigger dataset. ## Sibling-venue routing table | Signal in your project | Better home | Why | |---|---|---| | A model/policy with a **proven performance bound**, or a principled measurement/modeling study | **A

What's inside
Steps it walks through
  1. The routing question that matters most
  2. Sibling-venue routing table
  3. Contribution shapes SIGMETRICS rewards
  4. The rigor and validation tests
  5. Picking the track (do this at abstract registration)
  6. Cheap reconnaissance before committing
  7. Decision procedure
More from Awesome-Journal-Skills
All skills →
About this skill
What does the sigmetrics-topic-selection skill do?

Use when deciding whether a computer-systems performance project belongs at ACM SIGMETRICS or should be routed to IMC, SIGCOMM/NSDI/OSDI, INFOCOM, a learning venue (NeurIPS/ICML), or a performance journal (Performance Evaluation/TON/QUESTA), and when picking the right SIGMETRICS track (Theory / Measurement & Applied Modeling / Learning / Operational Systems).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmetrics-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 984 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