Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission…
Install Focs Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/FOCS-Skills/skills/focs-workflow .claude/skills/focs-workflow && rm -rf skills-srcUse ~/.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/
Install the "focs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-workflow into .claude/skills/focs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/FOCS-Skills/skills/focs-workflow .agents/skills/focs-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "focs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-workflow into .agents/skills/focs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/FOCS-Skills/skills/focs-workflow .cursor/skills/focs-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "focs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-workflow into .cursor/skills/focs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path FOCS-Skills/skills/focs-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/FOCS-Skills/skills/focs-workflow .gemini/skills/focs-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "focs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-workflow into .gemini/skills/focs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/FOCS-Skills/skills/focs-workflow .github/skills/focs-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "focs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-workflow into .github/skills/focs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills focs-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/FOCS-Skills/skills/focs-workflow .opencode/skills/focs-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "focs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FOCS-Skills/skills/focs-workflow into .opencode/skills/focs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "focs-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
focs-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 775 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission…
- Planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline
- SKILL.md covers The 2026 cycle, seen from…, Backward plan for a FOCS 2027…, Coordinating the two-flagship… and Owner matrix for a…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Managing the live post-submission summer of the 2026 cycle
What it does
Focs Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.
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. 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
- Planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline
- Managing the live post-submission summer of the 2026 cycle
- Coordinating with the STOC beat
- Preparing the November conference
Example prompts
- “/focs-workflow”
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.
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
Focs Workflow loads about 1.6k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 775 words of instructions outside code blocks.
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). 775 words, ~1,615 tokens.
Download SKILL.mdSave it as
.claude/skills/focs-workflow/SKILL.md (or your agent's skills folder).- name
- focs-workflow
- description
- Use when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.
FOCS Workflow
The FOCS year is anchored in spring: the 2026 cycle closed submissions on
Wednesday, April 1, 2026, 5:00 PM EDT (21:00 UTC) on focs26.hotcrp.com, for a
conference in New York on November 8–11, 2026 (67th edition, checked
2026-07-08). As of that check date the cycle is in its post-submission phase:
papers are with the program committee, notification and camera-ready dates were
not yet published (待核实), and the workshop-proposal window is open. This
skill manages both the live phases and the planning of the next attempt.
The 2026 cycle, seen from mid-July
| Phase | Status at 2026-07-08 | Author actions |
|---|---|---|
| Submission (Apr 1, 5 PM EDT) | Closed | None — do not contact reviewers |
| PC evaluation (spring–summer) | In progress | Keep the arXiv/ECCC version stable; log any bug fixes separately |
| Notification | Date 待核实 (historically midsummer) | Pre-draft both outcomes: camera-ready plan and resubmission memo |
| Workshop proposals | Open until July 31, 2026 AoE (to the workshop chairs; decisions August 14) | Consider proposing a Sunday Nov 8 workshop independent of paper outcome |
| Camera-ready | Date 待核实 (acceptance packet controls) | Reserve a two-week block after notification |
| Conference (Nov 8–11, New York) | Fixed | Budget travel early; November NYC hotel prices climb fast |
Two live rules for the waiting months: first, if you discover a genuine error in a submitted proof, the honest channel is a note to the program chair, not a silent arXiv update that de-synchronizes the record; second, do not submit the same result elsewhere — SIGACT's simultaneous-submission policy governs this IEEE venue and stays in force until decisions arrive.
Backward plan for a FOCS 2027 attempt
FOCS 2027 had no published CFP, venue, or deadline at the check date (待核实). The historical rhythm — CFP in late winter, deadline at the start of April, conference in late autumn — is a pattern to plan by, not a fact to rely on. A realistic backward schedule against a presumed early-April deadline:
T-20 weeks (mid-Nov) : freeze the theorem list; run the significance test
(focs-topic-selection); pick FOCS vs. the STOC beat
T-14 weeks (early Jan): complete proofs of all main theorems; begin the
full-version write-up — at FOCS you submit the whole
paper, so writing cannot trail proving
T-8 weeks (early Feb): STOC notifications land around now — merge any
resubmission into this plan within one week
T-5 weeks (late Feb) : draft the first ten pages as a standalone document;
external read by a non-subarea theoretician
T-2 weeks (mid-Mar) : double-blind sweep, format floor check, external-
citation audit (focs-submission, focs-related-work)
T-3 days : upload to HotCRP; verify the PDF has no copy/print
restrictions; re-upload cost is zero before the clockCoordinating the two-flagship year
From the FOCS seat, STOC is the community's other deadline, five months out of phase. Practical coordination rules:
- Maintain one canonical LaTeX source per project with venue-agnostic theorem
statements, so a FOCS rejection can be re-aimed at STOC without statement
drift (see
focs-reproducibility). - Never hold a finished strong result half a year just to hit FOCS; theory
moves by arXiv, and a posted preprint starts collecting concurrent-work
complications immediately (see
focs-related-work). - Track the sibling clocks explicitly: STOC 2026 was due November 4, 2025 and met June 22–26, 2026; a FOCS 2026 rejection therefore has a natural next stop at the following STOC deadline (exact 2027 date 待核实).
Show full SKILL.md (354 more words)Show less
Owner matrix for a multi-author paper
| Deliverable | Single named owner | Deadline discipline |
|---|---|---|
| Proof completeness audit | Most senior theoretician | T-14 weeks |
| First-ten-pages narrative | Lead author | T-5 weeks |
| Anonymity + format sweep | Any co-author not writing prose that week | T-2 weeks |
| HotCRP metadata, conflicts, topics | Corresponding author | T-3 days |
| arXiv/ECCC full version | Lead author | At or shortly after submission |
The most common workflow failure at this venue is not missing the deadline — it is arriving at T-2 weeks with proofs done and the ten-page front unwritten, because the team treated FOCS like a journal where the whole manuscript is read. Guard the T-5-week milestone above all others.
The workshop lane, run in parallel
The FOCS week has a second entrance that authors chronically forget: the Sunday workshop program. For 2026, proposals of two pages for 2.5-hour or 5-hour in-person workshops were due to the workshop chairs (Dakshita Khurana and Sam Hopkins) by July 31, 2026 AoE, with decisions on August 14. A workshop proposal is decided independently of your paper, gives your subarea a stage in New York even if the paper loses, and is one of the few FOCS levers still live during the review wait. If your group has three or more people working the same emerging direction, the proposal costs an afternoon and is usually worth it.
Rhythm failure modes, named
- The April surprise. Teams calibrated to AoE deadlines discover on the day that 5 PM EDT is nine hours earlier than 23:59 AoE. Convert the clock once, in writing, at T-2 weeks.
- The silent summer. No news between April and notification is the system working; interpreting silence as rejection and posting the paper to another proceedings venue violates the simultaneous-submission bar while the paper is still under review.
- The stale preprint. Referees will read your arXiv version. If it is three revisions behind the submission, they will referee the wrong proofs. Synchronize at submission time, then freeze.
- The double booking. The same result groomed for both FOCS and a
specialist deadline "to see which hits" is a policy violation at this
venue, not a strategy — sequence attempts instead (
focs-topic-selectionfor the ordering logic).
© 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 FOCS-Skills/skills/focs-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Focs Workflow 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Focs Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.8k | 15 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 46k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Read arXiv Paperkarpathy/nanochat | 58k | 2 repos | ~494 | Automated safety check: Pass | MIT | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag 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…
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…
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…
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…
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…
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…
Related
Categories
Questions about Focs Workflow
What does Focs Workflow do?
A skill your agent uses when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission…. Focs Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.
When should I use Focs Workflow?
Focs Workflow fits situations like: planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline; managing the live post-submission summer of the 2026 cycle; coordinating with the STOC beat; preparing the November conference.
How do I install Focs Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a claude-code`. Or copy the skill folder (FOCS-Skills/skills/focs-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/focs-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Focs Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill focs-workflow -a codex`. Or copy the skill folder (FOCS-Skills/skills/focs-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/focs-workflow in your project. Codex loads it when a task matches its description.
Can I use Focs Workflow 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 focs-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/focs-workflow, .gemini/skills/focs-workflow, .github/skills/focs-workflow and .opencode/skills/focs-workflow in your project.
What does Focs Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Focs Workflow is instructions for the agent only.
Does Focs Workflow 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 Focs Workflow 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 Focs Workflow use?
Focs Workflow 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 Focs Workflow use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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 Focs Workflow?
Skills that share tags, products or a category with Focs Workflow: Hypothesis Generation (spacering-net/codeg, 3.8k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars), Nature Paper Card (Yuan1z0825/nature-skills, 46k stars) and Read arXiv Paper (karpathy/nanochat, 58k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Focs Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.