conext-submission
Use when auditing an ACM CoNEXT submission for HotCRP readiness, covering the choice between the December and June cycles, the mandatory paper-registration step, the ACM acmart page budget (long ≤16 + ≤4 appendix; short ≤10 + ≤2 appendix), double-anonymous review, the reproducibility badge opt-in due at submission, PACMNET publication, and desk-reject triage before the cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-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.
# CoNEXT Submission Run this audit before uploading to the CoNEXT HotCRP site. CoNEXT research papers are published as **journal articles in PACMNET** (Proceedings of the ACM on Networking), so the submission is judged like a journal manuscript that also earns a conference slot. Every number below was read from the CoNEXT 2026 call and the CoNEXT 2025 CFP on 2026-07-09 via search renderings (see [`../../resources/official-source-map.md`](../../resources/official-source-map.md)); treat them as a one-cycle snapshot and reopen the live call first. ## Pick the cycle first CoNEXT runs **two submission cycles a year**, and choosing the wrong one costs months: - The **December cycle** (for CoNEXT 2026: registration 5 Dec 2025, submission 12 Dec 2025) gives an earlier notification (31 Mar 2026) and, if you earn a major revision, a spring resubmission path. - The **June cycle** (submission 5 Jun 2026) is the later entry point into the *same* annual program and the same rolling PACMNET volume. Both feed one conference and one journal volume, so the decision is about *readiness and calendar*, not prestige — submit to the nearer honest deadline your evidence is actually ready for. See [`conext
- Pick the cycle first
- The two-step deadline within a cycle
- Format and page budget
- Double-anonymous sweep
- Reproducibility opt-in at submission time
- 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-]+|gitlab|zenodo\.org/record|acknowledg|grant|our (testbed|deployment|university)' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head grep -rniE 'university|@[a-z0-9.]+\.edu|internal hostname|AS[0-9]+ .*our' artifact/ --include='*.md' | head
What does the conext-submission skill do?
Use when auditing an ACM CoNEXT submission for HotCRP readiness, covering the choice between the December and June cycles, the mandatory paper-registration step, the ACM acmart page budget (long ≤16 + ≤4 appendix; short ≤10 + ≤2 appendix), double-anonymous review, the reproducibility badge opt-in due at submission, PACMNET publication, and desk-reject triage before the cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-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.