FOCS Skills

A 12-skill depth pack for FOCS submissions: foundations-venue fit, the April HotCRP deadline, the ten-page attention window, full-version submissions, double-blind hygiene, proof checkability, computer-assisted steps, the no-rebuttal review arc, IEEE proceedings camera-ready, and the arXiv/ECCC public record. Grounded in the official FOCS 2026 CFP, IEEE TCMF pages, and award records checked on 202

by @brycewang-stanford 11 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/focs-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 11 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-focs-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 11
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Focs Submission · brycewang-stanford
Use when running the final pre-upload audit of a FOCS (IEEE Symposium on Foundations of Computer Science) submission — the April HotCRP deadline clock, the abstract-references-plus-ten-pages attention rule, the 11-point single-column format floor, PDF security restrictions, double-blind checks, and SIGACT publication-policy compliance.

1k repo stars
▌
Focs Experiments · brycewang-stanford
Use when deciding whether and how computation appears in a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue that accepts on theorems with no evaluation section expected — covering machine-verified case analyses, computer-discovered constructions, and honest illustrative plots.

1k repo stars
▌
Focs Camera Ready · brycewang-stanford
Use when converting a FOCS (IEEE Symposium on Foundations of Computer Science) acceptance into its deliverables — the IEEE proceedings version with copyright and de-anonymization steps, the public arXiv/ECCC full version the CFP expects, the New York talk, and award-eligibility hygiene.

1k repo stars
▌
Focs Related Work · brycewang-stanford
Use when building the related-work and citation apparatus of a FOCS (IEEE Symposium on Foundations of Computer Science) paper — tracing result lineages across the FOCS/STOC record, citing arXiv/ECCC full versions with version pins, handling concurrent preprints, and keeping self-citation double-blind-safe.

1k repo stars
▌
Focs Supplementary · brycewang-stanford
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.

1k repo stars
▌
Focs Writing Style · brycewang-stanford
Use when drafting or revising a FOCS (IEEE Symposium on Foundations of Computer Science) paper — making the first ten pages carry the whole case to a broad theory committee, pairing informal and formal theorem statements, keeping single-column 11-point prose readable, and writing double-blind-safe self-references.

1k repo stars
▌
Focs Review Process · brycewang-stanford
Use when reasoning about how a FOCS (IEEE Symposium on Foundations of Computer Science) submission is evaluated — the TCMF-sponsored program committee, subreferee delegation, double-blind norms the venue adopted years before STOC, the summer decision arc, and what each outcome means for a theory paper.

1k repo stars
▌
Focs Author Response · brycewang-stanford
Use when managing author-side communication around a FOCS (IEEE Symposium on Foundations of Computer Science) submission, where no rebuttal round exists — discharging objections inside the paper before submission, handling rare chair-mediated queries, and converting a rejection into a disciplined autumn resubmission.

1k repo stars
▌
Focs Reproducibility · brycewang-stanford
Use when hardening a FOCS (IEEE Symposium on Foundations of Computer Science) paper's checkability — the theory analogue of reproducibility — via hypothesis ledgers, single-source theorem statements that cannot drift between submission and arXiv versions, audits of imported theorems, and certificates for machine-checked steps.

1k repo stars
▌
Focs Topic Selection · brycewang-stanford
Use when deciding whether a theoretical-computer-science result belongs at FOCS (IEEE Symposium on Foundations of Computer Science) — testing foundations-level significance, weighing the April deadline against sibling theory venues like STOC, SODA, CCC, ITCS, or CRYPTO, and applying the CFP's broaden-the-reach clause.

1k repo stars
▌
Focs Artifact Evaluation · brycewang-stanford
Use when planning the durable evidence objects around a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue with no artifact track where the public arXiv/ECCC full version is the artifact of record, plus proof certificates, checker code, and the IEEE Xplore version's supporting role.

1k repo stars