ccs-review-process
Use when explaining or planning around ACM CCS peer review, the two-cycle HotCRP workflow, decision categories including minor revision, the rebuttal window, the adversarial reviewer pool, ethics and disclosure scrutiny, meta-review dynamics, and ACM proceedings outcomes.
Install / Use
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-review-processInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of ccs-review-process
ccs-review-process scores 83/100 on our quality scale, 2215th of 2,769 Automation skills we index.
Its SKILL.md is 3.4 KB long, split into 6 sections with 1 code example: a solid amount of guidance for an agent.
With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ccs-review-process is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ccs-review-process compared with similar skills
All 4 of these similar skills score higher than ccs-review-process; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ccs-review-process (this skill)by brycewang-stanford | 83 | 1.2k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.7k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 82.0k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.9k | today | MCP Server |
Frequently asked questions
- How do I install ccs-review-process?
- Run
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-review-process. The install tabs above show the steps for each supported agent. - Which AI agents does ccs-review-process work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ccs-review-process safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ccs-review-process still maintained?
- The repository was last updated about 2 months ago, so ccs-review-process is actively maintained.
Skill content
View source on GitHubname: ccs-review-process description: Use when explaining or planning around ACM CCS peer review, the two-cycle HotCRP workflow, decision categories including minor revision, the rebuttal window, the adversarial reviewer pool, ethics and disclosure scrutiny, meta-review dynamics, and ACM proceedings outcomes.
CCS Review Process
Use this to reason about review-stage strategy. Reopen the current CFP, the cycle's HotCRP site, the reviewer guidelines if posted, and the ethics policy before making process claims.
Process model
- CCS runs two review cycles per year on HotCRP, each with abstract registration, full-paper submission, review, a rebuttal window, and notification.
- Reviewers assess threat-model soundness, novelty, technical correctness, evidence quality, ethics and responsible disclosure, and significance to the security community.
- Decisions are not binary: CCS 2026 used accept, minor revision (authors revise for the same cycle under a shepherd or check), and reject. A first-cycle reject cannot return that year.
- An ethics or disclosure concern can sink an otherwise strong paper; the ethics reviewer's view carries weight independent of technical scores.
- Accepted papers publish in the ACM Digital Library proceedings, so camera-ready and metadata compliance matter as much as the initial decision.
Who reviews here
- The pool is adversarial by training: expect at least one reviewer to attack your threat model, look for the assumption that makes the attack easy, and probe whether the defense was tested against an adaptive attacker.
- CCS is broad, so a paper may draw reviewers from an adjacent sub-area; the threat model and intro must orient a web-security reviewer to a crypto result and vice versa.
- Borderline papers usually fall on one of three edges: an attacker assumption too strong to be interesting, a defense never adapted against, or an ethics gap left unaddressed.
Scoring leverage table
| Review dimension | What raises it | What sinks it | |---|---|---| | Threat model | A tight, realistic adversary stated up front | Capabilities that quietly grow to make the attack work | | Novelty | An attack class or guarantee the literature lacked | An increment over a cited paper with no new idea | | Evidence | End-to-end demonstration against a real target | Lab-only results against a strawman | | Ethics | Disclosure done, harm minimized, reasoned in the paper | Real-world harm with no disclosure or IRB reasoning |
Stage-by-stage realism
- Initial reviews: triage by what the meta-reviewer will weigh — threat model and evidence — not by reviewer tone.
- Rebuttal: the window is short and structured; one crisp answer to the decision-critical objection beats an exhaustive point-by-point.
- Decision: the meta-review synthesizes; one unresolved threat-model or ethics objection outweighs several resolved clarity complaints.
- Minor revision: treat it as conditional acceptance with a checklist, not a debate; do exactly what the shepherd asks within the cycle's timeline.
Output format
[Current stage] submitted / reviews / rebuttal / decision / revision / camera-ready
[Decision actors] <reviewers / ethics reviewer / meta-reviewer / chairs>
[Likely leverage] <threat model / novelty / evidence / ethics>
[Forbidden moves] <identity leak / new unsupported results / ignoring the shepherd>
[Next response move] <one action>
Related Skills
Agent-Reach
112.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.0k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.9k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
