Iso27001 Audit Prep
alirezarezvani/claude-skills
/cs:iso27001-audit-prep <scope — ISO 27001 ISMS audit readiness 6-question forcing interrogation.
A skill your agent uses when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references…
MITAuto-check passed
Install Sosp Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-submission --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-submission .claude/skills/sosp-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-submission into .claude/skills/sosp-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-submission --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-submission .agents/skills/sosp-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-submission into .agents/skills/sosp-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-submission --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-submission .cursor/skills/sosp-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-submission into .cursor/skills/sosp-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sosp-submission --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-submission .gemini/skills/sosp-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-submission into .gemini/skills/sosp-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/sosp-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-submission into .github/skills/sosp-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-submission", 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-submission -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-submission --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-submission .opencode/skills/sosp-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SOSP-Skills/skills/sosp-submission into .opencode/skills/sosp-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sosp-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 683 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references…
- Works in 6 steps: Freeze the evaluation and rebuild all… → Compile in the official format and… → Register the abstract with the final… → …
- Auditing a SOSP submission for HotCRP readiness
- SKILL.md covers Two deadlines, one hard gate, Page and format compliance, Anonymization the SOSP way and Conflict declaration is audited, plus 3 more sections
- Calls pdftotext
What it does
Sosp Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references excluded, the 7x9-inch two-column format, double-blind rules with paper-ID substitution, conflict declaration under PC-chair audit, and desk-reject triage.
Its SKILL.md is about 1.4k 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
- Auditing a SOSP submission for HotCRP readiness
- Covering the abstract-registration and full-paper deadlines
- The 12-page technical-content limit with references excluded
- The 7x9-inch two-column format
Example prompts
- “/sosp-submission”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Freeze the evaluation and rebuild all figures from logged data with one command.
- Compile in the official format and resolve overflow by cutting prose, not leading.
- Register the abstract with the final author list and a conflict list you can defend.
- Run the leak sweep above on the paper and the supplementary document.
- Replace the author block with the assigned paper ID; verify page one.
- Upload to HotCRP early; re-download the PDF from HotCRP and check it renders
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 Submission loads about 1.4k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 683 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). 683 words, ~1,427 tokens.
Download SKILL.mdSave it as
.claude/skills/sosp-submission/SKILL.md (or your agent's skills folder).- name
- sosp-submission
- description
- Use when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references excluded, the 7x9-inch two-column format, double-blind rules with paper-ID substitution, conflict declaration under PC-chair audit, and desk-reject triage.
SOSP Submission
Run this audit before anything is uploaded to the SOSP HotCRP instance. Every number
below is a 2026-cycle anchor verified on 2026-07-08 against the official CFP and author
guidelines at sigops.org/s/conferences/sosp/2026/ and the sosp26.hotcrp.com
deadlines page. SOSP re-issues these rules each year; treat the current cycle's pages
as controlling and this file as the map of what to check.
Two deadlines, one hard gate
SOSP registers abstracts ahead of papers, and the registration is a real gate, not a courtesy: the paper ID assigned at registration replaces the author names on page one of the anonymized PDF, and conflict screening starts from the registered author list.
| Gate (2026 anchors) | Date | What must be final |
|---|---|---|
| Abstract registration | March 27, 2026 | Title, abstract, complete author list, topics, conflicts |
| Full paper upload | April 2, 2026, 7:59:59 AM EDT | Anonymized PDF, optional supplementary document |
| Notification | July 3, 2026 | — |
| Camera-ready | August 28, 2026 | Shepherd-approved final PDF |
The six-day window between the two gates is for polishing, not for writing. A paper that does not build cleanly in the official format a week before registration is already late.
Page and format compliance
- At most 12 pages of technical content — all text, figures, and tables count. Bibliographic references are not included in the limit, so never compress the bibliography to save space; compress prose instead.
- 10-point font on 12-point leading, US letter, everything inside a 178 x 229 mm (7 x 9 in) block, two columns separated by 8 mm. Reviewers at this venue have seen every margin trick; a format violation reads as an integrity problem, not a typo.
- Supplementary material goes in a separate document and may cover only items that are not critical to evaluating the paper (formal proofs, extra analyses, methodological detail). If a claim's evidence lives only in the supplement, the claim is unsupported for review purposes — move it into the 12 pages.
Anonymization the SOSP way
SOSP asks for a good-faith anonymization effort, judged pragmatically:
- Page one carries the registered paper ID where the author block would sit.
- No author names, affiliations, acknowledgments, or grant numbers anywhere, including in the supplement and PDF metadata.
- Self-references in third person; do not cite an identifying technical report as "our earlier version."
- De-identify giveaway context: a deployment description that only one company could have written should be generalized ("a large content provider") without falsifying the evidence.
# Leak sweep over the built PDF and the LaTeX tree before upload
pdfinfo main.pdf | grep -iE '^(author|creator|producer)'
pdftotext main.pdf - | grep -inE 'acknowledg|grant no|@[a-z]+\.(edu|com)|github\.com/' | head
grep -rn --include='*.tex' -iE '\\author|university|laboratory|institute' . | grep -v paperidShow full SKILL.md (289 more words)Show less
Conflict declaration is audited
Unlike venues where conflict lists are taken on trust, SOSP's PC chairs review the declared conflicts, may add missing ones, and may remove declared conflicts that have no basis — naming a PC member as a conflict to dodge a tough reviewer is explicitly called out as improper. Papers conflicted with both PC chairs are routed to a designated conflict chair. Practical consequences:
- Build the conflict list from real categories (co-authors, advisors, same institution, recent collaboration), and be able to justify every entry if asked.
- An undeclared genuine conflict discovered late can poison an otherwise-positive review discussion; over-declaration can be reversed by the chairs and damages trust.
Desk-reject triage
| Finding | Outcome | Can it be fixed after the deadline? |
|---|---|---|
| More than 12 pages of technical content | Rejected without review | No |
| Font, block, or column-geometry tampering | Rejected without review | No |
| Author names or affiliation leak in PDF or supplement | Rejected or chair-flagged | No |
| Missing abstract registration | Paper cannot be submitted | No |
| Unjustified conflict entries | Removed by chairs; credibility cost | Chairs act unilaterally |
| Core evidence only in the supplement | Survives triage, dies in review | Only before the deadline |
Final-ten-days sequence
- Freeze the evaluation and rebuild all figures from logged data with one command.
- Compile in the official format and resolve overflow by cutting prose, not leading.
- Register the abstract with the final author list and a conflict list you can defend.
- Run the leak sweep above on the paper and the supplementary document.
- Replace the author block with the assigned paper ID; verify page one.
- Upload to HotCRP early; re-download the PDF from HotCRP and check it renders page-complete — the submission of record is what HotCRP holds, not your local file.
Output format
[SOSP readiness] Ready / Needs fixes / Not ready
[Gate status] abstract registered? / paper uploaded? / hours to deadline
[Format audit] pages of technical content / geometry / references handling
[Anonymity audit] pass / leaks found: <where>
[Conflict list] defensible? <yes/no + weakest entry>
[Fix order] <ordered actions before upload>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sosp Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Iso27001 Audit Prepalirezarezvani/claude-skills | 28k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| OmniRoute Audit and Policy CLIdiegosouzapw/OmniRoute | 75k | — | ~733 | Automated safety check: Pass | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT |
Similar skills
Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
Qms Audit Expert
davila7/claude-code-templates
Senior QMS Audit Expert for internal and external quality management system auditing.
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 Submission
What does Sosp Submission do?
A skill your agent uses when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references…. Sosp Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a SOSP submission for HotCRP readiness, covering the abstract-registration and full-paper deadlines, the 12-page technical-content limit with references excluded, the 7x9-inch two-column format, double-blind rules with paper-ID substitution, conflict declaration under PC-chair audit, and desk-reject triage.
When should I use Sosp Submission?
Sosp Submission fits situations like: auditing a SOSP submission for HotCRP readiness; covering the abstract-registration and full-paper deadlines; the 12-page technical-content limit with references excluded; the 7x9-inch two-column format.
How do I install Sosp Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-submission -a claude-code`. Or copy the skill folder (SOSP-Skills/skills/sosp-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sosp-submission in your project. Claude Code loads it when a task matches its description.
How do I install Sosp Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-submission -a codex`. Or copy the skill folder (SOSP-Skills/skills/sosp-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sosp-submission in your project. Codex loads it when a task matches its description.
Can I use Sosp Submission 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-submission -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-submission, .gemini/skills/sosp-submission, .github/skills/sosp-submission and .opencode/skills/sosp-submission in your project.
What does Sosp Submission need to run?
Going by SKILL.md and its folder, Sosp Submission needs the command-line tools its instructions call (pdftotext).
Does Sosp Submission 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 Submission 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 Submission use?
Sosp Submission 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 Submission use?
About 1.4k tokens (SKILL.md is roughly 5.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 Sosp Submission?
Skills that share tags, products or a category with Sosp Submission: Iso27001 Audit Prep (alirezarezvani/claude-skills, 28k stars), Production Audit (affaan-m/ECC, 277k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars) and OmniRoute Audit and Policy CLI (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sosp Submission?
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.