SkillAgentSearch skills...

ccs-workflow

Use when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification, revision, artifact evaluation, ACM camera-ready, and in-person presentation, with backward-planning offsets and the security big…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

83/100

Category

Security

Supported Platforms

Universal

Our assessment of ccs-workflow

ccs-workflow scores 83/100 on our quality scale, 915th of 1,096 Security skills we index.

Its SKILL.md is 4.1 KB long, split into 7 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.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so ccs-workflow 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 found

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.

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-workflow compared with similar skills

All 4 of these similar skills score higher than ccs-workflow; compare them before choosing.

SkillScoreStarsUpdatedFormat
ccs-workflow (this skill)by brycewang-stanford831.2k2mo agoSKILL.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install ccs-workflow?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow. The install tabs above show the steps for each supported agent.
Which AI agents does ccs-workflow 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-workflow 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-workflow still maintained?
The repository was last updated about 2 months ago, so ccs-workflow is actively maintained.

name: ccs-workflow description: Use when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification, revision, artifact evaluation, ACM camera-ready, and in-person presentation, with backward-planning offsets and the security big-four deadline-hopping calendar.

CCS Workflow

Use this as the project-management skill for a CCS submission. CCS is a conference, not a journal: it has no editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Co-Chairs (CCS 2026 Program Co-Chairs: Véronique Cortier and Zhiqiang Lin, reported 2026-07-08; verify against the organizing-committee page). Replace every date below with the current cycle's HotCRP deadlines and work backward.

The dual-deadline cycle

CCS runs two review cycles per year into one conference. A paper enters one cycle only; work rejected in the first cycle may not be resubmitted (even revised) to the second cycle of the same year. Pick the cycle from readiness, not hope — a thin first-cycle submission burns the year at this venue.

  • CCS 2026 (The Hague, Netherlands, Nov 15-19, 2026) Cycle A: abstract registration Jan 7, full paper Jan 14, rebuttal Mar 17-20, notification Apr 9, 2026 (verify).
  • CCS 2026 Cycle B: abstract registration Apr 22, full paper Apr 29, rebuttal Jun 29-Jul 1, notification Jul 17, 2026 (verify). Camera-ready reported Aug 21, 2026.
  • Both 2026 deadlines have passed as of 2026-07-08; treat them as a template and read the CCS 2027 CFP when posted (CCS 2027 host city was still under steering-committee selection).

Milestones

  • Venue fit: confirm the contribution is a broad security result for the SIGSAC PC.
  • Evidence lock: freeze threat model, attack/defense implementation, adaptive evaluation, measurement validation, and the ethics/disclosure posture.
  • Abstract registration: mandatory title, authors, abstract, and topics in HotCRP before the registration deadline; no paper without a registered abstract.
  • Full-paper deadline: upload the anonymized 12-page ACM sigconf PDF plus appendices.
  • Rebuttal window: respond to reviews in the short author-response period.
  • Notification: accept, minor revision (revise within the cycle), or reject.
  • Artifact evaluation: submit artifacts after acceptance for ACM badges if you opt in.
  • Camera-ready and registration: ACM proceedings version, then in-person presentation.

Backward plan from the full-paper deadline

| Weeks out (heuristic) | Attack-plus-defense milestone | |---|---| | 10+ | Threat model frozen, attack primitive working end to end | | 8 | Defense implemented; adaptive attacker designed against it | | 6 | Measurement or evaluation runs complete, environment logged | | 4 | Ethics and responsible-disclosure section drafted, disclosure initiated | | 3 | Full draft in ACM sigconf two-column format | | 2 | Internal red-team read by an adversarial-minded colleague | | 1 | Anonymity sweep, artifact-availability statement, appendix assembly | | 0 | Abstract registered, then full paper in HotCRP |

Anchor every offset to the current cycle, never to a past calendar.

Big-four deadline-hopping

CCS, IEEE S&P, USENIX Security, and NDSS run rolling multi-cycle deadlines, so a paper rejected in one can often be reworked into the next open venue within weeks. Keep a live map: a CCS Cycle A reject in April can target USENIX Security or the next NDSS cycle rather than waiting a year. Never resubmit unchanged — reviewers rotate across all four venues.

Coordination notes

  • Assign one owner for the ethics/disclosure section and another for the anonymity sweep; shared ownership is how both slip.
  • Archive the exact submitted PDF and appendices, since rebuttal replies must quote them.

Output format

[Current stage] idea / building / writing / abstract / submission / rebuttal / accepted / artifact
[Cycle] A / B and next official deadline (date + source, or unknown)
[Critical path] <three tasks that determine readiness>
[Risk register] <threat-model / anonymity / ethics / evidence / artifact / presentation>
[Owner map] <task -> person or role>

Related Skills

View on GitHub
GitHub Stars1.2k
CategorySecurity
Updated2mo ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
ccs-workflow — Universal Skill: Install & Safety Check | SkillAgent