itcs-experiments
From the author
Use when deciding what counts as evidence for an ITCS theory claim — proofs as the primary evidence, worked examples and separations that make a model concrete, and the rare, well-scoped illustrative computation or simulation — and how to keep any computational content checkable and subordinate to the mathematics.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-experiments -a claude-code
Installs to .claude/skills/itcs-experiments/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- icdt-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked examples and counterexamples that establish separations, and, only for papers with an algorithmic contribution, a proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution.Data★ 1.3K
- stoc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when judging whether computation belongs in a STOC (ACM Symposium on Theory of Computing) paper at all — STOC accepts on theorems, with no empirical-evaluation expectation — and when it does, scoping it as certified proof computation, constructive search, or clearly labeled illustration rather than benchmarking.Media★ 1.3K
- focs-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse 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.Media★ 1.3K
- isca-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ISCA paper — pinning simulator fidelity to the claims it must carry, documenting gem5-class configurations and sampling choices, selecting workload suites that represent the claim's domain, tuning baselines in good faith, and separating architectural effect from modeling artifact.Science★ 1.3K
- podc-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when building the evidence for an ACM PODC paper — where "evidence" is a proof, not a benchmark. Covers matching upper and lower bounds, tightness arguments, model and assumption stress-tests, adversary-strength calibration, and the honest, clearly-optional role of any simulation in a distributed-computing-theory paper.Testing★ 1.3K
- colt-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether a COLT (Conference on Learning Theory) paper needs numerical content at all — COLT has no experiments requirement — and, when numerics genuinely help, designing small illustrative simulations that visualize a proved bound, a separation, or a phase transition without diluting the theory.Media★ 1.3K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in