Digital Forensics
sickn33/agentic-awesome-skills
Authorized digital forensics: memory dumps, disk timelines, PCAP investigation, artifact triage, and incident-response evidence preservation.
A skill your agent uses when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge…
MITAuto-check passed
Install Ccs Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-camera-ready --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-camera-ready .claude/skills/ccs-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-camera-ready into .claude/skills/ccs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-camera-ready", 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-camera-readyType 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-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-camera-ready --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-camera-ready .agents/skills/ccs-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-camera-ready into .agents/skills/ccs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-camera-ready", 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-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-camera-ready --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-camera-ready .cursor/skills/ccs-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-camera-ready into .cursor/skills/ccs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-camera-ready", 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-camera-ready--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-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ccs-camera-ready --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-camera-ready .gemini/skills/ccs-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-camera-ready into .gemini/skills/ccs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-camera-ready", 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-camera-readyInstalls 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-camera-ready -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-camera-ready .github/skills/ccs-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-camera-ready into .github/skills/ccs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-camera-ready", 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-camera-ready -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-camera-ready --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-camera-ready .opencode/skills/ccs-camera-ready && 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-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ACM-CCS-Skills/skills/ccs-camera-ready into .opencode/skills/ccs-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ccs-camera-ready", 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-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 442 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge…
- Preparing an accepted ACM CCS paper for the ACM Digital Library proceedings
- SKILL.md covers Camera-ready audit, Badge placement map, De-anonymization sweep and ACM proceedings reflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering de-anonymization
What it does
Ccs Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge placement from artifact evaluation, incorporation of shepherd and minor-revision requirements, disclosure-timing coordination, registration, and in-person presentation.
Its SKILL.md is about 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
- Preparing an accepted ACM CCS paper for the ACM Digital Library proceedings
- Covering de-anonymization
- The ACM sigconf final format
- ACM rights and eRights forms
Example prompts
- “/ccs-camera-ready”
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 Camera Ready loads about 1k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 442 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). 442 words, ~1,030 tokens.
Download SKILL.mdSave it as
.claude/skills/ccs-camera-ready/SKILL.md (or your agent's skills folder).- name
- ccs-camera-ready
- description
- Use when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge placement from artifact evaluation, incorporation of shepherd and minor-revision requirements, disclosure-timing coordination, registration, and in-person presentation.
CCS Camera Ready
Use this after acceptance or after clearing a minor revision. Reopen the current CCS camera-ready instructions, the ACM rights form, the registration page, and the notification or shepherd email before advising authors.
Camera-ready audit
- Convert the anonymous submission to the public proceedings version: author names, affiliations, acknowledgements, funding, and artifact links restored.
- Apply the ACM
sigconffinal template and the ACM rights-management block; the DOI, the conference reference string, and the copyright notice come from the ACM eRights system. - Incorporate exactly what the shepherd or the minor-revision decision required, without expanding the contribution beyond what was reviewed.
- Place any artifact-evaluation badges earned (Available, Functional, Reusable, Results Reproduced) as instructed; badge placement is part of the ACM camera-ready workflow.
- Confirm the final title and abstract match the HotCRP-registered title and abstract if the cycle froze them at registration.
- Coordinate disclosure timing: the public proceedings version and any released exploit or advisory should not appear before the agreed vendor-disclosure date.
Badge placement map
| Badge earned in artifact evaluation | Where it goes | What to confirm |
|---|---|---|
| Artifacts Available | First page, with the archival DOI/URL | The archive is public and permanent before camera-ready |
| Artifacts Evaluated - Functional | First page | The committee's functional result is final |
| Artifacts Evaluated - Reusable | First page | Documentation matches the reusable claim |
| Results Reproduced | First page | The reproduced results match the camera-ready numbers |
De-anonymization sweep
- Restore the author block, acknowledgements, grants, and contribution statements the anonymous version stripped.
- Rewrite third-person self-citations into natural first person where it improves clarity.
- Replace anonymized repository placeholders with the public, licensed, archived artifact and test every link from a logged-out browser.
- Re-check that de-anonymizing did not silently reveal an embargoed vendor before its patch.
Show full SKILL.md (162 more words)Show less
ACM proceedings reflow
- Switching from the submission build to the final
sigconfbuild changes spacing; recheck every page break, protocol figure, and wide result table after adding the author block. - Material that fit the 12-page anonymous body can overflow once affiliations, acknowledgements, and the rights block are added; confirm the final length against the camera-ready page instruction rather than assuming.
- Keep theorem, protocol, and section numbering identical to the reviewed version so the meta-review and shepherd record stay traceable.
Worked example: integrating a shepherd requirement
The shepherd asked that the adaptive-attack results move from the appendix into the main evaluation. Camera-ready move: promote the adaptive table into Section 6, add one sentence interpreting the degraded defense numbers honestly, and leave the full attack derivation in the appendix — without strengthening any claim the reviewers did not see.
Hedged logistics
- Registration pricing, the exact camera-ready and rights-form deadlines, and badge-placement mechanics change every cycle; confirm against the notification email and current instructions.
Output format
[Camera-ready status] Ready / Needs fixes / Blocked
[Final package] <PDF / source / bib / ACM rights form / badges / artifacts>
[Policy checks] <format / authors / disclosure timing / registration / presentation>
[Reviewer-change map] <shepherd/revision requirement -> final edit>
[Remaining owner] <person -> task>© 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-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ccs Camera Ready 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 Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Digital Forensicssickn33/agentic-awesome-skills | 47k | 1 repos | ~495 | Automated safety check: Pass | MIT | |
| Digital Forensicszhaoxuya520/reverse-skill | 40k | 2 repos | ~389 | Automated safety check: Warn | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Ccs Alignthedotmack/claude-mem | 99k | — | ~6.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Digital Forensics
zhaoxuya520/reverse-skill
A skill your agent uses for authorized digital forensics including memory dumps, disk timelines, PCAP investigation, artifact triage, and IR evidence preservation.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
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…
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
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 Camera Ready
What does Ccs Camera Ready do?
A skill your agent uses when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge…. Ccs Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge placement from artifact evaluation, incorporation of shepherd and minor-revision requirements, disclosure-timing coordination, registration, and in-person presentation.
When should I use Ccs Camera Ready?
Ccs Camera Ready fits situations like: preparing an accepted ACM CCS paper for the ACM Digital Library proceedings; covering de-anonymization; the ACM sigconf final format; ACM rights and eRights forms.
How do I install Ccs Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-camera-ready -a claude-code`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ccs-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Ccs Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ccs-camera-ready -a codex`. Or copy the skill folder (ACM-CCS-Skills/skills/ccs-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ccs-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Ccs Camera Ready 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-camera-ready -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-camera-ready, .gemini/skills/ccs-camera-ready, .github/skills/ccs-camera-ready and .opencode/skills/ccs-camera-ready in your project.
What does Ccs Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Ccs Camera Ready is instructions for the agent only.
Does Ccs Camera Ready 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 Camera Ready 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 Camera Ready use?
Ccs Camera Ready 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 Camera Ready use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Camera Ready?
Skills that share tags, products or a category with Ccs Camera Ready: Digital Forensics (sickn33/agentic-awesome-skills, 47k stars), Digital Forensics (zhaoxuya520/reverse-skill, 40k stars), Audit Preparation (sickn33/agentic-awesome-skills, 47k stars) and QA Acceptance (paperclipai/paperclip, 99k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ccs Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.