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 turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every…
MITAuto-check passed
Install Pldi Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-camera-ready .claude/skills/pldi-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 "pldi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-camera-ready into .claude/skills/pldi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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/PLDI-Skills/skills/pldi-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 pldi-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-camera-ready .agents/skills/pldi-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 "pldi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-camera-ready into .agents/skills/pldi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 pldi-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-camera-ready .cursor/skills/pldi-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 "pldi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-camera-ready into .cursor/skills/pldi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 PLDI-Skills/skills/pldi-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 pldi-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills pldi-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/PLDI-Skills/skills/pldi-camera-ready .gemini/skills/pldi-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 "pldi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-camera-ready into .gemini/skills/pldi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 pldi-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 pldi-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/PLDI-Skills/skills/pldi-camera-ready .github/skills/pldi-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 "pldi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-camera-ready into .github/skills/pldi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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 pldi-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 pldi-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/PLDI-Skills/skills/pldi-camera-ready .opencode/skills/pldi-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 "pldi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/PLDI-Skills/skills/pldi-camera-ready into .opencode/skills/pldi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pldi-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
pldi-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 469 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every…
- Turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization
- SKILL.md covers What changes at acceptance, Open access, concretely, The de-anonymization pass and PACMPL metadata checklist, plus 2 more sections
- Calls git
- Acmsmall journal formatting
What it does
Pldi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every author-response commitment, and coordinating the Zenodo artifact and June conference 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
- Turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization
- Acmsmall journal formatting
- ACM rights and open-access handling
- Delivering every author-response commitment
Example prompts
- “/pldi-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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Pldi Camera Ready loads about 1k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 469 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). 469 words, ~1,039 tokens.
Download SKILL.mdSave it as
.claude/skills/pldi-camera-ready/SKILL.md (or your agent's skills folder).- name
- pldi-camera-ready
- description
- Use when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every author-response commitment, and coordinating the Zenodo artifact and June conference presentation.
PLDI Camera-Ready
Since 2023, "camera-ready" at PLDI means producing a journal article: accepted papers appear as PACMPL (Proceedings of the ACM on Programming Languages), Issue PLDI — Vol 7 for 2023, Vol 8 for 2024, Vol 9 for 2025 (SIGPLAN blog 2022-08-08 and ACM DL, read 2026-07-08). The conference talk in June is downstream of the article, not the other way around: the 2025 wording invited PACMPL Issue PLDI authors to present, without requiring it. Recheck the current instructions — the 2026 camera-ready deadline itself was not visible in accessible renderings (待核实).
What changes at acceptance
| Submission state | Camera-ready state |
|---|---|
| Anonymous, third-person self-citations | Real authors, ORCIDs, affiliations, acknowledgements, grants restored |
| "We will..." sentences in the response | Delivered text, tables, and proofs — reviewers may verify |
| acmsmall draft with review margins | acmsmall with ACM rights block, CCS concepts, and final metadata |
| Code on an anonymous mirror | Artifact heading to Zenodo with a DOI (see pldi-artifact-evaluation) |
| No fee questions | Open-access handling under ACM's model |
Open access, concretely
PACMPL is Gold Open Access. As of the check date: the discounted author-side APC was 400 USD, SIGPLAN covers it for authors who cannot pay, ACM Open institutions owe nothing, and ACM became a fully open-access publisher on January 1, 2026 (dl.acm.org/journal/pacmpl, read 2026-07-08). Verify which regime applies to your institution during the rights workflow rather than budgeting from hearsay, and never route the fee question to a student author alone.
The de-anonymization pass
Do this as a diff, not a rewrite:
git diff submission..camera-ready -- paper/ | grep -E '^\+' | \
grep -viE 'author|orcid|acknowledg|grant|funding|\\cite' && \
echo "WARNING: content drift beyond identity restoration"Legitimate additions: author block, acknowledgements, funding, restored first-person self-citations, and the revisions promised in the author response. Anything else — a new claim, a quietly changed number — needs your shepherd's or the chairs' sign-off. Fix any self-citations that were blinded into vagueness: "prior work [12]" may now become "our earlier analysis [12] which this paper extends," with the delta stated plainly.
Show full SKILL.md (165 more words)Show less
PACMPL metadata checklist
- Title and author order exactly as approved; changes after acceptance go through the chairs, not the production form.
- ORCID for every author; ACM's workflow expects them.
- CCS concepts and keywords chosen by where compiler and PL readers will search, not copied from the template sample.
- Citations to post-2023 SIGPLAN papers in journal form: Proc. ACM Program.
Lang. volume, issue (PLDI/POPL/OOPSLA/ICFP), article number — see
pldi-related-workfor the bibliography discipline. - Every axis label and table caption re-read at final size; the single-column layout is unforgiving of figure text scaled for two columns.
Coordinate the three deliverables
The article, the artifact, and the talk ship on different clocks: the article on the production deadline, the artifact on the AE timetable (Zenodo versioning means no artifact camera-ready deadline), and the talk in June — registration for PLDI 2026 opened March 16, 2026. Name one owner for each clock; the classic failure is a perfect article whose artifact DOI still points at a stale pre-response version.
Output format
[Camera-ready status] on track / blocked
[Response commitments] delivered: n/n, with section pointers
[Identity restoration] author block / ORCID / acknowledgements / self-citations
[Open access] ACM Open covered / APC path / SIGPLAN waiver (verify current terms)
[Clocks] article: <date 待核实> | artifact: <AE timetable> | talk: <June program>© 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 PLDI-Skills/skills/pldi-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Pldi 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 |
|---|---|---|---|---|---|---|
| Pldi Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Turn This Into A Threadsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.4k | 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 |
Similar skills
Turn This Into A Thread
sickn33/agentic-awesome-skills
Turn a long idea, transcript, article or draft into a Twitter/X thread where every tweet stands alone.
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.
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 Pldi Camera Ready
What does Pldi Camera Ready do?
A skill your agent uses when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every…. Pldi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and open-access handling, delivering every author-response commitment, and coordinating the Zenodo artifact and June conference presentation.
When should I use Pldi Camera Ready?
Pldi Camera Ready fits situations like: turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization; acmsmall journal formatting; ACM rights and open-access handling; delivering every author-response commitment.
How do I install Pldi Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-camera-ready -a claude-code`. Or copy the skill folder (PLDI-Skills/skills/pldi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/pldi-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Pldi Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pldi-camera-ready -a codex`. Or copy the skill folder (PLDI-Skills/skills/pldi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/pldi-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Pldi 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 pldi-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/pldi-camera-ready, .gemini/skills/pldi-camera-ready, .github/skills/pldi-camera-ready and .opencode/skills/pldi-camera-ready in your project.
What does Pldi Camera Ready need to run?
Going by SKILL.md and its folder, Pldi Camera Ready needs the command-line tools its instructions call (git).
Does Pldi Camera Ready access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pldi 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 Pldi Camera Ready use?
Pldi 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 Pldi Camera Ready use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Pldi Camera Ready?
Skills that share tags, products or a category with Pldi Camera Ready: QA Acceptance (paperclipai/paperclip, 99k stars), Turn This Into A Thread (sickn33/agentic-awesome-skills, 47k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars) and Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pldi Camera Ready?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.