ieeesp-submission
Use when auditing an IEEE S&P (Oakland) submission for HotCRP readiness, including the registration freeze with ORCID matching, the 13-page/18-page compsoc format, anonymization, the Ethics Considerations field, SoK checkbox, conflict declarations, and the desk-reject triggers specific to S&P cycles.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# IEEE S&P Submission Use this as the final audit before a paper enters an S&P cycle on HotCRP. S&P's desk-reject rules are unusually mechanical — page counts, ORCID matching, and registration completeness are enforced without review — so most preventable losses happen in the upload week, not in review. ## The two-deadline structure An S&P cycle has a **registration deadline** and a **paper deadline** about a week apart, and the registration is binding: title, full abstract, complete author list, ORCIDs, and conflicts are frozen when registration closes (cycle1.sp2027.ieee-security.org/deadlines, checked 2026-07-08). Audit registration as its own deliverable: - Every author has an ORCID whose **email and name match the HotCRP record** — the 2027 CFP desk-rejects papers that violate this. - The abstract entered at registration is the real abstract, not a placeholder; it routes reviewers and cannot be swapped later. - Conflicts are declared per the current CFP's conflict definition; both missing and fabricated conflicts are chair-level problems. - The **Ethics Considerations** field is filled with substance at registration time (see `ieeesp-review-process` for how the REC uses it). -
- The two-deadline structure
- Format gate
- Anonymization with security-paper edges
- Upload-week order of operations
- Desk-reject triage
- Output format
Mechanical pass before upload pdfinfo paper.pdf | grep -iE 'author|creator' # metadata pdftotext paper.pdf - | grep -inE 'our (prior|previous) work|we reported|CVE-20' grep -rniE '(\.edu|\.ac\.|corp)/|/home/[a-z]' figures/ scripts/ || true
What does the ieeesp-submission skill do?
Use when auditing an IEEE S&P (Oakland) submission for HotCRP readiness, including the registration freeze with ORCID matching, the 13-page/18-page compsoc format, anonymization, the Ethics Considerations field, SoK checkbox, conflict declarations, and the desk-reject triggers specific to S&P cycles.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-submission --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 984 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.