cscw-supplementary
Use when assembling supplementary materials for a CSCW submission — appendices, codebooks, interview guides, survey instruments, analysis code, and data extracts — deciding what accompanies a journal-model paper, anonymized end to end and consistent across R&R rounds.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-supplementary --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 Supplementary Materials Supplements at CSCW serve a journal-style review: they let reviewers *verify* the methods section without bloating a paper already policed by the contribution-vs- length standard. Because Revise and Resubmit sends the paper back to the same reviewers, the supplement is also a **versioned record** — round-two reviewers can and do compare it against round one. ## What goes where | Material | Main paper | Appendix | Separate supplement file | | --- | --- | --- | --- | | Method summary + key instrument excerpts | ✓ | | | | Full interview guide / survey instrument | | ✓ | ✓ if long | | Codebook (definitions + paraphrased exemplars) | | ✓ | ✓ | | Trace-pipeline ledger and attrition table | summary | ✓ | code as archive | | Analysis scripts | | | ✓ (archive) | | Additional tables/robustness checks | | ✓ | ✓ | | Consent forms / recruitment text | | | ✓ | | Raw transcripts, identifiable data | never | never | never | Decision rule: **anything a reviewer needs to evaluate a claim belongs in the paper or appendix; anything a reviewer needs to *trust* the method belongs in the supplement; anything participants did not consent to share belongs nowhere.** ## Anonym
- What goes where
- Anonymization is deeper than the PDF
- R&R versioning discipline
- Pre-upload checklist
strings that must not appear anywhere in the supplement tree grep -ri -l -E "(surname|firstname|university-name|lab-name|grant-no|protocol-no)" supplement/ metadata in every PDF for f in supplement/**/*.pdf; do exiftool "$f" | grep -iE "author|creator|company"; done accidental git history or user paths in code archives find supplement/ -name ".git" -o -path "*Users*" -o -path "*home*" | head
What does the cscw-supplementary skill do?
Use when assembling supplementary materials for a CSCW submission — appendices, codebooks, interview guides, survey instruments, analysis code, and data extracts — deciding what accompanies a journal-model paper, anonymized end to end and consistent across R&R rounds.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-supplementary --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.