focs-submission
Use when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the abstract-references-plus-ten-pages attention rule, the 11-point single-column format floor, PDF security restrictions, double-blind checks, and SIGACT publication-policy compliance.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-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.
# FOCS Submission Anchor cycle: FOCS 2026 (67th edition), submissions due Wednesday, April 1, 2026, 5:00 PM EDT — a US-Eastern wall clock equal to 21:00 UTC, not an anywhere-on-earth deadline — via `focs26.hotcrp.com` (CFP checked 2026-07-08; that deadline has passed, so this audit now serves the next cycle: reopen the live CFP before trusting any number here). ## What the 2026 CFP actually required | Requirement | 2026 wording (verify per cycle) | |---|---| | Length | No bound; full version encouraged as the submission | | Attention rule | Abstract + references + first **ten pages** guaranteed; the rest at the committee's discretion | | Typography | 11-point or larger font, single column, single-spaced with ample spacing, ≥1-inch margins, letter-size paper | | File | PDF **without security restrictions on copying or printing** | | Anonymity | Double-blind: no names/affiliations/emails, third-person self-references, acknowledgements omitted | | Publication policy | SIGACT rules: nothing published or scheduled before the conference month elsewhere; no simultaneous proceedings/journal submission | | Exceptions | Prior appearance in a venue with significantly different format/content/
- What the 2026 CFP actually required
- Mechanical pre-flight
- Deadline-week sequence
- HotCRP metadata is part of the submission
- Policy traps specific to this venue
- Readiness verdict
Page geometry and count of the guaranteed window pdfinfo submission.pdf | grep -E 'Pages|Page size' # letter = 612 x 792 pts qpdf --show-encryption submission.pdf # want: "File is not encrypted" Identity leakage in embedded metadata exiftool submission.pdf | grep -iE 'author|creator|company' Self-reference sweep in the source grep -rn --include='*.tex' -iE '\b(we|our) (recent|previous|earlier|prior)\b|acknowledg|thank' .
What does the focs-submission skill do?
Use when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the abstract-references-plus-ten-pages attention rule, the 11-point single-column format floor, PDF security restrictions, double-blind checks, and SIGACT publication-policy compliance.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-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 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.