infocom-submission
Use when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the five-papers-per-author cap, and desk-reject triage before the AoE cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.
# INFOCOM Submission Run this audit before the EDAS deadline. INFOCOM is a **large IEEE ComSoc flagship** — on the order of ~1,400-1,500 submissions per year — so mechanical non-compliance is caught at scale and papers over the length limit are simply **not reviewed**. Every number below was read from the INFOCOM 2026/2027 Call for Papers and Submission Guidelines on 2026-07-09 via search renderings of the `ieee-infocom.org` URLs (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## The two-step deadline (abstract, then paper) INFOCOM separates the **abstract/metadata registration** from the **full-paper upload**, both on EDAS and both AoE: - **Abstract/metadata** (INFOCOM 2026: 24 July 2025) locks title, all co-authors, and a **≤200-word abstract** into EDAS. This metadata drives the automated review assignment, so it must reflect the real paper. - **Full paper** (INFOCOM 2026: 31 July 2025; INFOCOM 2027: 31 July 2026) uploads the anonymized PDF. Miss the abstract step and EDAS will not accept the PDF later. Register with the *real* title and abstract, not a placeholder — the assignment system matches your manuscript and ab
- The two-step deadline (abstract, then paper)
- Format and page budget (hard)
- Double-blind sweep
- The five-paper cap
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF before EDAS upload
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # scrub metadata identity
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|our (prior|previous) (work|system)|acknowledg|this work was supported' | head
grep -nEi '\\thanks|\\author\{[^}]*[A-Za-z]' paper.tex | head # stray author/thanks blocksWhat does the infocom-submission skill do?
Use when auditing an IEEE INFOCOM main-conference submission for EDAS readiness, covering the two-step abstract-then-paper registration, the IEEEtran two-column 10-page/9-page-of-text budget, double-blind anonymization of the PDF and metadata, the five-papers-per-author cap, and desk-reject triage before the AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.