facct-submission
Use when auditing an ACM FAccT submission for OpenReview readiness — the mandatory abstract-registration gate with focus-area selection, the acmart anonymous/review PDF, the 14-page (+1 endmatter) budget, mutual anonymity, the required Generative AI Usage Statement and optional ethics/adverse-impacts statements, archival vs non-archival choice, and desk-reject triage before the deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-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.
# FAccT Submission Run this audit before uploading to the FAccT OpenReview site. FAccT papers are **archival ACM proceedings** in an *interdisciplinary* responsible-AI venue, reviewed **mutually anonymously** by a mixed CS+law+social-science pool. Every number below was read from the FAccT 2026 CFP and Author Guide on 2026-07-09 via search renderings (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## The two-step deadline (abstract gate first) FAccT separates **abstract registration** from **paper submission**, and the gate is hard: - **Abstract registration** locks title, abstract, authors, and **focus areas** roughly a week early (FAccT 2026: **8 January 2026**). Authors who do not register by this date **cannot submit a paper** — the focus areas drive reviewer/AC matching in the mixed pool. - **Paper submission** uploads the anonymized acmart PDF (FAccT 2026: **13 January 2026**). Register with the *real* title, abstract, and honestly chosen focus areas, not placeholders — a mismatch between your registered focus areas and your actual contribution mis-matches you to reviewers from the wrong discipline, the most damagin
- The two-step deadline (abstract gate first)
- Format and page budget
- Mutual-anonymity sweep
- Required and optional endmatter (do not skip)
- Archival vs non-archival
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any anonymized artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|osf\.io|acknowledg|funded|grant|IRB #' | head grep -rniE 'our (lab|group|team|university)|@[a-z0-9.]+\.edu' artifact/ --include='*.md' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head
What does the facct-submission skill do?
Use when auditing an ACM FAccT submission for OpenReview readiness — the mandatory abstract-registration gate with focus-area selection, the acmart anonymous/review PDF, the 14-page (+1 endmatter) budget, mutual anonymity, the required Generative AI Usage Statement and optional ethics/adverse-impacts statements, archival vs non-archival choice, and desk-reject triage before the deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill facct-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.