webconf-supplementary
Use when deciding what belongs in the Web Conference (WWW) appendix versus the 8 main pages versus an external artifact, under the single-PDF 12-page ceiling where references and appendix share the tail, reviewers need not read past page 8, and no separate supplementary upload exists in the research tracks.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-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.
# Web Conference Supplementary Material The Web Conference's 2026 research tracks had **no separate supplementary upload**. Everything travels in one PDF: 8 pages of main paper, then references, then an optional appendix, capped at 12 pages total. That design creates a zero-sum tail — every reference line competes with appendix space — and a hard rhetorical rule: reviewers are told they need not read past page 8, so the appendix can *support* belief but never *create* it. ## The three-container model | Container | Budget | Reviewer contract | Right contents | |---|---|---|---| | Main paper | 8 pages | Read and judged | Claims, method, headline evidence, limitations | | PDF tail | 12 − 8 − |refs| pages | Optional reading | Proofs, pseudo-code, protocol, extra tables | | External artifact | unlimited | Reached only via link | Code, data manifests, full logs | The tail is the scarcest resource most teams misbudget. A survey-flavored web paper with 90 references can eat 2.5+ pages, leaving under 1.5 pages of appendix; a theory-flavored one with 35 references gets nearly 4. Count your tail *before* promising appendix sections to co-authors. ## What earns tail space (and what does not) E
- The three-container model
- What earns tail space (and what does not)
- Compression order when the PDF is over 12
- Anonymized linking pattern
- Worked budget: one paper, two viable splits
- Cross-track variation
- Pre-flight audit
- Output format
What does the webconf-supplementary skill do?
Use when deciding what belongs in the Web Conference (WWW) appendix versus the 8 main pages versus an external artifact, under the single-PDF 12-page ceiling where references and appendix share the tail, reviewers need not read past page 8, and no separate supplementary upload exists in the research tracks.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill webconf-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.