percom-submission
Use when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget, double-blind anonymization, the open-data / human-subjects plan, IEEE Xplore publication, and desk-reject triage before the AoE cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-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.
# PerCom Submission Run this audit before uploading to the PerCom HotCRP site (`percom2027.hotcrp.com` for the current cycle). PerCom research papers publish in **IEEE Xplore** and are reviewed **double-blind**, so the submission must be both anonymous and complete on its own — the bounded rebuttal cannot add new experiments later. Every number below was read from the PerCom 2027 Call for Papers and Dates pages on 2026-07-09 via search renderings of the `percom.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 PerCom separates **paper registration** from **paper submission**, and both are AoE: - **Registration** locks in title, abstract, authors, and topic areas about a week early (PerCom 2027: **4 September 2026**). Miss it and the system will not accept the PDF later. - **Submission** uploads the anonymized PDF (PerCom 2027: **11 September 2026**, 23:59 AoE). Register with the *real* title and abstract, not a placeholder — the abstract drives TPC bidding, and a registered abstract that diverges from the final paper quietly worsens your reviewer match. ## Format and page budget - **IEEEtr
- The two-step deadline
- Format and page budget
- Double-blind sweep
- Open data and human subjects 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 dataset/artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|ieee-dataport|zenodo\.org/record|acknowledg|IRB|university' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head grep -rni 'our (lab|testbed|deployment)|@[a-z0-9.]*\.edu' artifact/ --include='*.md' | head
What does the percom-submission skill do?
Use when auditing an IEEE PerCom research-track submission for HotCRP readiness, covering the mandatory paper-registration step, the IEEEtran 9+1 two-column page budget, double-blind anonymization, the open-data / human-subjects plan, IEEE Xplore publication, and desk-reject triage before the AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill percom-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.