cscw-artifact-evaluation
Use when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and post-acceptance release, where community-data ethics constrain release more than any badge checklist.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CSCW Artifact Packaging CSCW has no artifact-evaluation committee stamping badges; the "evaluators" of your artifacts are the reviewers deciding whether to trust your methods, and later the researchers and *the studied communities themselves* who encounter the released materials. That second audience is the venue's distinctive constraint: a CSCW artifact release is an act with consequences for real people who never signed your consent form. ## Artifact classes and their release logic | Artifact | Review-time form | Post-acceptance form | Governing constraint | | --- | --- | --- | --- | | Study instruments (guides, surveys) | Anonymized in supplement | Public archive | Institution redaction only | | Codebooks | Anonymized in supplement | Public archive | Paraphrased exemplars only | | Analysis code | Anonymized archive | Public repository + DOI archive | Strip identity from history | | Built systems / prototypes | Screenshots/video + code where feasible | Open source if maintainable | Third-party assets, API keys | | Trace datasets | Aggregates or synthetic sample | Aggregates; raw only if terms + ethics allow | Platform ToS + re-identification risk | | Interview/field data | Neve
- Artifact classes and their release logic
- The community re-identification test
- Minimum viable released package
- Review-time discipline
- Release audit
What does the cscw-artifact-evaluation skill do?
Use when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and post-acceptance release, where community-data ethics constrain release more than any badge checklist.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.