Ccs Align
thedotmack/claude-mem
Run the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → getobservations, land them in a seat-owned middle…
A skill your agent uses when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification…
MITAuto-check passed
Install Ccs Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-workflow .claude/skills/ccs-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ccs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-workflow into .claude/skills/ccs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-workflow .agents/skills/ccs-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ccs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-workflow into .agents/skills/ccs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-workflow .cursor/skills/ccs-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ccs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-workflow into .cursor/skills/ccs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ACM-CCS-Skills/skills/ccs-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-workflow .gemini/skills/ccs-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ccs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-workflow into .gemini/skills/ccs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-workflow .github/skills/ccs-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ccs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-workflow into .github/skills/ccs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ACM-CCS-Skills/skills/ccs-workflow .opencode/skills/ccs-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ccs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-workflow into .opencode/skills/ccs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ccs-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 496 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification…
- Planning an ACM CCS project timeline across the two HotCRP review cycles
- SKILL.md covers The dual-deadline cycle, Milestones, Backward plan from the… and Big-four deadline-hopping, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- From venue fit through abstract registration
What it does
Ccs Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning an ACM CCS project timeline across the two HotCRP review cycles
- From venue fit through abstract registration
- Full-paper upload
- Artifact evaluation
Example prompts
- “/ccs-workflow”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ccs Workflow loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 496 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 496 words, ~1,060 tokens.
Download SKILL.mdSave it as
.claude/skills/ccs-workflow/SKILL.md (or your agent's skills folder).- 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.
Show full SKILL.md (188 more words)Show less
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>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ACM-CCS-Skills/skills/ccs-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ccs Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ccs Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ccs Alignthedotmack/claude-mem | 99k | — | ~6.1k | Automated safety check: Pass | Apache-2.0 | |
| Project Timeline Reportthedotmack/claude-mem | 99k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Ccs Workflow
What does Ccs Workflow do?
A skill your agent uses when planning an ACM CCS project timeline across the two HotCRP review cycles, from venue fit through abstract registration, full-paper upload, rebuttal, notification…. Ccs Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Ccs Workflow?
Ccs Workflow fits situations like: planning an ACM CCS project timeline across the two HotCRP review cycles; from venue fit through abstract registration; full-paper upload; artifact evaluation.
How do I install Ccs Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a claude-code`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ccs-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Ccs Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a codex`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ccs-workflow in your project. Codex loads it when a task matches its description.
Can I use Ccs Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ccs-workflow, .gemini/skills/ccs-workflow, .github/skills/ccs-workflow and .opencode/skills/ccs-workflow in your project.
What does Ccs Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Ccs Workflow is instructions for the agent only.
Does Ccs Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ccs Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ccs Workflow use?
Ccs Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ccs Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ccs Workflow?
Skills that share tags, products or a category with Ccs Workflow: Ccs Align (thedotmack/claude-mem, 99k stars), Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars) and Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ccs Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.