ccs-submission
Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy, per-cycle submission caps, desk-reject triggers, and final-week sequencing.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CCS Submission Use this for a CCS paper submission audit. Reopen the current Call for Papers, the cycle's HotCRP site, the ACM sigconf template, and the ethics policy before giving deadline-ready advice, because CCS rules and dates are set per cycle. ## Submission audit - Confirm the target is the main CCS research track, not a workshop, poster, or the SIGSAC co-located events. - Register the abstract in HotCRP before the registration deadline. CCS requires a mandatory title, author list, abstract, and topics one week before the full-paper deadline; no abstract, no paper. In 2026 registration led the paper deadline by seven days each cycle. - Apply the unaltered ACM `sigconf` two-column template. CCS 2026 set a 12-page main-text limit excluding the bibliography, well-marked appendices, and supplementary material. Whitespace and margin tampering is forbidden and is a desk-reject trigger. - Enforce anonymization: cite your own prior work in the third person, blind references only where third-person phrasing is infeasible, and strip identity from text, PDF metadata, system names, and repository links. - Place the ethics considerations content in a dedicated section (in 2026, an appe
- Submission audit
- Blocking risks
- Desk-reject and triage table
- Final-week sequence for an attack-plus-defense paper
- Format anchors
- Output format
What does the ccs-submission skill do?
Use when auditing an ACM CCS submission for HotCRP readiness, dual-cycle abstract registration and full-paper deadlines, the 12-page ACM sigconf body, anonymization, the ethics considerations appendix, artifact-availability posture, dual-submission policy, per-cycle submission caps, desk-reject triggers, and final-week sequencing.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-submission --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.