cs-venue-strategy

CS Venue Strategy

Computer science venues reward different contribution shapes. Use this skill to choose a realistic target and adapt the paper's evidence, tone, and framing.

Read First

• references/repository-contract.md
• references/venue-strategy-policy.md
• references/research-positioning-policy.md

Workflow

1. Identify field and subfield: ML, NLP, HCI, systems, SE, security, databases, IR, theory, PL, robotics, graphics, education, or interdisciplinary CS.
2. List plausible venues and tracks with deadlines, format, review model, and artifact expectations.
3. Compare audience fit, novelty bar, methodological norms, page limits, and risk.
4. Map contribution type to venue expectations.
5. Record the decision in docs/venue/venue-strategy.md.
6. Update paper/research design if venue fit requires stronger baselines, clearer theory, user study, artifact, or threat analysis.

Venue Fit Checks

• Does the venue value this contribution type?
• Are the baselines and datasets credible for this venue?
• Does the paper need artifact evaluation or reproducibility badges?
• Is the novelty claim too incremental for the main track?
• Would a workshop, demo, findings track, or journal be more honest?

Do Not

• Choose a venue only by prestige.
• Ignore track-specific review criteria.
• Reframe after experiments without checking whether evidence still supports the claim.