isca-submission
Use when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the template check, the double-blind sweep including PDF metadata and anonymized artifact links, and HotCRP form completion before AoE.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.
# ISCA Submission This audit assumes the deadline is days away and the PDF nearly final. Every hard rule cited below is the verified ISCA 2026 record (checked 2026-07-08); the 2027 guidelines were not yet posted at check time, so confirm each line against the live `iscaconf.org` pages before trusting it (待核实). ## The two-step gate ISCA 2026 collected **abstracts November 10** and **full papers November 17, 2025** — a seven-day gap with different stakes at each step: - The abstract step registers title, abstract text, authors, topics, and conflicts in HotCRP. It is what reviewer assignment works from. Submitting a throwaway abstract and rewriting it at the paper step defeats its purpose and can misroute the paper to the wrong reviewers. - The paper step uploads the reviewed PDF. New submissions cannot appear at this step — no abstract, no paper. - Industry-track submissions ran on their own later pair (December 5 / December 12, 2025); confirm which track's dates govern you. Treat the abstract deadline as the real deadline for *decisions* (title, claim, topic areas, author list, conflicts) and the paper deadline as the real deadline for *evidence and prose*. ## Hard-format checklist,
- The two-step gate
- Hard-format checklist, 2026 rules
- Double-blind sweep — the three 2026-specific rules
- The HotCRP form is a second document
- Final-72-hours run order
- Common last-week failures, ranked by frequency
- Audit output template
Mechanical anonymity + format pass on the final PDF pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # metadata fields pdftotext paper.pdf - | grep -nEi \ pdftotext -f 1 -l 1 paper.pdf - | head -5 # no names under title pdffonts paper.pdf | awk '$5=="no"' # non-embedded fonts body-page count: note the page where references begin, compare to 11 pdftotext paper.pdf - | grep -n 'REFERENCES\|References' | head -1
What does the isca-submission skill do?
Use when running the final pre-deadline audit of an ISCA submission — the two-step abstract-then-paper gate a week apart, the 11-page text limit with unlimited references, the template check, the double-blind sweep including PDF metadata and anonymized artifact links, and HotCRP form completion before AoE.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.