Agent skill · Code Review & Quality

ieeesp-camera-ready

Use when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section, de-anonymizing and restoring disclosure specifics, IEEE compsoc and Xplore requirements, and coordinating artifact submission.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-camera-ready --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: IEEE-SP-Skills/skills/ieeesp-camera-ready/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# IEEE S&P Camera-Ready Use this after an Accept decision. S&P's camera-ready is not a formatting pass: acceptance arrives with a **draft meta-review listing remaining concerns and a shepherd who strikes each concern only when the revision resolves it** (2027 CFP, checked 2026-07-08). The camera-ready is the last reviewed artifact of the cycle. ## Working the shepherding loop 1. Convert the draft meta-review into a numbered concern ledger on day one. 2. For each concern, agree internally on: the change, its location, and the one-line evidence the shepherd can check. 3. Ask the shepherd early about any concern you believe is out of scope or wrong — negotiation happens at the start, not at the deadline. 4. Submit the revision with a concern → change → location map; make the strike-through decision mechanical for the shepherd. 5. Nothing in the shepherding loop authorizes *new* claims: the accepted contribution is the contribution. | Shepherd asks for | Right-sized response | |---|---| | Tone down claim X | Rewrite the claim to the evaluated boundary; show old/new text | | Add limitation discussion | A titled paragraph, referenced from the intro | | Clarify threat model edge | Amend §

What's inside
Steps it walks through
  1. Working the shepherding loop
  2. The ethics section is added now — and does not count
  3. De-anonymization with security-specific restorations
  4. IEEE mechanics
  5. Sequence to the deadline
  6. Common failures at this stage
  7. Output format
Commands it runs
Residue sweep after de-anonymization
pdftotext final.pdf - | grep -inE 'anonym|redacted|omitted for (review|anonymity)|Vendor [A-Z]\b'
pdfinfo final.pdf | grep -iE 'title|author'   # metadata now correct, not blank
grep -rn 'REPLACE-AFTER-ACCEPT' . || true
More from Awesome-Journal-Skills
All skills →
About this skill
What does the ieeesp-camera-ready skill do?

Use when converting an IEEE S&P (Oakland) acceptance into a final paper, including working the shepherd against the draft meta-review's concern list, adding the ethics section, de-anonymizing and restoring disclosure specifics, IEEE compsoc and Xplore requirements, and coordinating artifact submission.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-camera-ready --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.

Keep going