SkillAgentSearch skills...

ccs-related-work

Use when positioning an ACM CCS submission against the security big-four and specialist literature, including arXiv preprints, prior CCS/S&P/USENIX/NDSS papers, concurrent disclosures, CVE and advisory records, and the attack-and-defense lineage that a SIGSAC program committee expects to see credite…

Install / Use

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

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-related-work

ccs-related-work scores 83/100 on our quality scale, 912th of 1,096 Security 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.

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

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

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

name: ccs-related-work description: Use when positioning an ACM CCS submission against the security big-four and specialist literature, including arXiv preprints, prior CCS/S&P/USENIX/NDSS papers, concurrent disclosures, CVE and advisory records, and the attack-and-defense lineage that a SIGSAC program committee expects to see credited.

CCS Related Work

Use this to audit novelty and eligibility. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors.

Positioning checks

  • Separate a genuine security advance from an engineering increment: a new attack class, a broken assumption, a defense with a new guarantee, or a measurement that overturns received wisdom.
  • Compare against all four top venues, not just CCS. A SIGSAC PC expects the nearest attack or defense from S&P, USENIX Security, and NDSS to be cited and distinguished.
  • Credit the practitioner and disclosure record: relevant CVEs, vendor advisories, and public exploit write-ups count as prior art at CCS even when they are not peer-reviewed papers.
  • Cite arXiv and preprint versions without breaking double-blind review; do not point reviewers to identity-revealing pages or your own advisory.
  • Explain overlap with any concurrent disclosure and do not submit duplicate archival work.
  • Use related work to sharpen the delta: a stronger attacker, a weaker assumption, a lower overhead, a wider measurement, or a defense where prior work had only detection.

Literature-lane table

| Literature lane | Typical sources | What CCS reviewers check | |---|---|---| | Security big four | CCS, IEEE S&P, USENIX Security, NDSS proceedings | Whether the nearest attack/defense is compared or explicitly distinguished | | Specialist venues | PETS/PoPETs, ESORICS, ACSAC, CRYPTO/EUROCRYPT | Whether the sub-community's known results are acknowledged | | Practitioner record | CVEs, vendor advisories, CTF and exploit write-ups | Whether a known real-world case predates the claimed novelty |

A bibliography citing only academic papers while ignoring a well-known CVE that already demonstrated the attack is a recognizable CCS reject pattern that no amount of measurement polish repairs.

Positioning vignette

Imagine the paper reports a new cache side-channel that recovers keys from a TLS library. Its nearest neighbors: an S&P paper with a slower channel, a USENIX defense that assumed the channel was impractical, and a public CVE for a related timing bug. The novelty sentence should name all three contrasts — a faster channel than the S&P line, a break of the USENIX paper's practicality assumption, and a distinct root cause from the CVE.

Concurrent-work judgment calls

  • Independently concurrent arXiv or disclosure work: cite neutrally, state the technical difference, and avoid priority claims reviewers cannot verify.
  • Your own prior workshop or poster version: usually citable and non-archival, but verify against the current CFP wording and phrase the citation to preserve double-blind review.
  • When unsure whether a co-located CCS workshop counts as archival overlap, declare it in the submission form rather than gambling on a chair's reading.

Output format

[Eligibility] clear / needs declaration / risky
[Closest literatures] <big-four / specialist / practitioner record>
[Nearest 3 works] <work -> distinction>
[Archival-overlap risk] <none / issues>
[Novelty sentence] <CCS-ready contribution contrast>

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-related-work — Universal Skill: Install & Safety Check | SkillAgent