New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Stoc Related Work

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint…

MITAuto-check passedResearch & Science

Install Stoc Related Work

skills CLI
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-related-work -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install brycewang-stanford/Awesome-Journal-Skills stoc-related-work --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/STOC-Skills/skills/stoc-related-work .claude/skills/stoc-related-work && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stoc-related-work
GitHub stars
1.2k
Token cost
~1.6k tokens
SKILL.md length
767 words
Files
1
Skills in repo
2,387
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint…

  • Works in 5 steps: Search arXiv (cs.DS, cs.CC, and your… → Check the most recent STOC/FOCS/SODA… → Walk the dblp pages of the five authors… → …
  • Positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages
  • SKILL.md covers The lanes a STOC reviewer checks, Version-aware citation, a…, Concurrent and independent work and Double-blind self-positioning, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Stoc Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint version pairs correctly, handling concurrent arXiv and ECCC work, and keeping self-citation double-blind-safe.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Academic paper search, Literature review and Positioning and messaging. It works with arXiv. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.

When your agent uses it

  • Positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages
  • Citing conference/journal/preprint version pairs correctly
  • Handling concurrent arXiv and ECCC work
  • Keeping self-citation double-blind-safe

Example prompts

  • “/stoc-related-work”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Search arXiv (cs.DS, cs.CC, and your problem's other categories) and
  2. Check the most recent STOC/FOCS/SODA accepted-paper lists — results
  3. Walk the dblp pages of the five authors most active on the problem; new
  4. For each hit, classify: prior (delta must be recomputed), concurrent
  5. Re-run the same sweep before camera-ready; the February-to-March window

What it can do on your machine

Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bibtex).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stoc Related Work loads about 1.6k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 767 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 767 words, ~1,638 tokens.

Download SKILL.mdSave it as .claude/skills/stoc-related-work/SKILL.md (or your agent's skills folder).
name
stoc-related-work
description
Use when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint version pairs correctly, handling concurrent arXiv and ECCC work, and keeping self-citation double-blind-safe.

Theory positioning is quantitative: reviewers expect the paper to place its bounds in an explicit lineage ("[A] gave $O(n^2)$; [B] improved to $O(n \log n)$ under assumption X; we remove X and reach $O(n)$"), and they check the lineage against their own memory of it. Errors here — a missed improvement, a misquoted exponent, a result attributed to the journal version's year instead of the conference announcement — are among the fastest credibility losses available at this venue.

The lanes a STOC reviewer checks

LaneWhat must be coveredTypical miss
The direct lineageEvery prior bound on your exact problem, with its modelQuoting the weakest prior bound to inflate the delta
The barrier literatureKnown obstructions your result confronts (relativization, natural proofs, hardness reductions, integrality gaps)Claiming a breakthrough while silent on why the barrier does not apply
Neighboring modelsThe same question in weaker/stronger models (randomized vs. deterministic, static vs. dynamic, classical vs. quantum)"First" claims that are only first in one cell of the model grid
Technique ancestryWhere your machinery comes from, even from other subfieldsReviewers who invented the machinery are plausibly your reviewers
Concurrent workRecent arXiv/ECCC preprints on the problemThe subreviewer knows about last month's preprint; your draft predates it

Version-aware citation, a theory-specific craft

Most important theory results exist as a conference extended abstract, a later journal version, and a preprint — and they can differ mathematically (bounds improve; bugs get fixed in the journal version). House rules:

  • Cite the version whose statement you actually use. If you invoke the strengthened journal bound, cite the journal paper, possibly alongside the conference announcement.
  • Date claims by first announcement (conference or preprint), attribute proofs by where the complete proof appears.
  • Keep both versions in the entry when the community habitually does:
bibtex
@inproceedings{ST01-smoothed,
  author    = {Spielman, Daniel A. and Teng, Shang-Hua},
  title     = {Smoothed Analysis of Algorithms: Why the Simplex Algorithm
               Usually Takes Polynomial Time},
  booktitle = {Proc. 33rd ACM Symposium on Theory of Computing (STOC)},
  pages     = {296--305},
  year      = {2001},
  note      = {Journal version: J. ACM 51(3), 2004}
}
  • dblp is the community's canonical metadata source; export entries from it rather than hand-typing venues, and prefer its conference/journal splitting over publisher aggregator records.

Concurrent and independent work

The arXiv/ECCC-first culture means collisions are visible within days, not years. Norms as practiced:

  • A concurrent preprint (posted around your submission, obtained independently) gets a clearly flagged paragraph — "Independently and concurrently, [Z] obtained..." — with an honest comparison of strength, generality, and technique. Committees routinely accept both papers when the note is fair.
  • A prior preprint you missed is not concurrent work; the delta must be recomputed against it, sometimes fatally. Run a fresh arXiv/ECCC sweep the week before the deadline, and again before camera-ready.
  • If a collision surfaces mid-review, current practice varies on whether and how to notify the chair; check the cycle's instructions (待核实) rather than improvising contact with the PC.
Show full SKILL.md (328 more words)Show less

Double-blind self-positioning

STOC 2026 was double-blind (checked 2026-07-08). Your prior work is often the nearest related work, so:

  • Cite yourself in third person, with no ownership markers ("building on the framework of [7]" — not "our framework [7]").
  • Do not cite an unpublished manuscript of yours that only the authors could possess; if the submission genuinely depends on it, it must be publicly posted (anonymity-compatibly) or its content inlined.
  • Acknowledgement-style thanks to collaborators on adjacent work wait for camera-ready.

Building the comparison honestly

  • State comparisons in the prior work's own parameterization before yours; translating everything into the units most flattering to your bound is spotted immediately by the lane-one reviewer.
  • When your result is incomparable to a prior one (better dependence on $n$, worse on $\varepsilon$), say "incomparable" and give the crossover point — that sentence pre-empts the review question (stoc-author-response's objection ledger).
  • A small comparison table in the introduction (result, model, bound, source) is house-standard for crowded problems and often becomes the most-read object in the paper.

The deadline-week sweep, as a procedure

  1. Search arXiv (cs.DS, cs.CC, and your problem's other categories) and ECCC for the problem's standard names and their variants; theory titles are conventional enough that keyword search works.
  2. Check the most recent STOC/FOCS/SODA accepted-paper lists — results announced there may not have preprints yet.
  3. Walk the dblp pages of the five authors most active on the problem; new preprints appear there within days.
  4. For each hit, classify: prior (delta must be recomputed), concurrent (comparison paragraph), or unrelated-despite-title (note why, for your own future reference).
  5. Re-run the same sweep before camera-ready; the February-to-March window regularly produces new lineage entries that the full version should cite.

Cycle-volatility warnings

  • Anonymity rules for citing your own preprints follow the live CFP's double-blind wording (待核实 per cycle; the policy is new at STOC and may be refined).
  • Deadline-week literature sweeps must include ECCC and the current FOCS/SODA accepted-paper lists, which shift the frontier between CFPs.

Output format

text
[Lineage table] complete / gaps: <missing bounds or models>
[Barrier account] addressed / silent <- fix before review
[Version hygiene] statements matched to cited versions? dblp-verified?
[Concurrency] <preprints found in final sweep; comparison note drafted?>
[Self-citation] double-blind-safe / leaks: <list>

© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in STOC-Skills/skills/stoc-related-work of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Stoc Related Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stoc Related Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stoc Related Work this skillbrycewang-stanford/Awesome-Journal-Skills1.2k—~1.6kAutomated safety check: PassMIT
Literature Reviewneflibata-feng/MyArxiv-Agent12620 repos~5.9kAutomated safety check: NotesMIT
Systematic Literature Review Builderbytedance/deer-flow84k2 repos~4.3kAutomated safety check: PassMIT
Paper Research on arXivXiaomiMiMo/MiMo-Code14k—~1.5kAutomated safety check: PassMIT
Literature Review AgentAr9av/PaperOrchestra6791 repos~5.2kAutomated safety check: PassCustom licence
Arxiv MCP Serverblazickjp/arxiv-mcp-server3.2k—~353Automated safety check: PassApache-2.0

Similar skills

  • Literature Review

    neflibata-feng/MyArxiv-Agent

    Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).

    126 GitHub starsUsed in 20 repos~5.9k tokens
    Research & ScienceAuto-check: notes

  • Systematic Literature Review Builder

    bytedance/deer-flow

    Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.

    84k GitHub starsUsed in 2 repos~4.3k tokens
    Research & ScienceAuto-check passed

  • Paper Research on arXiv

    XiaomiMiMo/MiMo-Code

    Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.

    14k GitHub stars~1.5k tokensUpdated 2 days ago
    Research & ScienceAuto-check passed

  • Literature Review Agent

    Ar9av/PaperOrchestra

    Step 3 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from Ar9av/PaperOrchestra.

    679 GitHub starsUsed in 1 repo~5.2k tokens
    Research & ScienceAuto-check passed

  • Arxiv MCP Server

    blazickjp/arxiv-mcp-server

    A skill your agent uses when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or…

    3.2k GitHub stars~353 tokensUpdated 2 days ago
    Research & ScienceAuto-check passed

  • Arxiv Paper Writer

    appautomaton/latex-arxiv-SKILL

    Write LaTeX ML/AI review articles for arXiv using the IEEEtran template and verified BibTeX citations.

    458 GitHub stars~2.3k tokensUpdated 27 days ago
    Research & ScienceAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

  • Aaag Data Analysis

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Literature Positioning

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Rebuttal

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Research Design

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…

    1.2k GitHub stars~1.4k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Review Process

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…

    1.2k GitHub stars~1.3k tokensUpdated 14 days ago
    Auto-check passed

  • Aaag Submission

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…

    1.2k GitHub stars~1.6k tokensUpdated 14 days ago
    Auto-check passed

Works with

Categories

Questions about Stoc Related Work

What does Stoc Related Work do?

A skill your agent uses when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint…. Stoc Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages, citing conference/journal/preprint version pairs correctly, handling concurrent arXiv and ECCC work, and keeping self-citation double-blind-safe.

When should I use Stoc Related Work?

Stoc Related Work fits situations like: positioning a STOC (ACM Symposium on Theory of Computing) paper against the theory literature — tracing bound-improvement lineages; citing conference/journal/preprint version pairs correctly; handling concurrent arXiv and ECCC work; keeping self-citation double-blind-safe.

How do I install Stoc Related Work in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-related-work -a claude-code`. Or copy the skill folder (STOC-Skills/skills/stoc-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/stoc-related-work in your project. Claude Code loads it when a task matches its description.

How do I install Stoc Related Work in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-related-work -a codex`. Or copy the skill folder (STOC-Skills/skills/stoc-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/stoc-related-work in your project. Codex loads it when a task matches its description.

Can I use Stoc Related Work in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill stoc-related-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stoc-related-work, .gemini/skills/stoc-related-work, .github/skills/stoc-related-work and .opencode/skills/stoc-related-work in your project.

What does Stoc Related Work need to run?

SKILL.md names no scripts, command-line tools or credentials: Stoc Related Work is instructions for the agent only.

Does Stoc Related Work access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stoc Related Work safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stoc Related Work use?

Stoc Related Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stoc Related Work use?

About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stoc Related Work?

Skills that share tags, products or a category with Stoc Related Work: Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars), Systematic Literature Review Builder (bytedance/deer-flow, 84k stars), Paper Research on arXiv (XiaomiMiMo/MiMo-Code, 14k stars) and Literature Review Agent (Ar9av/PaperOrchestra, 679 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stoc Related Work?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.

Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.