focs-supplementary
Use when architecting everything after page ten of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — a venue with no separate supplement channel where the paper itself continues past the guaranteed-read window — covering body organization, proof placement, and navigation for the discretionary reader.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-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.
# FOCS Supplementary FOCS has no supplementary-material upload, no appendix size cap, and no separate supplement deadline: the submission is one PDF, the CFP encourages it to be the full version, and everything beyond the abstract, references, and first ten pages is read at the committee's discretion (2026 CFP, checked 2026-07-08). "Supplementary material" at this venue therefore means *the rest of your own paper* — pages eleven onward — and the design question is how to serve two readers at once: the committee member who stops at page ten, and the assigned expert who reads to the end. ## The two-reader contract | Reader | What they read | What pages 11+ must give them | |---|---|---| | Breadth reviewer (any PC member) | Window only | Nothing — the window must be self-sufficient; pages 11+ may not carry any *claim* absent from it | | Depth reviewer / subreferee | Window, then targeted dives | Fast navigation from each windowed statement to its complete proof, with no re-derivation required | | Post-acceptance community | The public full version | The same body, now the record of correctness for a decade | The contract's first clause is the one authors break: introducing a new resul
- The two-reader contract
- Organizing the discretionary body
- Pointer discipline
- The window boundary is a design object
- Length judgment
- Mechanics that keep a long document navigable
- Final check before upload
What does the focs-supplementary skill do?
Use when architecting everything after page ten of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — a venue with no separate supplement channel where the paper itself continues past the guaranteed-read window — covering body organization, proof placement, and navigation for the discretionary reader.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-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.