Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the…
Install Itcs Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-workflow .claude/skills/itcs-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 "itcs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-workflow into .claude/skills/itcs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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/ITCS-Skills/skills/itcs-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 itcs-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-workflow .agents/skills/itcs-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 "itcs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-workflow into .agents/skills/itcs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-workflow .cursor/skills/itcs-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 "itcs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-workflow into .cursor/skills/itcs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 ITCS-Skills/skills/itcs-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 itcs-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-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/ITCS-Skills/skills/itcs-workflow .gemini/skills/itcs-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 "itcs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-workflow into .gemini/skills/itcs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-workflow .github/skills/itcs-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 "itcs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-workflow into .github/skills/itcs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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 itcs-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 itcs-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/ITCS-Skills/skills/itcs-workflow .opencode/skills/itcs-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 "itcs-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-workflow into .opencode/skills/itcs-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-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
itcs-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 566 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the…
- Plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review
- SKILL.md covers The single-cycle calendar…, Working backward from the…, The no-rebuttal consequence,… and After notification, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The November notification
What it does
Itcs Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.
Its SKILL.md is about 1.4k 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
- Plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review
- The November notification
- The LIPIcs camera-ready
- The January conference with its Graduating Bits session
Example prompts
- “/itcs-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
Itcs Workflow loads about 1.4k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 566 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). 566 words, ~1,385 tokens.
Download SKILL.mdSave it as
.claude/skills/itcs-workflow/SKILL.md (or your agent's skills folder).- name
- itcs-workflow
- description
- Use to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.
ITCS Workflow
ITCS runs on one annual cycle with a distinctive rhythm: submit in early September, get a
yes/no in November with no rebuttal in between, and present the following January, with
open-access publication in LIPIcs. There is no second round, no revise-and-resubmit, and no
author-response phase, so the leverage is almost entirely before the deadline. Plan the year
backward from that September date. Every date below is the ITCS 2026 snapshot (Bocconi,
Milan); reopen the current call — see
../../resources/official-source-map.md.
The single-cycle calendar (ITCS 2026 anchor)
| Phase | ITCS 2026 date | What actually happens |
|---|---|---|
| Abstract / registration | 4 Sep 2025 (7:59:59 PM EDT) | Title, abstract, authors, conflicts locked in HotCRP; the abstract drives PC bidding |
| Full-paper submission | 6 Sep 2025 (7:59:59 PM EDT) | Anonymized PDF with complete proofs uploaded |
| Reviewing (no rebuttal) | Sep-Oct 2025 | PC + external reviewers read; no author-response phase |
| Notification | ~10 Nov 2025 | Accept / reject; there is no Major Revision category |
| Camera-ready | Late 2025 (per call) | lipics-v2021 class, de-anonymized, LIPIcs metadata |
| Conference | 27-30 Jan 2026 | Talks, Graduating Bits session, community mixing at Bocconi |
Because there is no rebuttal and no second deadline, treat the September upload as final in a way authors from rebuttal venues underestimate: the paper must answer the reviewer's objections on its own.
Working backward from the deadline
D-day (early Sep) : full paper, complete proofs, anonymized, uploaded and re-downloaded
D-2 days : abstract/registration + conflicts locked (earlier than the paper!)
D-1 to 2 weeks : full version to arXiv/ECCC/ePrint (encouraged; lightweight double-blind)
final proof-completeness pass (no "proof omitted" on a central claim)
D-3 to 4 weeks : freeze the model and definitions; polish the first-10-pages merits window
D-2 months : decide ITCS vs STOC/FOCS/SODA on the novelty axis (itcs-topic-selection)The two commonest self-inflicted failures: (1) missing the abstract/registration cutoff, which is ~2 days before the paper deadline — no registration, no submission slot; and (2) carrying a rebuttal-venue mindset that leaves objections for "later," when there is no later.
The no-rebuttal consequence, planned for
Since you cannot answer reviewers after they read, you must answer them inside the paper:
- Anticipate the "is this model empty/trivial?" question with an anchoring result up front.
- Anticipate the "is this actually new?" question with an honest related-work delta.
- Anticipate the "why should I care?" question with a first-page conceptual payoff.
- State scope and limitations yourself, so a reviewer does not raise them as your blind spot.
See itcs-author-response for how the absence of a rebuttal
reshapes strategy, and itcs-writing-style for pre-empting
objections in the prose.
Show full SKILL.md (224 more words)Show less
After notification
- Accept: move to
itcs-camera-ready— switch tolipics-v2021, de-anonymize, complete ACM CCS / keywords / funding, and hit the LIPIcs production deadline. Register at least one author to present. Consider submitting a Graduating Bits talk if a coauthor is near graduation. - Reject: there is no resubmission to a later ITCS round this year (single cycle). Route the
paper — often to STOC/FOCS/SODA on depth, or to a journal — via the table in
itcs-topic-selection. The reviews, though not rebuttable, are usually substantive; use them to sharpen the next submission.
The Graduating Bits and community layer
ITCS is a smaller-community venue with a strong direction-setting culture. The Graduating Bits session — short talks by researchers near graduation (on either side) presenting results, plans, and themselves — is a fixture worth planning for if you or a coauthor is on the market. The conference is as much about seeding directions as reporting finished work, which is why bold, early ideas fare well here; budget time for the hallway and session conversations, not just the talk.
Reverify each cycle
- The exact abstract and paper deadlines, and the AoE/EDT timezone of the cutoff.
- Whether the current call still runs no rebuttal (the theory-venue norm, but confirm).
- The camera-ready deadline and the current LIPIcs class/version.
- The host, city, and dates — ITCS 2027 is 待核实 as of 2026-07-09; do not carry Bocconi forward.
Output format
[ITCS cycle status] on track / at risk
[Registration] title/abstract/authors/conflicts locked by the earlier cutoff? yes/no
[Paper] complete proofs present? anonymized? first-10-pages merits window done?
[Preprint] full version posted (arXiv/ECCC/ePrint)? yes/no
[Post-notification] accept -> camera-ready owner+date ; reject -> reroute target
[Calendar risks] <ordered, with dates before the early-September cutoff>© 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 ITCS-Skills/skills/itcs-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Itcs 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 |
|---|---|---|---|---|---|---|
| Itcs Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | 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 Itcs Workflow
What does Itcs Workflow do?
A skill your agent uses to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the…. Itcs Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.
When should I use Itcs Workflow?
Itcs Workflow fits situations like: plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review; the November notification; the LIPIcs camera-ready; the January conference with its Graduating Bits session.
How do I install Itcs Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-workflow -a claude-code`. Or copy the skill folder (ITCS-Skills/skills/itcs-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/itcs-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Itcs Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-workflow -a codex`. Or copy the skill folder (ITCS-Skills/skills/itcs-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/itcs-workflow in your project. Codex loads it when a task matches its description.
Can I use Itcs 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 itcs-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/itcs-workflow, .gemini/skills/itcs-workflow, .github/skills/itcs-workflow and .opencode/skills/itcs-workflow in your project.
What does Itcs Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Itcs Workflow is instructions for the agent only.
Does Itcs 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 Itcs 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 Itcs Workflow use?
Itcs 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 Itcs Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.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 Itcs Workflow?
Skills that share tags, products or a category with Itcs 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 Itcs 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.