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.
A skill your agent uses when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue…
MITAuto-check passed
Install Cscw Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-camera-ready .claude/skills/cscw-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 "cscw-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-camera-ready into .claude/skills/cscw-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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/CSCW-Skills/skills/cscw-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 cscw-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-camera-ready .agents/skills/cscw-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 "cscw-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-camera-ready into .agents/skills/cscw-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 cscw-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-camera-ready .cursor/skills/cscw-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 "cscw-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-camera-ready into .cursor/skills/cscw-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 CSCW-Skills/skills/cscw-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 cscw-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-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/CSCW-Skills/skills/cscw-camera-ready .gemini/skills/cscw-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 "cscw-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-camera-ready into .gemini/skills/cscw-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 cscw-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 cscw-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/CSCW-Skills/skills/cscw-camera-ready .github/skills/cscw-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 "cscw-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-camera-ready into .github/skills/cscw-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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 cscw-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 cscw-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/CSCW-Skills/skills/cscw-camera-ready .opencode/skills/cscw-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 "cscw-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-camera-ready into .opencode/skills/cscw-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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
cscw-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 527 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue…
- A CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions
- SKILL.md covers Track 1: the PACMHCI article, Track 2: the conference…, Two-track checklist and Final sweep
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Deanonymizing text and artifacts
What it does
Cscw Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue assignment, and the separate track of presenting at the next CSCW conference.
Its SKILL.md is about 1.2k 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
- A CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions
- Deanonymizing text and artifacts
- ACM journal e-rights and TAPS steps
- Issue assignment
Example prompts
- “/cscw-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
Cscw Camera Ready loads about 1.2k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 527 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). 527 words, ~1,175 tokens.
Download SKILL.mdSave it as
.claude/skills/cscw-camera-ready/SKILL.md (or your agent's skills folder).- name
- cscw-camera-ready
- description
- Use when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue assignment, and the separate track of presenting at the next CSCW conference.
CSCW Camera-Ready and Production
Acceptance at CSCW starts two parallel tracks that most venues fuse into one: the paper becomes a journal article in PACMHCI on ACM's production schedule, and separately the authors are invited to present at the next CSCW conference. Keep the tracks distinct in your planning — the article's publication and the talk's logistics run on different clocks with different owners.
Track 1: the PACMHCI article
Execute the conditions first. Many acceptances arrive as Conditional Accept with Minor Changes: a named list verified before the acceptance is final. Treat the list as a contract — do the items, document where, and resist bundling in unrequested rewrites that could reopen questions.
Deanonymization is a build step, not a find-replace. Reverse every layer the submission masked:
- Restore authors, affiliations, and the acknowledgements section (people, funders, grant numbers) — this is the text most often still missing at the deadline because it never existed in any draft.
- Convert third-person self-citations back to first person where natural.
- Re-point anonymized repository links to the public, attributed release
(
cscw-artifact-evaluation's release build), and verify each resolves. - Revisit setting-level masking deliberately: some community pseudonyms were promised to participants, not merely required by review — those stay. Your consent documents, not the venue, govern what gets unmasked.
ACM production mechanics. Expect journal-standard steps: e-rights/copyright forms, final source preparation through ACM's TAPS pipeline, ORCID for authors, CCS concepts, and accessibility requirements (alt text, tagged PDFs). The precise sequence, deadlines, and any open-access fee treatment for PACMHCI CSCW articles were 待核实 at the 2026-07-08 check — take them from the acceptance email and the live ACM author instructions, not from this file or from CHI-trained habits.
Issue assignment. Historically CSCW papers appeared in paired annual issues (e.g., Vol. 8: CSCW1 April 2024, CSCW2 November 2024). How rolling acceptances map to issues is part of the soft launch — confirm your article's volume/issue/article number when production tells you, then cite yourself accordingly.
Show full SKILL.md (210 more words)Show less
Track 2: the conference presentation
- The rolling CFP's wording is an invitation to present at the next CSCW, pending space — confirm which conference year your paper is assigned to before booking anything. The next edition at check time: CSCW 2026, Salt Lake City, Utah, October 10-14, 2026.
- Registration and attendance obligations (who must register, remote options) were 待核实; verify on the conference site early, because travel budgets and visas move slower than production deadlines.
- Prepare the talk for CSCW's mixed audience: lead with the cooperative practice and the concept, not the pipeline; participant-voice slides need the same paraphrase discipline as the paper.
Two-track checklist
| Item | Track | Owner | Verified against |
|---|---|---|---|
| Minor-change conditions executed and documented | Article | Lead author | Decision letter |
| Deanonymization build (text, links, acknowledgements) | Article | Lead author | Submission-era mask list |
| Consent-bound masks preserved | Article | Ethics owner | Consent forms |
| E-rights, TAPS, ORCID, accessibility | Article | Corresponding author | Live ACM instructions (待核实) |
| Public artifact release live and cited by DOI | Article | Artifact owner | cscw-artifact-evaluation |
| Conference-year assignment confirmed | Talk | Any author | Official email |
| Registration/attendance rules checked | Talk | Presenting author | cscw.acm.org (待核实) |
Final sweep
[Conditions] each acceptance condition → location in final text
[Identity] authors/acks restored; consent-bound pseudonyms intact
[Links] every URL and DOI in the final PDF resolves (run a link check)
[Metadata] title/abstract/author order identical across TAPS, the PDF,
and the artifact release
[Two clocks] production deadline and presentation logistics tracked separatelyThe venue facts here (conference dates, issue anchors) were verified 2026-07-08; production-mechanics items are flagged 待核实 above because ACM instructions arrive with the acceptance and override anything written down in advance.
© 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 CSCW-Skills/skills/cscw-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cscw 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 |
|---|---|---|---|---|---|---|
| Cscw Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Change, Accept or Leave Frameworkkangarooking/cangjie-skill | 11k | — | ~700 | Automated safety check: Pass | MIT | |
| Frost Sequence Camera Orbitheygen-com/hyperframes | 59k | 1 repos | ~9.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
Change, Accept or Leave Framework
kangarooking/cangjie-skill
Helps someone stuck ruminating over an unchangeable situation decide whether to change it, accept it, or leave it, drawn from a chapter of Navalism-style writing.
Frost Sequence Camera Orbit
heygen-com/hyperframes
A ready-made HyperFrames video block where an orbiting camera follows an ice logo that shatters, reforms into two text lines and fades, at 1920×1080.
Phaser 4 Cameras
autonomous-ai/openharness
Guide to cameras in Phaser 4: the CameraManager, main camera, viewport and scroll, zoom, bounds, following sprites, effects, multiple cameras and minimaps.
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 Cscw Camera Ready
What does Cscw Camera Ready do?
A skill your agent uses when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue…. Cscw Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when a CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions, deanonymizing text and artifacts, ACM journal e-rights and TAPS steps, issue assignment, and the separate track of presenting at the next CSCW conference.
When should I use Cscw Camera Ready?
Cscw Camera Ready fits situations like: A CSCW paper is accepted and enters PACMHCI production — executing minor-change conditions; deanonymizing text and artifacts; ACM journal e-rights and TAPS steps; issue assignment.
How do I install Cscw Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-camera-ready -a claude-code`. Or copy the skill folder (CSCW-Skills/skills/cscw-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cscw-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Cscw Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-camera-ready -a codex`. Or copy the skill folder (CSCW-Skills/skills/cscw-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cscw-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Cscw 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 cscw-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/cscw-camera-ready, .gemini/skills/cscw-camera-ready, .github/skills/cscw-camera-ready and .opencode/skills/cscw-camera-ready in your project.
What does Cscw Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Cscw Camera Ready is instructions for the agent only.
Does Cscw 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 Cscw 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 Cscw Camera Ready use?
Cscw 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 Cscw Camera Ready use?
About 1.2k tokens (SKILL.md is roughly 4.7k 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 Cscw Camera Ready?
Skills that share tags, products or a category with Cscw Camera Ready: QA Acceptance (paperclipai/paperclip, 99k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars), Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars) and Change, Accept or Leave Framework (kangarooking/cangjie-skill, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cscw 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.