Individual skill

focs-experiments

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.

FOCS-Skills/skills/focs-experiments/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,404
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# FOCS Experiments

FOCS solicits research on the theory of computation; nothing in the 2026 CFP
asks for an evaluation, a benchmark, or an artifact (checked 2026-07-08).
Most accepted papers contain no computation at all, and a submission that
*needs* an empirical section to be persuasive is signaling that it belongs at
an algorithms-engineering venue. Yet computation does appear in strong FOCS
papers — inside proofs, behind constructions, and occasionally as a figure.
This skill scopes each mode so it helps rather than hurts.

## Referee questions, by computational mode

The useful frame is not "may I include code?" but "what will a theory referee
ask about this computation?" — because each mode triggers a different
Back to top