Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
A skill your agent uses when preparing a SOSP camera-ready after acceptance, working with an assigned shepherd toward the final deadline, expanding from the 12-page submission to the 13-page final…
MITAuto-check passed
Install Sosp Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-camera-ready .claude/skills/sosp-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 "sosp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-camera-ready into .claude/skills/sosp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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/SOSP-Skills/skills/sosp-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 sosp-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-camera-ready .agents/skills/sosp-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 "sosp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-camera-ready into .agents/skills/sosp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-camera-ready .cursor/skills/sosp-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 "sosp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-camera-ready into .cursor/skills/sosp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 SOSP-Skills/skills/sosp-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 sosp-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-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/SOSP-Skills/skills/sosp-camera-ready .gemini/skills/sosp-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 "sosp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-camera-ready into .gemini/skills/sosp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-camera-ready .github/skills/sosp-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 "sosp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-camera-ready into .github/skills/sosp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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 sosp-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 sosp-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/SOSP-Skills/skills/sosp-camera-ready .opencode/skills/sosp-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 "sosp-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-camera-ready into .opencode/skills/sosp-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-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
sosp-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 606 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing a SOSP camera-ready after acceptance, working with an assigned shepherd toward the final deadline, expanding from the 12-page submission to the 13-page final…
- Works in 3 steps: Clarifications the reviews showed were… → Evaluation context reviewers asked for… → Honest-limitations text that the PC…
- Preparing a SOSP camera-ready after acceptance
- SKILL.md covers Shepherding is the center of…, The extra page is for…, De-anonymization checklist and ACM proceedings mechanics, plus 2 more sections
- Calls pdftotext
What it does
Sosp Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing a SOSP camera-ready after acceptance, working with an assigned shepherd toward the final deadline, expanding from the 12-page submission to the 13-page final limit (14 with shepherd approval), de-anonymizing safely, adding artifact badges, and meeting ACM proceedings requirements.
Its SKILL.md is about 1.3k 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
- Preparing a SOSP camera-ready after acceptance
- Working with an assigned shepherd toward the final deadline
- Expanding from the 12-page submission to the 13-page final limit (14 with shepherd approval)
- De-anonymizing safely
Example prompts
- “/sosp-camera-ready”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Clarifications the reviews showed were needed — misread invariants, buried
- Evaluation context reviewers asked for that the submitted runs already support.
- Honest-limitations text that the PC meeting surfaced.
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:
pdftotext
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
Sosp Camera Ready loads about 1.3k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 606 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). 606 words, ~1,291 tokens.
Download SKILL.mdSave it as
.claude/skills/sosp-camera-ready/SKILL.md (or your agent's skills folder).- name
- sosp-camera-ready
- description
- Use when preparing a SOSP camera-ready after acceptance, working with an assigned shepherd toward the final deadline, expanding from the 12-page submission to the 13-page final limit (14 with shepherd approval), de-anonymizing safely, adding artifact badges, and meeting ACM proceedings requirements.
SOSP Camera-Ready
Use this between a SOSP acceptance notification and the final-version deadline. The 2026-cycle anchors (verified 2026-07-08 on the sosp26 HotCRP deadlines page and the official author guidelines): notification July 3, 2026; camera-ready due August 28, 2026; final papers may use 13 pages of technical content, and the shepherd may approve one additional page for a 14-page maximum. References remain uncounted. Proceedings are published in the ACM Digital Library.
Shepherding is the center of this phase
Accepted SOSP papers are shepherded: a PC member is assigned to see the revision through, and the shepherd's sign-off — including on the optional 14th page — gates the camera-ready. Treat the shepherd as the PC's delegate, not as a copy editor.
- Within days of notification, send the shepherd a revision plan: every substantive reviewer concern, what will change in the text, and what will not change with a one-line reason. Get agreement on scope before rewriting.
- Batch questions; shepherds are volunteers working around their own deadlines.
- If you want the extra page, ask early with a concrete use ("the failure-model discussion Rev C requested needs ~0.7 pages"), not at upload time.
- Disagreements about a requested change go through the shepherd to the chairs; never silently skip an agreed item — shepherds diff drafts.
The extra page is for reviewers' concerns
The jump from 12 submitted pages to 13 (or 14) exists so the discussion-phase concerns can be addressed with substance. Spend it in priority order:
- Clarifications the reviews showed were needed — misread invariants, buried assumptions, undefined workload details.
- Evaluation context reviewers asked for that the submitted runs already support.
- Honest-limitations text that the PC meeting surfaced.
Do not spend it on new claims: results that were never reviewed, added to the final version, are how camera-ready papers acquire post-publication trouble.
De-anonymization checklist
The submitted PDF carried a paper ID and scrubbed context; reversing that has sharp edges:
| Restore | Watch out for |
|---|---|
| Author block, affiliations, emails | Order and spelling final — the DL metadata is generated from this |
| Acknowledgments and funding | Grant numbers your funder requires verbatim |
| Real system and organization names | Employer/legal approval for deployment details that were generalized for review |
| First-person references to your prior work | Rewrite the third-person camouflage so citations read naturally |
| Repository and artifact URLs | Point at the archival artifact (see sosp-artifact-evaluation), not a moving main branch |
# Confirm no review-phase debris survives in the final PDF
pdftotext final.pdf - | grep -inE 'paper ?#?[0-9]{2,4}|anonym|double.blind|under submission' | head
pdfinfo final.pdf | grep -iE '^(author|title)' # metadata should now be realShow full SKILL.md (218 more words)Show less
ACM proceedings mechanics
- The ACM rights form arrives per-paper by email after acceptance; the completed rights block text and DOI must be placed in the paper exactly as issued. The title and author list on the form must match the PDF character for character.
- ORCID and author-profile linkage happen through the ACM submission pipeline; make sure every co-author completes their part before the deadline, since one missing rights confirmation blocks the whole paper.
- Artifact badges earned through evaluation are rendered on the DL page and may be stamped on the paper; coordinate badge placement with the camera-ready timeline rather than re-opening the PDF after upload. Exact form names and TAPS/workflow details vary by year — 待核实 against the acceptance-email instructions rather than assumed from this file.
Sequencing against artifact evaluation and the conference
August is crowded: the camera-ready, the artifact-evaluation window, and conference logistics (registration, visas for the host country, talk preparation) all run in parallel. Assign different owners to the shepherd thread and the AE thread — both are interactive, deadline-bound conversations, and one person context-switching between them drops messages. Book travel for the conference (Sep 29 - Oct 2, 2026 in Prague for the 2026 edition) as soon as acceptance is firm; attendance and presentation expectations for the current year are stated in acceptance materials, not guessed.
Output format
[Camera-ready stage] plan agreed / revising / shepherd review / uploaded
[Page budget] 13 base + 14th requested? granted? <use>
[Revision map] <reviewer concern -> change or agreed no-change>
[De-anonymization] complete / pending items
[ACM mechanics] rights form / metadata match / badges / ORCID
[Parallel threads] AE owner, travel, talk© 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 SOSP-Skills/skills/sosp-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sosp 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 |
|---|---|---|---|---|---|---|
| Sosp Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Release PreparationCherryHQ/cherry-studio | 53k | — | ~4.3k | Automated safety check: Pass | AGPL-3.0 | |
| 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 |
Similar skills
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.
Release Preparation
CherryHQ/cherry-studio
Prepares a Cherry Studio release by resolving the version, collecting commits, writing bilingual release notes, updating version files and creating a release branch.
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.
Prepare Paperclip PR
paperclipai/paperclip
Prepare a Paperclip branch for PR with commits, template body, and checks.
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 Sosp Camera Ready
What does Sosp Camera Ready do?
A skill your agent uses when preparing a SOSP camera-ready after acceptance, working with an assigned shepherd toward the final deadline, expanding from the 12-page submission to the 13-page final…. Sosp Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing a SOSP camera-ready after acceptance, working with an assigned shepherd toward the final deadline, expanding from the 12-page submission to the 13-page final limit (14 with shepherd approval), de-anonymizing safely, adding artifact badges, and meeting ACM proceedings requirements.
When should I use Sosp Camera Ready?
Sosp Camera Ready fits situations like: preparing a SOSP camera-ready after acceptance; working with an assigned shepherd toward the final deadline; expanding from the 12-page submission to the 13-page final limit (14 with shepherd approval); de-anonymizing safely.
How do I install Sosp Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-camera-ready -a claude-code`. Or copy the skill folder (SOSP-Skills/skills/sosp-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sosp-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Sosp Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-camera-ready -a codex`. Or copy the skill folder (SOSP-Skills/skills/sosp-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sosp-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Sosp 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 sosp-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/sosp-camera-ready, .gemini/skills/sosp-camera-ready, .github/skills/sosp-camera-ready and .opencode/skills/sosp-camera-ready in your project.
What does Sosp Camera Ready need to run?
Going by SKILL.md and its folder, Sosp Camera Ready needs the command-line tools its instructions call (pdftotext).
Does Sosp 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 Sosp 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 Sosp Camera Ready use?
Sosp 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 Sosp Camera Ready use?
About 1.3k tokens (SKILL.md is roughly 5.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 Sosp Camera Ready?
Skills that share tags, products or a category with Sosp Camera Ready: Audit Preparation (sickn33/agentic-awesome-skills, 47k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Release Preparation (CherryHQ/cherry-studio, 53k stars) and Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sosp 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.