isca-supplementary
Use when deciding what accompanies an ISCA submission beyond the 11 reviewed pages — what must live inside the page budget because reviewers see nothing else, how to use fully anonymized artifact links under the double-blind rules, staging material for the revision window, and planning post-acceptance release.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-supplementary --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 Supplementary Strategy ISCA's verified 2026 format was spare: a printable PDF of at most 11 pages of text plus unlimited references, uploaded to HotCRP. The public guidelines described no separate supplementary-file channel and no appendix regime — the only sanctioned overflow surface they mention is a **fully anonymized artifact link** inside the paper. Strategy at this venue is therefore not "what goes in the supplement" but **"what earns a place in the only document reviewers are given"** — and what waits, staged, for the revision window and the camera-ready. ## Triage: the four destinations for every piece of material | Material | Destination | Why | |---|---|---| | Anything a claim depends on (mechanism detail, methodology, headline evidence, overheads) | The 11 pages | Reviewers judge the submission PDF; content elsewhere is invisible at decision time | | Full config dumps, per-workload result tables, extra sweeps | Anonymized artifact repo, referenced once | Available to the curious without spending pages; not assumed read | | Experiments anticipating likely objections | Staged, unpublished — ready for the rebuttal/revision window | The 2026 process let authors add ev
- Triage: the four destinations for every piece of material
- What the anonymized link may carry — and what it may not
- Fitting evidence into 11 pages without hiding it
- The staging shelf: supplementary material in time, not space
- After acceptance: the release ladder
- Failure modes specific to this venue's spareness
- Quick triage output
Identity scrub of the anonymous artifact mirror before submission git -C mirror log --format='%an %ae' | sort -u # commit identities grep -rniE 'university|institute|\.edu|corp|@[a-z-]+\.(com|org)' \ mirror/ --include='*.md' --include='*.txt' | head grep -rn '/home/\|/Users/\|hostname\|slurm' mirror/ | head zip -r artifact-mirror.zip mirror/ -x '*.git*' # if a file drop is used
What does the isca-supplementary skill do?
Use when deciding what accompanies an ISCA submission beyond the 11 reviewed pages — what must live inside the page budget because reviewers see nothing else, how to use fully anonymized artifact links under the double-blind rules, staging material for the revision window, and planning post-acceptance release.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-supplementary --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.