Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses to operate under the reality that ITCS has no rebuttal or author-response phase — pre-empting reviewer objections inside the submission, then handling the post-decision…
Install Itcs Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-author-response --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-author-response .claude/skills/itcs-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-author-response into .claude/skills/itcs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-author-response", 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-author-responseType 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-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-author-response --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-author-response .agents/skills/itcs-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-author-response into .agents/skills/itcs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-author-response", 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-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-author-response --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-author-response .cursor/skills/itcs-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-author-response into .cursor/skills/itcs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-author-response", 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-author-response--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-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills itcs-author-response --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-author-response .gemini/skills/itcs-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-author-response into .gemini/skills/itcs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-author-response", 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-author-responseInstalls 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-author-response -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-author-response .github/skills/itcs-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-author-response into .github/skills/itcs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-author-response", 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-author-response -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-author-response --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-author-response .opencode/skills/itcs-author-response && 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-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ITCS-Skills/skills/itcs-author-response into .opencode/skills/itcs-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "itcs-author-response", 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-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 594 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to operate under the reality that ITCS has no rebuttal or author-response phase — pre-empting reviewer objections inside the submission, then handling the post-decision…
- Operate under the reality that ITCS has no rebuttal
- SKILL.md covers Part 1 — The rebuttal you…, Part 2 — After the decision, What "author response" is NOT… and Output format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Author-response phase — pre-empting reviewer objections inside the submission
What it does
Itcs Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to operate under the reality that ITCS has no rebuttal or author-response phase — pre-empting reviewer objections inside the submission, then handling the post-decision situation (camera-ready window on accept, or rerouting and reusing the reviews on reject) since there is no revise-and-resubmit.
Its SKILL.md is about 1.3k 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
- Operate under the reality that ITCS has no rebuttal
- Author-response phase — pre-empting reviewer objections inside the submission
- Then handling the post-decision situation (camera-ready window on accept
- Rerouting and reusing the reviews on reject) since there is no revise-and-resubmit
Example prompts
- “/itcs-author-response”
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 Author Response loads about 1.3k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 594 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). 594 words, ~1,254 tokens.
Download SKILL.mdSave it as
.claude/skills/itcs-author-response/SKILL.md (or your agent's skills folder).- name
- itcs-author-response
- description
- Use to operate under the reality that ITCS has no rebuttal or author-response phase — pre-empting reviewer objections inside the submission, then handling the post-decision situation (camera-ready window on accept, or rerouting and reusing the reviews on reject) since there is no revise-and-resubmit.
ITCS Author Response
The defining fact of this skill: ITCS has no rebuttal and no author-response phase. Following
theory-conference norms, the program committee forms its reviews and reaches accept/reject
without any input from you in between (see
itcs-review-process). There is also no Major Revision and
no revise-and-resubmit. So "author response" at ITCS is not a rebuttal-writing task — it is
(1) doing the rebuttal's work inside the submission, before the deadline, and (2) handling the
situation after the decision lands. Both are covered here.
Part 1 — The rebuttal you write in advance (in the paper)
At a rebuttal venue you would hold arguments in reserve to answer reviewers. At ITCS there is no reserve turn, so every such argument must be in the submitted PDF. Pre-empt the three objections an ITCS PC reliably raises:
- "Is the model trivial or all-powerful?" Answer with an anchoring result in the
introduction — a separation or surprising possibility showing the model is neither empty nor
everything (see
itcs-writing-style). - "Is this actually new?" Answer with a delta-first related-work paragraph naming the
closest prior model and what it did not ask; search the ITCS/ICS back-catalog hardest, since
that is where "already asked" hides (see
itcs-related-work). - "Why should the community care?" Answer with a concrete payoff — a connection, a reframing, an application sketch — on the first page.
Also disarm the objections you can foresee about your own paper:
- State scope and limitations yourself. A candidly owned gap is a strength at ITCS; the same gap discovered by a reviewer, with no rebuttal to contextualize it, is a weakness.
- Prove the load-bearing lemma in full, in the PDF's appendix — a reviewer who gets stuck on a
deferred proof cannot ask you to clarify (see
itcs-reproducibility). - Add a "why not the obvious approach" remark where a reviewer might think your problem is easy; this is the single most common unspoken objection to a new-model paper.
Part 2 — After the decision
On accept
- Move to
itcs-camera-ready: switch tolipics-v2021, de-anonymize, complete LIPIcs metadata, hit the production deadline. - Reviews may still contain requests or corrections even without a rebuttal round. Fold reasonable fixes into the camera-ready — a corrected claim, a missing citation, a clarified definition — using the extra latitude the (unlimited) LIPIcs length allows.
- Register a presenter; consider a Graduating Bits talk if a coauthor is near graduation.
Show full SKILL.md (209 more words)Show less
On reject
There is no resubmission to a later ITCS round this year (single annual cycle), so the move is to use the reviews, not to answer them:
- Mine the reviews for the real objection. Since they were written without expecting a reply, they tend to be candid. Identify whether the paper was judged not novel enough (a framing problem) or not correct/complete (a proof problem) — the fix differs sharply.
- Reroute by the diagnosis. If reviewers admired the depth but not the novelty, a depth venue
(STOC/FOCS/SODA) may fit; if they doubted the novelty of the question, rethink the framing
before resubmitting anywhere (see
itcs-topic-selection). - Fix proof gaps before the next submission, and update the arXiv/ECCC/ePrint full version so the durable record is correct.
- Do not email the PC to argue the decision. There is no appeal-by-rebuttal culture; a polite clarifying question to the chairs is the ceiling, and rarely changes an outcome.
What "author response" is NOT at ITCS
| Not this | Because |
|---|---|
| A rebuttal document answering reviewers | There is no author-response phase |
| A point-by-point response letter | There is no Major Revision / R&R round |
| A second submission to a later round | ITCS runs one annual cycle |
| An appeal to overturn a reject | No appeal-by-rebuttal culture; reroute instead |
Output format
[ITCS response mode] pre-submission pre-emption / post-accept / post-reject
[Pre-emption] anchoring result? novelty delta? payoff? scope owned? load-bearing proof in PDF? (yes/no each)
[Post-accept] camera-ready fixes folded in? presenter registered? Graduating Bits considered?
[Post-reject] objection diagnosed (novelty vs correctness)? reroute target? full version corrected?
[Next action] <single clearest step>© 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-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Itcs Author Response 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 Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | 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.
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.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Author Response
What does Itcs Author Response do?
A skill your agent uses to operate under the reality that ITCS has no rebuttal or author-response phase — pre-empting reviewer objections inside the submission, then handling the post-decision…. Itcs Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to operate under the reality that ITCS has no rebuttal or author-response phase — pre-empting reviewer objections inside the submission, then handling the post-decision situation (camera-ready window on accept, or rerouting and reusing the reviews on reject) since there is no revise-and-resubmit.
When should I use Itcs Author Response?
Itcs Author Response fits situations like: operate under the reality that ITCS has no rebuttal; author-response phase — pre-empting reviewer objections inside the submission; then handling the post-decision situation (camera-ready window on accept; rerouting and reusing the reviews on reject) since there is no revise-and-resubmit.
How do I install Itcs Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-author-response -a claude-code`. Or copy the skill folder (ITCS-Skills/skills/itcs-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/itcs-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Itcs Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill itcs-author-response -a codex`. Or copy the skill folder (ITCS-Skills/skills/itcs-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/itcs-author-response in your project. Codex loads it when a task matches its description.
Can I use Itcs Author Response 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-author-response -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-author-response, .gemini/skills/itcs-author-response, .github/skills/itcs-author-response and .opencode/skills/itcs-author-response in your project.
What does Itcs Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Itcs Author Response is instructions for the agent only.
Does Itcs Author Response 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 Author Response 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 Author Response use?
Itcs Author Response 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 Author Response use?
About 1.3k tokens (SKILL.md is roughly 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 Author Response?
Skills that share tags, products or a category with Itcs Author Response: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Itcs Author Response?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.