ccs-supplementary
Use when preparing ACM CCS appendices and supplementary material, including the ethics considerations appendix, protocol transcripts, formal proofs, measurement tables, and anonymized supporting material under the 12-page body limit, anonymity, and reviewer-discretion constraints for a security pape…
Install / Use
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-supplementaryInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
SecuritySupported Platforms
Our assessment of ccs-supplementary
ccs-supplementary scores 83/100 on our quality scale, 913th of 1,096 Security skills we index.
Its SKILL.md is 3.6 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-supplementary 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-supplementary compared with similar skills
All 4 of these similar skills score higher than ccs-supplementary; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ccs-supplementary (this skill)by brycewang-stanford | 83 | 1.2k | 2mo ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 4d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 56d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install ccs-supplementary?
- Run
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-supplementary. The install tabs above show the steps for each supported agent. - Which AI agents does ccs-supplementary work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ccs-supplementary 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-supplementary still maintained?
- The repository was last updated about 2 months ago, so ccs-supplementary is actively maintained.
Skill content
View source on GitHubname: ccs-supplementary description: Use when preparing ACM CCS appendices and supplementary material, including the ethics considerations appendix, protocol transcripts, formal proofs, measurement tables, and anonymized supporting material under the 12-page body limit, anonymity, and reviewer-discretion constraints for a security paper.
CCS Supplementary
Use this when assembling CCS appendices and supplementary material. At CCS the main 12-page body must let reviewers judge novelty and soundness on its own; appendices support it but the committee is not obligated to read them.
Supplement structure
- Put formal proofs, full protocol transcripts, extra measurements, and additional evaluation tables in well-marked appendices after the bibliography.
- Place the ethics considerations content where the CFP directs it. CCS 2026 required a dedicated ethics section as an appendix after the 12-page body and the bibliography for work touching human subjects, user data, or real-world vulnerabilities.
- Keep every supplementary file double-blind: no authors, institutions, acknowledgements, private paths, repository owners, or identifying metadata, including in code and datasets.
- Do not hide the core threat model, the main attack description, the headline defense, or the primary evidence in an appendix; a paper whose contribution is only legible with the appendix reads as unreviewable within the page limit.
- Verify archives open on a clean machine and carry no credentials, cache directories, or OS metadata that leaks identity.
Appendix architecture for a security paper
- Order appendix sections to mirror the body: threat model details, then proofs, then extended attack variants, then measurement tables, then the ethics section where required.
- Restate each theorem or protocol step before its full derivation so the appendix reads standalone without flipping back to the two-column body.
- Cross-reference every appendix table and proof from the body at least once; orphaned material is invisible under reviewer discretion.
- Keep the ethics section self-contained: disclosure timeline, harm-minimization steps, IRB or ERB status, and the reasoning, so the ethics reviewer can grade it without hunting.
What gets opened first
| Supplement item | Inspection likelihood | Practical implication | |---|---|---| | Ethics considerations section | High for sensitive work | Write it to stand alone and answer the obvious concern | | Proof of the headline security guarantee | High for crypto/formal papers | Polish it to main-text standard | | Extended attack variants and measurements | Medium | Reference each one from the body | | Code and data archive | Variable, reviewer discretion | The README must orient a reader in one minute |
Vignette: splitting a protocol-security paper
A submission proving a key-exchange protocol secure, plus an implementation and overhead plots: the body keeps the threat model, the protocol, the main security theorem with a sketch, and the overhead figure; the appendix holds the full proof, the message-level transcript, and the ethics note on the disclosed implementation bug; the archive carries the reference implementation and test vectors. Nothing decision-critical lives only in the archive, because archive inspection is discretionary.
Output format
[Supplement status] Ready / Needs fixes / Not ready
[Files] <appendix / proofs / ethics section / code / data>
[Ethics section] present / required-and-missing / not-applicable
[Anonymity checks] passed / issues
[Main-paper dependency] <what breaks if the appendix is ignored>
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
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.
