Individual skill
ccs-topic-selection
Use when deciding whether a security project fits ACM CCS versus IEEE S&P, USENIX Security, NDSS, PETS, or a crypto/theory venue, identifying the security contribution type, and sharpening the threat model and attacker capability before writing begins.
ACM-CCS-Skills/skills/ccs-topic-selection/SKILL.md
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.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- security Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,789 bytes
Read excerpt
# CCS Topic Selection
Use this before writing. ACM CCS is the SIGSAC flagship: it rewards work with a concrete
attacker, a defensible threat model, and evidence that survives an adversarial program
committee. Decide venue by community and contribution type, never by prestige ranking.
## Fit test
- Prefer CCS when the contribution is a broad computer-security result — a new attack class,
a defense with measured cost, an applied-cryptography protocol, a systems or web-security
mechanism, or a measurement study — aimed at the cross-area SIGSAC community.
- Route to IEEE S&P (Oakland) when the work suits that PC's taste for foundational or
systematization framing and the November cycle fits your calendar better.
- Route to USENIX Security when the contribution is artifact-heavy systems security whose