Individual skill

ccs-reproducibility

Use when strengthening ACM CCS reproducibility evidence, including the artifact-availability posture, threat-model-to-evidence mapping, attack reproduction steps, defense overhead measurement, measurement-dataset provenance, environment and version pinning, and honest justification when artifacts cannot be shared.

ACM-CCS-Skills/skills/ccs-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,411
Repository last updated: Sep 27, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

academic-writing Repository topic
agent-skills Repository topic
journal Repository topic
academic-research Repository topic
ai-agents Repository topic
anthropic Repository topic
awesome-list Repository topic
claude Repository topic
claude-code Repository topic
economics Repository topic
security Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 3,618 bytes

Read excerpt


# CCS Reproducibility

Use this before submission and again before the artifact-evaluation deadline. Reopen the
current CFP and call for artifacts to confirm what availability statement and packaging CCS
expects this cycle.

## Evidence map

- Map each security claim — every attack, defense guarantee, and measurement result — to a
  verifiable location: a script, a config, a dataset, a proof, or a logged run.
- For attacks, record the target's exact version and configuration, the attacker's resource
  budget, and the sequence of steps that reproduce the exploit.
- For defenses, record the workload, the overhead-measurement method, the hardware, and the
  adaptive attacker used, so the cost-versus-security tradeoff can be rechecked.